Mscd001 Device Driver For Mac
Ok I got this to work so everyone interested here goes: I loaded the standard generic cd rom driver in m y config.sys. This is the gscdrom.sys or something like that specified for like Gold Star cd drive. The page tells you how too load it in config.sys LOADHIGH=C: WINDOWS COMMAND MSCDEX.EXE /D:MSCD001 CONFIG.SYS: DEVICEHIGH=C: CD-ROM NECIDE.SYS /D:MSCD001 I did not bother using loadhi I don't have the memory set up or tried as of yet.
But anyway it looks like I have had success in moving all my stuff over. Thanks, Gordon.
It's a bit difficult to be clear from your post exactly how your system is configured, but if I understand correctly, of installations on three different hard drives in the same system, only the XP installation has access to the CD-ROM and CD writer? If this is correct, some general observations: To write CDs in Win98 you need suitable burning software, eg Nero or Roxio, no driver is required but the burning software must be able to work directly with the type of drive. XP has its own built-in burning software.
The names you've quoted are the type of names commonly assigned to MS-DOS CD-ROM drivers, which need to suit the brand of drive you're using. But for the vast majority of drives, these are not necessary, as Win98 has its own built-in CD-ROM drivers.
On the Win98 installations, are the CD drives appearing in the Device Manager? In Config.sys you should see something like this: DEVICEHIGH=C: CDROM CDDRV.SYS /D:xxxxxxx (Must agree with /D: in MSCDEX below! The D: parameter IS NOT the CDROM drive letter but a device name like 'MSCD0001' or 'OEMCD001') I have my own: DEVICEHIGH=C: CDROM CDDRV.SYS /D:Nick CDDRV.SYS is the driver. More times than not it uses OakCdRom.Sys as a generic driver.
If you need a special driver, this is where it goes. In Autoexec.bat you should see something like this: LH C: WINDOWS COMMAND MSCDEX.EXE /D:Nick Load in high memory the mscdex.exe and the matching device name. Windows 98 does not even need these drivers to load cdroms. If they are generic drivers, as mentioned, it will load automatically. There is almost always no need for autoexec.bat or config.sys unless you need some dos drivers for older sound cards and such. Platypus & Nick Grana: Thank for the responses. Platyus: Yes, only XP installation has access to the CD-ROM & CD-Writer.
The CD writer is Nero capable, when working OK, of writing CDs & DVDs (Sony DRU-800A). It also is not recognized. The CD drives do not appear in the Device Manager. In addition, the Primary and Secondary IDE controllers do no appear. I don't know if this is related to the CD ROM problem. Nick Grana: An error message 'oemcd001 driver not found during the boot up process. Config.sys Device = C: Windows HIMEM.sys Device = C: Windows EMM386.exe device = oakcdrom.sys/ emcd001 Autoexec.bat MSCDEX/D emcd001 /L In addition, Grisoft, Blaster, CTSYN, and Creative statements appeared.
For the other hard disk, the error message was the same except it said 'MSCD001 driver not found' during the boot up process. I did put ';' ( which will ignore the statement) in front of the statements containing OEMCD001.
As expected no change was noticable in the operation. Device = C: Windows HIMEM.sys Device = C: Windows EMM386.exe device = oakcdrom.sys/D:emcd001 Autoexec.bat MSCDEX/D:emcd001 /L You see from the above you are not directing the commands from the correct location unless mscdex.exe and oakcdrom reside in your root directory.
As with the HIMEM and EMM386, you see they are directed to go to Windows to find these files. Do a start/find/ on oakcdrom and mscdex.exe and highlight and select properties, This will show where files are located. Oakcdrom is probably located in c: cdrom Mscdex.exe is probably located in windows command The directions to these files have to be right.
Mscd001 Device Driver For Mac Windows 10
Hope this helps. In addition, the Primary and Secondary IDE controllers do no appear. I don't know if this is related to the CD ROM problem. This should not be related. These controllers should show up with nothing attached. To be sure and safe, check you drives ribbon cables and make sure the red line on side of cable is oriented with pin1 on the drive and the controller.
It's ok if these cables are backwards but only if both drive and controller are backwards so the red line will align with the other side of pin 1. Last edited by Nick Grana; December 17th, 2005 at 12:28 PM. There is no driver to download for 'oemcd001' As Nick stated oemcd001 is just a name chosen as a label, as a name for the cdrom, in fact if the entries matched in config.sys and autoexec.bat you could replace oemcd001 with MYNAME01 or whatever else you wanted to call it. The reason you are getting an error is probably because the autoexec and config are not correctly set up, but since you don't actually need them anyway. Look at this page for information on MSCDEX etc It states The MSCDEX.exe file is used in the autoexec.bat file to set the DOS CD-ROM parameters. It is always used in conjunction with a file in the config.sys file. Both the Autoexec.bat and the Config.sys files reside in the Root directory ( C: ) It goes on to say A typical entry is as follows: C: WINDOWS COMMAND MSCDEX.EXE /D:NCI000 And the matching (and required) file in the config.sys has the following format: DEVICE=C: CDROM SomeName.SYS /D:NCI000 Notice that in order for the above 2 files to properly work, the parameter (in this example the name 'NCI000') matches in both files.
This is required. Daftar harga jual microsoft office for mac 2016. Now in your case instead of NC1000 your system uses the label oemcd001. Also note in the example how it points to the correct location for MSCDEX and for SomeName.SYS which is in your case is oakcdrom.sys.
Now, assuming you even want to bother with all this which win98 does not need, you may want to rewrite the files to point correctly to wherever MSCDEX and oakcdrom.sys are in your system. On my system the correct paths for example would be device = C: WINDOWS COMMAND oakcdrom.SYS /D:MSCD000 and for the autoexec.bat file LH C: WINDOWS COMMAND MSCDEX.EXE /D:MSCD000 /L: Now how about actually disabling autoexec and config.sys?
You could either rename autoexec.bat and config.sys to say autoexec.old, config.old, or go to Start- run and type in MSCONFIG and press return. Then go to selective startup and unselect config and autoexec. This will rename the files as config.tsh and autoexec.tsh and create a new blank autoexec.bat. The only things I have placed in the autoexec file now is a line calling a boot time dos virus scanner and a couple of lines my ancient sound card needs. Last edited by General Winters; December 18th, 2005 at 02:56 AM. GW makes the same points I did. You do not need autoexec.bat or config.sys for windows.
In dos type ren autoexec.bat autoexec.sav And then type ren config.sys config.sav This will eliminate these two files but keep them handy if you need them by just renaming them back to their original name. But if you have the commands in autoexec.bat and config.sys and they are wrong, you will get an error. As with our examples, this is where you fail to accurately enter the command.
Config.sys Device = C: Windows HIMEM.sys Device = C: Windows EMM386.exe device = oakcdrom.sys/D:emcd001 Change last item to read: device=c: cdrom cdrom.sys /D:emcd001 (or any name) Autoexec.bat MSCDEX/D:emcd001 /L Change to read LH c: windows command mscdex.exe /D:emcd001 (or the name you choose above in config.sys) /L. The CD drives do not appear in the Device Manager. In addition, the Primary and Secondary IDE controllers do no(t) appear.I think this tells the story, chalonen. Have these two Win98 installations been set up on this system, or are they on hard drives that have come out of other computers? If it's the latter, those Windows installations will have driver setups intended for a different motherboard, and I suspect that is why this is happening. If this describes the situation, can you identify and obtain the correct Win98 motherboard drivers for the system you are putting the drives into? If you can, I suggest you try starting each Windows installation in Safe Mode, and in Device Manager, remove any 'phantom' instances of CD-ROM devices and IDE controllers.
Re-start, allow Windows to set up any generic drivers it feels moved to do, then install the motherboard drivers, and see if the IDE controllers and CD-ROM drives appear correctly in Device Manager. Windows may ask for the Windows 98 CD-ROM. Last edited by Platypus; December 19th, 2005 at 07:26 AM. General Winters, Nick Grana, & platypus: Thank you for the replys.
That was relieving in that oemcd001 and mscd001 are labels and not drivers. It's no wonder that I couldnt find them. To an amateur like me, to call out as being drivers in the error message is very misleading.
Now it has caused a new line of thinking for the problem solution. With 'rem' in front of config.sys and autoexec.bat files located in the msconfig section, where are device = C: windows command oakrom.sys/d:mscd000 and lh c: windows command mscdex.exe/d:mscd000/l statements placed? Platypus: These hard drives are used in the same CPU. Run MSCONFIG and unselect autoexec.bat and config.sys, ok out and reboot. See if you get any errors on the reboot then place any other lines as needed in the new (blank) autoexec.bat file. I don't have a config.sys file at all now and my autoexec file just contains 3 lines C: PROGRA1 GRISOFT AVGFRE1 BOOTUP.EXE SET BLASTER=A220 I2 D3 T4 LH C: WINDOWS ASP4DOS.COM The first is inserted automatically by my antivirus and the next two by my sound card. So, thats it, 3 lines and no worrysome calls to mscdex etc.
Why don't you try running Msconfig right now and see if all is ok after the reboot, hopefully no more errors referring to 'oemcd001 driver not found'. As to the other problems you mention, re IDE controllers not appearing etc, well thats a totally different problem, but solve the simple problem first! The Q's you ask are already explained above in quite detail. Having your cdrom drivers run in autoexec.bat and config.sys if for you to use the cdrom in dos. You don't need these commands in Windows only. You do need to see some controllers in device manager. I think you have a greater prob as Platypus described above.
Basics: When did this system last work properly? When did you start getting probs? What was done in between these times? Are we missing some vital info that may lead to a fix for this prob.? General Winters: I unckecked config.sys in msconfig and deleted the statement 'mscdex/d emcd001 in autoexec.bat.
I got an error message 'rem tshoot:msc.exe emcd001. I have the same 3 statements referring to the virus checker and sound blaster. Nick Grana: I been off and on this problem for about 3 months. As near as I can tell, I think the problem started occurring when I put another hard disk as a slave. I was trying to partition and put on XP and 98 on the the same hard drive. I've used Ghost, Acronis, and Partition Magic in the process without any success.