![]() |
![]() |
#21 | |
Amiga Games Database
Join Date: Jun 2006
Location: South West England
Posts: 1,316
|
Quote:
Thanks Thomas. I just had another thought...... I may not have properly understood what people have been saying, but in Tornado, I don't use the WHDLoad Quit key because the default one conflicts with one of the flight-sims keybopard bindings. I exit the game by using the original Quit function from the game. Might that be the problem - assuming the game tried to save on Exit, and PFS3 is not quick enough to manage that? |
|
![]() |
![]() |
#22 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,047
|
No, you didn't understand that right.
The problem is while the game is running. As an originally floppy-based game it kills the OS and used its own routines to access the hardware. This includes the floppy hardware. I.e. if it writes something to disk, it keeps the OS dead and uses its own means to write to floppy disk. Now the WHDLoad slave changed the game code to write to harddisk instead. Here hardware banging is not possible. So the slave has to wake up the OS and use DOS routines to write to a file and then set the OS asleep again. But the OS does multitasking. That means DOS sends the data to another task and returns to the caller. The other task write the data to disk in the background. This means the slave must not kill the OS too early. But it cannot tell when the data finally has been written completely. That's where WriteDelay comes into account. It tells the slave how long it should wait so that the harddisk definitely has finished its work. If it is too short the background task is interrupted in the middle of its work. If you quit the game, the OS wakes up ultimately. You cannot quit the game too early. It is more likely that the game code does something bad to the memory used by the OS while the OS is sleeping. In this situation the game has full control and might not care about allocated vs. unallocated memory. It treats everything as its own. |
![]() |
![]() |
#23 |
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 3,325
|
The default WHDLoad behaviour is that writes to HD are done on Quit (key) if you don't use http://whdload.de/docs/en/opt.html#NoWriteCache
|
![]() |
![]() |
#24 |
Registered User
Join Date: Feb 2017
Location: Denmark
Posts: 1,301
|
I have no idea what the problem might be, but whdload also writes when you exit through other means (doesn't have to be the quit key), at least when it's not an abnormal exit (but maybe there as well, just haven't tested that). I can change settings and use the "exit button" in the game and they are persisted just fine. (Only commenting on the AGA version)
Tornado is fairly system friendly, and doesn't take over the machine. It uses DOS for all its file operations. In the whdload version this goes through the kickfs (virtual HD), but the write cache thing still applies of course. I can't rule out that there are bugs where the game will trash memory outside WHDLoad, but by default the MMU (if present) is used to guard against that, and I haven't seen any such problems during testing. |
![]() |
![]() |
#25 | |
Amiga Games Database
Join Date: Jun 2006
Location: South West England
Posts: 1,316
|
Quote:
I'm very grateful for all the knowlegable comments, guys. I'm still unsure what to do. ![]() I know the partition is broken - but presumably it might just be a faulty SD card? It's a 3GB partition by the way. Here's what I think I'll do: Reformat the partition (still PFS3) Copy back my stuff to it (mostly WHDLoad games) Double the WriteDelay on Tornado to 300 (6 seconds) See how that goes. ![]() If that doesn't work..... Maybe convert the partition to FFS and perhaps split it into 2 partitions. Does that sound sensible, or at least not completely daft? ![]() |
|
![]() |
![]() |
#26 |
Amiga Games Database
Join Date: Jun 2006
Location: South West England
Posts: 1,316
|
I've now had problems on my boot partition, SDH0:
I don't know if this is Tornado related or not, but after the problems appeared on my WHDLoad partition (SDH1 ![]() I have played a couple of games of Tornado with it there. Then yesterday I got an error requester, so I used Quarterback Tools. This is the error log I got. It does feature Tornado, but I have no idea if that implies that it is the problem or not. * Starting to analyze and repair disk "SDH0" * Block scan started Jun 27, 2024 at 2:04:59 PM No bad blocks were found. * Block scan completed Jun 27, 2024 at 2:09:40 PM * File scan started Jun 27, 2024 at 2:09:40 PM Drawer: SDH0:L Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:L Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:L Entry: KingCON-handler Error: File ext header checksum error Action: Checksum was recalculated Drawer: SDH0:L Entry: KingCON-handler Error: File ext header type is bad Action: File was deleted Drawer: SDH0:L Entry: KingCON-handler Error: File size error Action: Error was corrected Drawer: SDH0:L Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Temp Entry: v³_v³_v³_v³_v Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Tools/HDTools Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Tools/HDTools Entry: „³ Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Tools/HDTools Entry: BRU Error: File ext header checksum error Action: Checksum was recalculated Drawer: SDH0:Tools/HDTools Entry: BRU Error: File ext header type is bad Action: File was deleted Drawer: SDH0:Tools/HDTools Entry: BRU Error: File size error Action: Error was corrected Drawer: SDH0:Tools/HDTools Entry: HDBackup Error: File ext header checksum error Action: Checksum was recalculated Drawer: SDH0:Tools/HDTools Entry: HDBackup Error: File ext header type is bad Action: File was deleted Drawer: SDH0:Tools/HDTools Entry: HDBackup Error: File size error Action: Error was corrected Drawer: SDH0:X Entry: p³_p³_p³_p³_p Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:X Entry: o³_o³_o³_o³_o Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:X Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:X Entry: u³_u³_u³_u³_u Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Games/Tornado Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Games/Tornado/DATA-AGA Entry: FLIGHT Error: File ext header checksum error Action: Checksum was recalculated Drawer: SDH0:Games/Tornado/DATA-AGA Entry: FLIGHT Error: File ext header type is bad Action: File was deleted Drawer: SDH0:Games/Tornado/DATA-AGA Entry: FLIGHT Error: File size error Action: Error was corrected Drawer: SDH0:Libs Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs Entry: xadmaster.library Error: File ext header checksum error Action: Checksum was recalculated Drawer: SDH0:Libs Entry: xadmaster.library Error: File ext header type is bad Action: File was deleted Drawer: SDH0:Libs Entry: xadmaster.library Error: File size error Action: Error was corrected Drawer: SDH0:Libs Entry: t³_ t³_t Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs Entry: y³_ y³_y Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs/XAD Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs/XAD Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs/XAD Entry: n³_n³ Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs/XAD Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs/XAD Entry: ‚³_‚³_ Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs Entry: z³_z³ Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0:Libs Entry: Error: Unknown secondary type Action: Bad entry was deleted Drawer: SDH0: Entry: Error: Bitmap contents incorrect Action: Bitmap was reconstructed Major problems found: 32 Minor problems found: 11 Total files processed: 10,779 Bad files deleted: 0 Total links processed: 0 Bad links deleted: 0 Total drawers processed: 0 Bad drawers detected: 22 Unreadable blocks found: 0 Volume status: Major problems corrected. Volume usable. |
![]() |
![]() |
#27 |
Registered User
Join Date: Jan 2008
Location: Warsaw/Poland
Age: 56
Posts: 2,125
|
Always better is use small partition for WHDload saving.
Dont must to move installed games. Use SavePath from WHDLoad https://whdload.de/docs/en/opt.html Do you used WriteDelay ? Im not expert, but these errors looks strange. Maybe you have virus in your system? You dont need to use QBTools if it was normal validation problem. You need only a wait a few minutes, for 500MB partition. |
![]() |
![]() |
#28 | |
Amiga Games Database
Join Date: Jun 2006
Location: South West England
Posts: 1,316
|
Quote:
The saga continues to develop - the problem has now spread to the FAT32 partition so the PIStorm can't boot, when I power up the Amiga I just see a lot of Raspberry Pi4 checks etc. I've asked the guys on the PiStorm Discord server for any thoughts. Can I assume this rules out an issue with: PFS3 Tornado WHDLoad saving And is most likely a failing SD card? In case it is a virus (I have an anti-virus in WB startup, but it's probably older than some Amiga games ![]() P.S. I still have a CF card on the Amiga. |
|
![]() |
![]() |
#29 |
Amiga Games Database
Join Date: Jun 2006
Location: South West England
Posts: 1,316
|
Just to conclude this tale of woe, I bought some more SD cards and replaced the one in the PiStorm. That seems to have fixed things.
I don't think my original SD card (SanDisk was fake) the other 2 bought at the same time are okay (for now!) and they each came in what seems like genuine packaging along with the larger SD adaptors - which the replacements don't have. :-/ I managed to reformat the original problem SD card and then run H2Testw on it. I have put the somewhat scary results below: Warning: Only 14893 of 14894 MByte tested. The media is likely to be defective. 14.3 GByte OK (30108448 sectors) 191.6 MByte DATA LOST (392416 sectors) Details:191.5 MByte overwritten (392352 sectors) 0 KByte slightly changed (< 8 bit/sector, 0 sectors) 32 KByte corrupted (64 sectors) 191.5 MByte aliased memory (392352 sectors) First error at offset: 0x000000005f5c4000 Expected: 0x000000005f5c4000 Found: 0x00000001f0cb4000 H2testw version 1.3 Writing speed: 14.8 MByte/s Reading speed: 17.9 MByte/s H2testw v1.4 |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
PFS3 file system and Quake 2 angst | Angus | Retrogaming General Discussion | 39 | 14 November 2023 21:34 |
Installed PFS3 AIO file system on my 1200 CF Card. Am I okay? | turrican9 | support.Hardware | 7 | 01 June 2018 16:14 |
Does ClassicWB support PFS3/long file names? | Foebane | support.Apps | 12 | 06 March 2018 23:07 |
File systems PFS3, FFS and Early boot menu | Gilloo | request.Other | 0 | 15 June 2015 20:42 |
System is not validated! FFS (and I dont mean fast file system!) | Macca | support.Hardware | 11 | 11 June 2007 13:04 |
|
|