Can't read dvd drive in DOS mode

[dencorso]

Short answer: No.

Long answer: ....

Short answer: Yes.

Long answer: ....

Fact: YMMV

@dencorso

Are you old enough to remember MEMMAKER?

http://www.easydos.com/memmaker.html

Sure. I have used ALGOL programs punched in cards. I have used QEMM. And I like a finely optimized DOS setup with UMBs. But, by now, as most of the time I'm in Windows (9x or XP), when I do want such a setup, I boot from a floppy.

I have banished EMM386.EXE from my config.sys some years ago and have no regrets whatever about it.

[jaclaz]

Sure. I have used ALGOL programs punched in cards.

I still have the advantage on you :

http://www.911cd.net/forums//index.php?sho...1702&st=123

I have banished EMM386.EXE from my config.sys some years ago and have no regrets whatever about it.

You should have more respect for something that in good and bad times, and with good and bad results, has accompanied us over the years.

Unrelated, but not much:

http://news.bbc.co.uk/2/hi/uk_news/2905953.stm

A:las poor floppy, I knew you well

Dan Garbutt, UK

Why, in my day....

http://tinyapps.org/blog/2007/02/index.html

...and we LIKED it!

jaclaz

[dencorso]

For what it's worth, here's a pointer (link) to a freeware program capable of opening and closing the CD door in DOS, and to another freeware one that does precisely that in Win, too, just in case. I find them pretty useful, so I think maybe so will you, too.

[MDGx]

If I may add to this already link cluttered thread...

CD/DVD Drivers 4 DOS guide:

http://www.mdgx.com/newtip1.htm#CDROM4

CD-ROM Name:

http://www.mdgx.com/newtip4.htm#CDROMNAME

Free CD/DVD Drivers for native DOS:

http://www.mdgx.com/drv.htm#CDR

where one can find VIDE-CDD.SYS, TEAC_CDI.SYS, XGCDROM.SYS and also SHCDX, SHSUCDX, NWCDEX + cloaked MSCDEX.

UIDE.SYS:

http://johnson.tmfc.net/dos/driver.html

also here:

http://www.mdgx.com/drv.htm#DTU

Loading drivers in upper memory using proper memory managers:

http://www.mdgx.com/newtip20.htm#9SMM

DOS 7 [Win9x] MEM/A/C/P Screens:

http://www.mdgx.com/mem7.htm

UMBPCI:

http://www.mdgx.com/umb.htm

And if any1 has loads of spare time on their hands, pls read MEMORY.TXT [part of W95-11D]:

http://www.mdgx.com/95.htm

HTH

[Fredledingue]

dencorso

Your system works!

I have successfuly copied one file from a dvd to the hd in DOS mode.

Thank you very much.

Next, I'll study the links MDGx gave...

[Hoko]

OK, Fred, I did some testing, and here's how it's done:

=============

Preparation Steps:

=============

1) Download DEVLOD7.ZIP (from the great Jim Kyle himself!), grab just DEVLOD.COM from inside it and drop it into the C:\WINDOWS folder.

2) Go to this page at cdrom-drivers.com, scroll down, complete and send the Re-Captcha, download Oakcdrom.sys and drop it into the C:\WINDOWS folder, too.

3) Go to this page, download SHCDX33E.ZIP, grab just SHCDX33E.COM from inside it and also drop it into the C:\WINDOWS folder.

4) Open notepad, copy the quoted text below to a text file, save it as DOSDVD.BAT and drop it into the C:\WINDOWS folder, too.

@ECHO OFF

C:\WINDOWS\DEVLOD C:\WINDOWS\OAKCDROM.SYS /D:MYDVDS

C:\WINDOWS\SHCDX33E /D:MYDVDS

==========

Normal Usage:

==========

1) Go to the Start Menu and "Restart in MS-DOS Mode"

2) As soon as you get to the prompt, type DOSDVD <Enter>

If all goes well, now both your DVD Recorders should be recognized and usable.

3) When you finish, you may simply turn off the computer with the power button, or reboot, or type EXIT <Enter> at the prompt, and this will result in a full reboot (because you've loaded resident DOS drivers, so you cannot just go back to Windows, without a full reboot). Notice that if you type EXIT <Enter> before issuing the DOSDVD <Enter>, in this case you get back to Windows without a full reboot, because no resident DOS drivers were loaded yet, so a full reboot was not needed.

4) If this procedure fails to work OK for you, my first guess is that your internal DVD-Recorders are not IDE, but SATA, and in this case, you'll have to substitute OAKCDROM.SYS for another apropriate driver (look for them at MDGx's).

I say this because you've never confirmed (nor denied) that your Recorders are in fact IDE. I'm guessing here.

5) Now, if you don't mind always having to do a full reboot on EXIT, or prefer not to have to remember running DOSDVD every time you "Restart in MS-DOS Mode", before being able to use the DVDs, then simply copy DOSDVD.BAT to DOSSTART.BAT (that also must be located in C:\WINDOWS), and the system will automagically load the DOS drivers for you, every time you "Restart in MS-DOS Mode".

N.B.: I'm also supposing that your %windir% folder is C:\WINDOWS, if this is not true, adjustments have to be made for it, too. I didn't use %windir% in the batch file, because this environment variable doesn't exist outside Windows, that is, in True DOS Mode.

HTH.

I have an IDE CDROM instead of a DVDROM. Would this work for me or would it have to be changed?

Edited May 5, 2013 by Hoko

[dencorso]

I have an IDE CDROM instead of a DVDROM. Would this work for me or would it have to be changed?

No matter... it should just work.

[Hoko]

3) Download SHCDX33F.ZIP, grab just SHCDX33F.COM from inside it and also drop it into the C:\WINDOWS folder.

Maybe I'm not looking in the right place but the only file I see for download is SHCDX33F.ZIP

[LoneCrusader]

Maybe I'm not looking in the right place but the only file I see for download is SHCDX33F.ZIP

It's probably been updated since dencorso made that post. The new version should be fine.

You actually do not NEED that file. MSCDEX.EXE is provided with Windows and should work for your CDROM.

There is some disagreement about MSCDEX vs. SHSUCDX among myself, dencorso, and jaclaz. I prefer to use MSCDEX, they prefer SHSUCDX. But either will work for your project, so it's for you to decide.

[Hoko]

@ECHO OFF

C:\WINDOWS\DEVLOD C:\WINDOWS\OAKCDROM.SYS /D:MYDVDS

C:\WINDOWS\SHCDX33E /D:MYDVDS

Are there any spaces in this statement? Also I'm going to have to change to SHCDX33F since that file has been updated. I'll be glad when my network card comes in this week and be able to download directly to my Win95 computer instead of shuffling disks.

Edited May 6, 2013 by Hoko

[jaclaz]

There is some disagreement about MSCDEX vs. SHSUCDX among myself, dencorso, and jaclaz. I prefer to use MSCDEX, they prefer SHSUCDX. But either will work for your project, so it's for you to decide.

Actually there is NO disagreement whatever.

MSCDEX is "crystalized" in time to it's last release, which was BEFORE a number of changes happened to the ISO 9660 standard (and it's integrations)

SHSUCDX is continuously updated

If you are in the usual nostalgia trip and want to - say - explore an AOL CD :

http://www.tomshardware.com/news/america-online-aol-cd-discs,11854.html

MSCDEX is more than OK .

If you want to access data written to a CD (or DVD) more recently it is possible that MSCDEX will choke on it.

As said elsewhere :

I won't get involved in a flame war about MSCDEX.EXE vs. SHSUCDX.EXE or mkisofs vs magiciso or whatever, they all seem to me like King Kong vs. Godzilla (and JFYI, the dinosaur can get rid of that grown up chimpanzee with one hand tied behind his back, anytime )

jaclaz

[DougB]

Actually there is NO disagreement whatever.

MSCDEX is "crystalized" in time to it's last release, which was BEFORE a number of changes happened to the ISO 9660 standard (and it's integrations)

SHSUCDX is continuously updated

Not to mention the memory footprint. On my system:

   8,848k  SHCDX33F
  32,384k  MSCDEX v2.25 (from MS-DOS v7.1)

- Doug B.

[jaclaz]

Not to mention the memory footprint.

That is Rule #3 .

Rules of the SHSUCDX club:

#1 You DON'T TALK about the SHSUCDX club.

#2 You DON'T TALK about the SHSUCDX club.

#3 You DON'T TALK about memory footprint!

Ooops.

jaclaz

[LoneCrusader]

Actually there is NO disagreement whatever.

MSCDEX is "crystalized" in time to it's last release, which was BEFORE a number of changes happened to the ISO 9660 standard (and it's integrations)

SHSUCDX is continuously updated

If you are in the usual nostalgia trip and want to - say - explore an AOL CD :

http://www.tomshardware.com/news/america-online-aol-cd-discs,11854.html

MSCDEX is more than OK .

If you want to access data written to a CD (or DVD) more recently it is possible that MSCDEX will choke on it.

,,,

Well, I don't see how you can say there is no "disagreement" when we still each recommend the opposite program.

However I do agree there is no reason to debate it. But since you "quoted for the record," so must I.

...

MSCDEX has NEVER ONCE failed to work for reading ANY OPTICAL DISC that I have wanted to use.

I see no reason to change it simply based on someone saying "SHSUCDX is better."

...

[dencorso]

Well, I don't see how you can say there is no "disagreement" when we still each recommend the opposite program.

However I do agree there is no reason to debate it. But since you "quoted for the record," so must I.

And I! I refuse to be the only to resist quoting that thread, although I too see no need to debate the issue!

[...] MSCDEX has NEVER ONCE failed to work for reading ANY OPTICAL DISC that I have wanted to use. [...]

But it will, rest assured it will!

And while I agree with jaclaz:

I won't get involved in a flame war about MSCDEX.EXE vs. SHSUCDX.EXE

and I much less want to be the starter of such a flame war, I'll say that the reason for recommending quite strongly SHSUCDX is simply that it was written to be much more forgiving than MSCDEX, so that it can read many optical media that are beyond MSCDEX strict format requirements. Even if you don't feel like testing it right now, do have a copy of it in your toolbox, because, sooner or later, you'll find it quite handy. And because it's open source and very well documented (although you'd have to gather at least three versions to have access to all existing documentation: John McCoy's 1.4b, Jason Hood's 3.02 ...

... and Jack Ellis' 3.03F, which is the current one), confirming it remains supported and actively developed.