muteki wrote: Sun May 26, 2024 3:40 pm
Thanks for all the info and testing!
Just wondering about a couple of things:
-Does it mean that Kickstart 3.2.2 (47.111) is not supported (or that it is assumed that this version will crash when using the TF IDE)?
-Same question for ehide: Is ehide.device 1.2 not supported?
- @supaduper Can you confirm that my TF1232 has the 2024_02_22 firmware version?
Yes you have the latest firmware
3..2.2 will work and so will ehide.1.2 but like you I get lockups with file transfers, remember, OS 3.2 is buggy that`s why there has been so many updates
I know eric ( ehide dev ) tried the same as me and said he only got one one lockup, but he was doing small file transfers, you have to try large file transfers of bigger than 500mb and then see if it locks up
muteki wrote: Sun May 26, 2024 3:40 pm
Thanks for all the info and testing!
Just wondering about a couple of things:
-Does it mean that Kickstart 3.2.2 (47.111) is not supported (or that it is assumed that this version will crash when using the TF IDE)?
-Same question for ehide: Is ehide.device 1.2 not supported?
- @supaduper Can you confirm that my TF1232 has the 2024_02_22 firmware version?
Yes you have the latest firmware
3..2.2 will work and so will ehide.1.2 but like you I get lockups with file transfers, remember, OS 3.2 is buggy that`s why there has been so many updates
I know eric ( ehide dev ) tried the same as me and said he only got one one lockup, but he was doing small file transfers, you have to try large file transfers of bigger than 500mb and then see if it locks up
The tool i posted above just keeps transferring data forever until a lockup. I cant see the issue with the versions posted.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Steve I will send you my SD 16 gb 3.2.2.1 system via email that has an empty large partition so you can just drag and drop some big folders/files into and see if it locks up like it does on me, also I mentioned to eric that he was using emulated rom, whereas I am using eeproms, do not know it that makes a difference , do you use emulated roms ?
Also when I used your readdisk.exe it says it is using the scsi.device in the output window is that correct ?
supaduper wrote: Sun May 26, 2024 4:14 pm
Also when I used your readdisk.exe it says it is using the scsi.device in the output window is that correct ?
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Can i just check with everyone. I am booting from the internal CF card and then hammering the TF ide?
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
terriblefire wrote: Sun May 26, 2024 4:45 pm
Can i just check with everyone. I am booting from the internal CF card and then hammering the TF ide?
No Bud you need nothing on the Internal IDE and should boot solely from the TF IDE
Use the roms and system image I sent you on the TF IDE, then we are both on the same page
Ok.. Dont do that. Always have something on the internal IDE. TF123x seem to be sulky unless you have something on the internal IDE. You dont need to use it.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Thanks folks. Can you guys try the readdisk.exe with ehide.device as a parameter.. see if you get the lockup
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
