The only exception is you should have only one section. So that 'advice' about having separate disk tag files was wrong, it actually makes things worse (unless you have all the tag files on both floppies)!Īlso, for txtsetup.oem, I found that you can have as many sections as you like and in any order you like! It will just read them all. The only difference is that one txtsetup.oem has a section for firadisk and the other txtsetup.oem file has a section for iastor disk1) and the other driver files are identicalĢ. fd0 and fd1 have identical files on them. So the problem seems to be that at the Copyfiles stage, XP does not have any concept of floppies A: and B: - just the current 'drive A:'!!!ġ. If the disk0 tag was present and the file copy was successful, it now looks for the disk1 tag on the current drive - it does not find it so it asks you to insert the correct disk! So it looks for a disk0 tag file on the current drive A: - if present it copies over the sys/inf/cat files (if not present it stops and asks you to insert the correct disk). Now in copy-files textmode stage after formatting has taken place, it tries to find the drivers so it can copy them over to the hard disk. In F6 we load iastor and firadisk and then the drivers are loaded (not sure what order.) so we can see the internal hard disk to format it. The 'current' drive A: is whatever was accessed last after selecting the drivers using F6 + S and then it loading the drivers before getting to the EULA screen.įd0 'disk0' tag file txtsetup.oem has firadisk as defaultįd1 'disk1' tag file txtsetup.oem has iastor as default It seems the problem in the copyfiles stage (after formatting) is that it expects the 'current' floppy drive A: to have the correct driver files. I was just doing some more investigating. I tried it on a VM (using ICH9) and a real nbook (using ICH7) - both give identical behaviour, so it is not a VM problem. I have been trying various things for ages to get past this but I seem to be stuck! Once (and only once!) I got it to work but I could not repeat it even though I know what I did ! However, the problem is that immediately after formatting the HDD and then going into the text-mode copyfiles stage, it stops with a 'Please insert disk "xxxx" into Drive A:" So it seems to have loaded both drivers automatically. When I press F8 to accept the EULA, I can now see both the USB drive and the HDD listed (so I know that the AHCI driver has been loaded) Now I do not need to use F6! When XP Setup loads, the firadisk driver is loaded without pressing F6 (if it wasn't I would get a BSOD). Well, I have * almost* got it working buy using two F6 floppies!īoth virtual floppies are identical but the txtsetup.oem has default=iastor on one and on the other I have default=firadisk.īoth disks have all driver files for firadisk and ahci and both disks have a disk0 and disk1 empty file used as a diskid file. Is it possible to load more than one driver from txtsetup.oem? Any ideas? If I omit the firadisk and winvblock lines, then it does load the AHCI driver. I have tried adding multiple lines to the Files section e.g.īut this does not seem to work in that the AHCI driver is not loaded. The problem is I am not sure how to add more than one driver to the txtsetup.oem so that they are all loaded automatically without pressing F6. I have modified the code and can now make a virtual floppy with the firadisk and winvblock drivers on it and modify the txtsetup.oem file. I want to add the FiraDisk and WinvBlock drivers to the txtsetup.oem file that is created by DPMS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |