![]() Tried this modification, install ran up to 99% then it asked me where "Windows 95 Boot Floppy" files where located, I typed "A:\" followed by ENTER and installation continued without any more hiccups. Can CD.INF be modified so it searches for the files in the floppy? I tried it as is, and at 23% the installation stopped and asked me where the *.sys files were, pointing to D:\WIN95, which is where they obviously are not. ![]() ![]() start installation with SETUP.EXE CD.INF.īut now I want to use CD.INF from the floppy, ie SETUP.EXE A:\CD.INF because the cd drivers are already in the floppy and so I don't have to use a modified ISO. create \WIN95\CD.INF with the following content:ĭevAddDev=OAKCDROM.SYS,device,"/D:MSCD001"ĭevAddDev=BTCDROM.SYS,device,"/D:MSCD001"ĭevAddDev=ASPICD.SYS,device,"/D:MSCD001" copy cd drivers to \WIN95 folder (aspi*.sys, bt*.sys, flashpt.sys and oakcdrom.sys) It basically copies the cd drivers to the Windows folder during Windows installation, and adds the required lines to config.sys and autoexec.bat: Some years ago I used this workaround with VirtualPC, which also works with VirtualBox. I know that the emulated chipset is not supported by Windows 95, so the first part of the installation "sees" the CD drive because of the drivers loaded by the floppy, but the second part of the installation doesn't see the cd drive because it's no longer booting from the floppy, and fails to copy files. I'm trying to install Windows 95 on VirtualBox with a homemade floppy and an original CD. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |