Hi guys. I have problems getting the cdrom to work in dos mode under Win95. The error mess I keep getting is "No drives found, aborting installation. No valid cdrom device drivers selected". I have the drivers in the dir that I state in config.sys and autoexec.bat. I have put exactly the same name on the cdrom in both config.sys and autoexec.bat. The PC is a Packard-Bell Millennium XLE 1424. It has the cdrom connected to the motherboard, and the cdrom comes up as an idedrive in postboot self test. The thing is, the cdrom works in Win95. When I exit to DOS (under win95) the cd doesnt work. When I boot straight to DOS the cd doesnīt work, and I get the same error mess as stated above. Creative cd2422E is the model on the cdrom. I have downloaded DOS drivers from creative but I still get the same error mess. I have tried the masterboot disk with cd support, but it still gives me the same error mess. Please help, /Mattias

Why don't u put ur boot disk in the drive and restart the pc. then select "with cdrom support". u can now use your cdrom. reply here on further posts

There is a dosstart.bat file in the windows directory. It loads mscdex when you exit to dos so that the cdrom will work. The cdrom name there must be the same as in config.sys. Post back the contents of c:\config.sys, c:\autoexec.bat and c:\windows\dosstart.bat if you need additional help.

Here's the contents of c:\config.sys FILES=40 LASTDRIVE=Z DEVICE=C:\SBCD\DRV\SBIDE.SYS /D:MSCD001 /P:1e8,11 /V device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1) Country=046,850,C:\WINDOWS\COMMAND\country.sys c:\autoexec.bat C:\WINDOWS\AZTPNP.exe /A:ON /IDE:OFF C:\SBCD\DRV\MSCDEX.exe /D:MSCD001 /V /M:8 mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi) mode con codepage select=850 keyb sv,,C:\WINDOWS\COMMAND\keyboard.sys SET BLASTER=A240 I10 D3 T4 c:\windows\dosstart.bat C:\WINDOWS\AZTPNP.exe /A:ON /IDE:OFF [Packard Bell] c:\ctload c:\sbcd\drv\sbide.sys /D:MSCD001 /P:1E8,11 C:\WINDOWS\COMMAND\MSCDEX.exe /D:MSCD001 All help needed. Thanks. /Mattias

It looks OK. However you should remove the line: c:\ctload c:\sbcd\drv\sbide.sys /D:MSCD001 /P:1E8,11 from dosstart.bat That's the cdrom driver. It can only be loaded in config.sys. Also you might add the /V /M:8 to the mscdex line in dosstart.bat since it's in autoexec.bat also. The mscdex being loaded in autoexec.bat is coming from sbcd directory while the one in dosstart is coming from windows\command. Ideally they should both be loaded from windows\command or the one in autoexec.bat should be removed but you might leave that alone for now and see if the above changes help. If you exit to dos you can use the edit command to change the file as in: edit c:\windows\dosstart.bat Post back the results.

I changed it, but it didnīt resolve the problem. I started it in "plain" DOS by pressing F8 when the system boots and then I chosed "accept each line" (or whatever it is called) so that it steps through config.sys, autoexec.bat etc. Then I saw that while executing config.sys it reported an error while loading DEVICE=C:\SBCD\DRV\SBIDE.SYS /D:MSCD001 /P:1e8,11 /V. Thats when the error message "No drives found, aborting install" comes up. Correct me if Iīm wrong, but wouldnīt that be where it all begins? It cant load the cdrom driver, and then it cant execute mscdex as it should? So why would it say "No drives found, aborting installation. No valid cdrom device drivers selected" when trying to load the cdrom driver? /Mattias

The 'P:1e8,11' is telling the driver to look only at the port with IDE address 1e8 and use irq 11. Without specifying the port most drivers will search all the IDE ports for the cdrom. Your cdrom is probably not at that address. Your cdrom works in 95 because windows used it's own drivers which found the correct port. You should be able to remove the 'P:1e8,11' and probably the '/v' also. As I recall the '/v' stands for verbose, meaning a more detailed explanation is given on the screen as the drivers load. If you're using the newer drivers from creative, they should find the cdrom without the address being specified. If it still doesn't load the drivers you may have to install some different drivers. I have some generic drivers I can email you if you need them.