hmmmm,

I never had a problem moving bigger files over the LAN, streaming TV from and to the box. But this is not SMB .... maybe there is the problem. Can you check if swap is enabled on your box? Apart from this I don't have a clue what could be the cause. One would have to repeatedly check the status via console (serial or telnet) to see what happens....

schufti

fuse and ntfs_3g is now in newest fw (MGB100_v4c3sq_080926)

Hi,

unfortunately I can't see your setup from here.
BUT if you are using the MGB100 as AP, the PC is a client and you are using TKIP then I have to tell you that the only way is to cange to AES.
(Explanation: the AP driver is no longer maintained....)

schufti

Hi,

if you were familiar with U, you would guess that the copy process wants to duplicate the access rights on the new (copied) file. BUT FAT32 doesn't support any (apart from r/o) access rights, so leading to the message that "chmod" (setting access rights) failed.... MC therefor gives you the option to skip (all), just to copy the files but skip the access rights.

schufti

Hi,

that is normal, as the version string is now fixed in the GUI (that is not included in .upg files). You can telnet into the device and look at the /build-* file that should have an appropriate date, or try ntfs-3g command ;-)

schufti

Hi,
there shouldn't be any problem, as long as you don't try to downgrade (flash 's' upgrade file). If you are on 'c' series, you will have to downgrade with ~b7 orig fw.

it is in rebrand_MGB.zip that you find in my repository (see my signature)
you have to flash via recovery loader (see wiki)
then flash latest orig c3 fw from airlive webpage
now you can flash MGB100_v4c3sq_080926 via GUI

Hi,

forgot to mention: 

I wrote about "unlock" file in several threads; in reality it rebrands your box without telling you. So I disregard using it. If you want your device rebranded, do it willingly with the rebranding files in the repository (then you can use whatever fw you like, even airlive latest c3 full fw.

If you want your box "warranty" clean but use "c3" fw with dl'agent, only flash uc3gui and c3 upgrade fw. You are free to revert to your boxes orig. fw at any time.

schufti

n.b.: now that you messed up your box with "unlock" fw, it is only first option to you.

hi,

if you would have read a little in other threads - even only recent posts - you would have found this:
http://www.macsat.com/macsat/component/option,com_smf/Itemid,50/topic,685.msg4584/#msg4584

schufti

Hi,

I don't know your SMC fw, but c2 sounds pretty modern.

So maybe all you need to do is flash the uc3gui (repository) via recovery loader and then flash with desired c3 upgrade via GUI. Warning: all your settings will be set to default.

schufti

hi stharvey,

now it is starting to make sense...

Best thing for you to do isget the "rebranding" package from the wiki/repository. Then flash your box with the file "ovislink.bin" via recovery loader. Right after this (without reboot) flash the v400b6 fw from the airlive page. Then you should reboot and reset to factory settings. After this you can decide to work with old GUI and S8 (GPL-) upgrade file or flash to latest original c3 airlive fw with new GUI (download agent) and then "upgrade" with my c4 (GPL-)upgrade file.

N.B.: "uprade" files don't come with GUI, so one has to use orig fw files to successfully upgrade between all orig fw versions. (GPL-)upgrade files are allways valid for same base orig. fw version only.

schufti

as I don't know what you did with your box, I cant say what fw you really need.
you are saying that you have a SMC box, but you were working with tha latest airlive fw!
what didi you do to get that working? Did you use the "opening" fw, did you rebrand with my "rebranding" files or ....?

No fw on the airlive website is an upgrade file, they are all full fw.

but if it is still SMC "inside" (what I doubt) then you'll need SMC fw!

btw, did you manage to start recovery loader?

schufti

hi,
ahh yesss, hw fault was what I was expecting on 2nd thought, but I asumed that to being checked first.

ok, so now it's working and everyone is happy 

schufti

the flash won't change it's identity whatever you do, unless you fry it.... what you won't be able without doing really nasty stuff like applying (too) high voltage.

what makes you think that jtag is skipping bytes all over the place? are you sure that your redboot is actually working?
I asume that you have a working serial console? then just try to flash the redboot from the wiki and see if it gives any serial output (38400,8,1,n). disable verify on flashing!


schufti