1165b245ce
- numerous bug fixes - wtv-mail system - user account updates - viewergen alpha (experimental webtv viewer patcher on pc_service) - implement wtv-favorites with huge help from @JarHead4 - add wtv-ticket store api - Bump vm2 from 3.9.5 to 3.9.7 in /zefie_wtvp_minisrv - fix bf0app default rom - Add wtv-1800 service to wtv-1800:/noflash - handle webtvism: - allow get/post variables to be the same name multiple times - rather than overwrite, the server will now change the variable from a string to an array. - Rewrite script processing a bit - Instead of using eval() we now use a proper VM Context - As a result, any scripting errors will now give a more useful filename and line number. - However, some things may break, if they are dependant on variables we are not allowing in the context. - BREAKING CHANGES: - `ssid_sessions[socket.ssid]` is now `session_data` - `require` is no longer allowed in user scripts - add star service - change how we handle modules for services in the VM - fixed wtv-disk:/sync always failed the first time - implement production-like wtv-star handling (when a service port becomes unavailable, it requests the url over the wtv-star port to show an error page) - renamed WTVDownloadList.js to WTVDisk.js - a bit more work on WTVNews (created class) - probably more stuff I can't remember
12 lines
883 B
Plaintext
12 lines
883 B
Plaintext
The bf0app flashing system requires a two things that you must be aware of, that are different from a typical setup:
|
|
|
|
1) Your PPP system MUST accept auth, a noauth setup will not work for the 2nd dialing phase
|
|
|
|
2) You must have a clean dialup. DreamPi voltage-hacked lines, and unstable VoIP systems are known
|
|
to cause errors, leaving the box in a 'braindead' state with no flash. MiniSrv can help recover
|
|
from this but you will need to provide a stable dialup connection. This was tested with my Cisco 3825 setup.
|
|
|
|
3) bf0app systems flash right away, as soon as a part is received and validated.
|
|
This means if your bf0app box fails mid-flash, you could design a custom page to send the flashrom
|
|
from where it left off (for example, if your box failed on part 3 of 16, you could start again at
|
|
part 3 (with a specially set up page, minisrv won't do this by default) |