MS-DOS 5.0 setup disk 1 hangs when starting setup? \ VOGONS

MS-DOS 5.0 setup disk 1 hangs when starting setup?

Topic actions

Post a reply

First post, by superfury

Posted on 2016-02-14, 17:06

superfury Offline

Rank l33t++

Rank: l33t++
Posts: 5472
Joined: 2014-03-08, 11:25
Location: Netherlands

When I try to start the setup procedure on MS-DOS 5.0 setup disk 1, I get the following log (when enabling the emulator debugger, which currently logs both instructions executed and floppy disk activity (except the actual data transfer itself, so only command, parameter, result phases and status changes and register reads/writes (using all floppy ports except the data port) results/written data).

When I try the disk on Virtualbox, it works without problems. When I try to run it in my emulator, it first boots, then starts detecting hardware (or so it tells me), then telling me to insert disk 1 in a loop.

This is the log of the Floppy Disk Controller during checking for disk 1:

10:05:15:43.5.0062: FLOPPY: Write DOR=18
2
30:05:15:43.6.0277: FLOPPY: Reset requested by DOR!
4
50:05:15:43.7.0329: Pending 1 Sense Interrupt because of a bug in the Turbo XT BIOS!
6
70:05:15:45.3.0984: FLOPPY: Write DOR=1C
8
90:05:15:45.4.0903: FLOPPY: Activation requested by DOR!
10
110:05:15:46.3.0444: FLOPPY: MSR changed: 80
12
130:05:15:46.4.0397: FLOPPY: Read MSR=80
14
150:05:15:46.6.0664: FLOPPY: Command byte sent: 08
16
170:05:15:46.7.0354: FLOPPY: executing command: 08
18
190:05:15:46.7.0354: FLOPPY: Reset for all drives has been finished!
20
210:05:15:46.7.0386: FLOPPY: Sense interrupt: ST0=C0, Currentcylinder=00
22
230:05:15:48.6.0012: FLOPPY: MSR changed: d0
24
250:05:15:48.6.0899: FLOPPY: Read MSR=D0
26
270:05:15:48.8.0903: FLOPPY: Reading result byte 1/2
28
290:05:15:49.4.0192: FLOPPY: Read MSR=D0
30
310:05:15:50.0.0335: FLOPPY: Read MSR=D0
32
330:05:15:51.8.0173: FLOPPY: Reading result byte 2/2
34
350:05:15:52.1.0786: FLOPPY: MSR changed: 80
36
370:05:15:52.2.0509: FLOPPY: Read MSR=80
38
390:05:15:52.8.0750: FLOPPY: Read MSR=80
40
410:05:15:53.2.0068: FLOPPY: Command byte sent: 03
42
430:05:15:53.6.0372: FLOPPY: MSR changed: 90
44
450:05:15:53.7.0062: FLOPPY: Read MSR=90
46
470:05:15:55.4.0735: FLOPPY: Parameter sent: DF(#1/2)
48
490:05:15:55.9.0597: FLOPPY: Read MSR=90
50
510:05:15:56.2.0586: FLOPPY: Parameter sent: 02(#2/2)
52
530:05:15:56.3.0342: FLOPPY: executing command: 03
54
550:05:15:69.6.0976: FLOPPY: Write DOR=1C
56
570:05:15:70.2.0659: FLOPPY: MSR changed: 80
58
590:05:15:70.3.0480: FLOPPY: Read MSR=80
60

…Show last 103 lines

610:05:15:72.0.0365: FLOPPY: Command byte sent: 07
62
630:05:15:72.5.0555: FLOPPY: MSR changed: 90
64
650:05:15:72.6.0311: FLOPPY: Read MSR=90
66
670:05:15:72.8.0545: FLOPPY: Parameter sent: 00(#1/1)
68
690:05:15:72.9.0268: FLOPPY: executing command: 07
70
710:05:15:75.3.0774: FLOPPY: MSR changed: 80
72
730:05:15:75.4.0661: FLOPPY: Read MSR=80
74
750:05:15:75.6.0894: FLOPPY: Command byte sent: 0F
76
770:05:15:76.1.0494: FLOPPY: MSR changed: 90
78
790:05:15:76.2.0216: FLOPPY: Read MSR=90
80
810:05:15:76.4.0450: FLOPPY: Parameter sent: 00(#1/2)
82
830:05:15:76.8.0721: FLOPPY: Read MSR=90
84
850:05:15:78.7.0379: FLOPPY: Parameter sent: 00(#2/2)
86
870:05:15:78.8.0365: FLOPPY: executing command: 0F
88
890:05:15:79.7.0563: FLOPPY: MSR changed: 80
90
910:05:15:79.8.0351: FLOPPY: Read MSR=80
92
930:05:15:80.0.0585: FLOPPY: Command byte sent: 08
94
950:05:15:80.1.0472: FLOPPY: executing command: 08
96
970:05:15:80.1.0472: FLOPPY: Sense interrupt: ST0=20, Currentcylinder=00
98
990:05:15:81.9.0967: FLOPPY: MSR changed: d0
100
1010:05:15:82.0.0821: FLOPPY: Read MSR=D0
102
1030:05:15:82.3.0022: FLOPPY: Reading result byte 1/2
104
1050:05:15:82.6.0537: FLOPPY: Read MSR=D0
106
1070:05:15:83.1.0497: FLOPPY: Read MSR=D0
108
1090:05:15:83.4.0322: FLOPPY: Reading result byte 2/2
110
1110:05:15:85.3.0277: FLOPPY: MSR changed: 80
112
1130:05:15:85.4.0525: FLOPPY: Read MSR=80
114
1150:05:17:11.9.0714: FLOPPY: Read MSR=80
116
1170:05:17:12.3.0459: FLOPPY: Command byte sent: E6
118
1190:05:17:12.8.0682: FLOPPY: MSR changed: 90
120
1210:05:17:12.9.0339: FLOPPY: Read MSR=90
122
1230:05:17:13.1.0672: FLOPPY: Parameter sent: 00(#1/8)
124
1250:05:17:15.1.0776: FLOPPY: Read MSR=90
126
1270:05:17:15.5.0028: FLOPPY: Parameter sent: 00(#2/8)
128
1290:05:17:15.9.0989: FLOPPY: Read MSR=90
130
1310:05:17:16.3.0306: FLOPPY: Parameter sent: 00(#3/8)
132
1330:05:17:16.9.0351: FLOPPY: Read MSR=90
134
1350:05:17:18.9.0094: FLOPPY: Parameter sent: 01(#4/8)
136
1370:05:17:19.4.0120: FLOPPY: Read MSR=90
138
1390:05:17:19.7.0241: FLOPPY: Parameter sent: 02(#5/8)
140
1410:05:17:20.2.0135: FLOPPY: Read MSR=90
142
1430:05:17:22.0.0006: FLOPPY: Parameter sent: 09(#6/8)
144
1450:05:17:22.5.0327: FLOPPY: Read MSR=90
146
1470:05:17:22.8.0382: FLOPPY: Parameter sent: 2A(#7/8)
148
1490:05:17:23.3.0146: FLOPPY: Read MSR=90
150
1510:05:17:25.1.0180: FLOPPY: Parameter sent: FF(#8/8)
152
1530:05:17:25.2.0100: FLOPPY: executing command: 06
154
1550:05:17:25.2.0100: FLOPPY: Read sector #0
156
1570:05:17:25.2.0133: FLOPPY: Sector size: 512 bytes
158
1590:05:17:25.2.0133: FLOPPY: Requesting transfer for 512 bytes.
160
1610:05:17:25.2.0297: FLOPPY: Start transfer of data (DMA: 1)...
162

Is it actually not requesting a DMA transfer method of reading the boot sector, because of unhandled registers? It does send a specify command (the command #3 in the log) with a value of 2(setting it's DMA bit to 0, or Non-DMA mode to the floppy disk controller). However, it also enables DMA mode with the DOR register (which is actually used by my emulator to determine DMA access). Is DMA enable a simple 'AND' operation(both need to be set to use DMA) or an OR operation (either one needs to be set to use DMA) between those two DMA values? In this case the DOR has DMA&IRQs enabled, and the floppy disk itself (specify command) has it's DMA disabled. So does the read sector actually need to use DMA or not?

Edit: After verifying it, the setup procedure is actually asking for a DMA transfer (DMA bit 1=0 tells DMA transfer, FDC is instructed to use DMA&IRQs). For some reason, it isn't correctly reading the boot sector at that point? Or it's actually timing out for some reason?

Author of the UniPCemu emulator.
UniPCemu Git repository
UniPCemu for Android, Windows, PSP, Vita and Switch on itch.io

Go to top of page Go to top of page

Back to PC Emulation

Main menu

Common searches