First post, by superfury
I notice some weird behaviour by Windows NT's setup booting when it starts to read the files from disk into memory(the log is of Windows NT setup being loaded)?
CHS=>physicalmemoryaddress
9,1,3=>49e00
9,1,4=>4a000
9,1,5=>4a200
9,1,6=>4a400
9,1,7=>4a600
9,1,8=>4a800
9,1,9=>4aa00
9,1,a=>4ac00
9,1,b=>4ae00
9,1,c=>4b000
9,1,d=>4b200
9,1,e=>4b400
9,1,f=>4b600
9,1,10=>4b800
9,1,11=>4ba00
9,1,12=>4bc00
a,0,1=>4be00 (9,0,1=>4be00?)
a,0,2=>4c000
a,0,3=>4c200 (a,0,3=>4a000?)
a,0,4=>4c400 (a,0,4=>4a200?)
a,0,5=>4c600
As is seen, each time it switches over to the next track, it reads the wrong addresses(as is noted within (...)). The automatic seeking will wrap back from head 1 to head 0, but the track will stay the same(as it won't increase to the next track by it's own, until a seek command is executed).
Would that be correct behaviour?
Author of the UniPCemu emulator.
UniPCemu Git repository
UniPCemu for Android, Windows, PSP, Vita and Switch on itch.io