Im having trouble transferring files from Windows 10 to DOS. When I inserted the CD-RW -disk to my Win10 computer, I chose the "Mastered" option. However, when I burn some files on the CD and then try to read the directory in DOS, I get a CDR101 error?
Windows 10 defaults to UDF format which isn't compatible with dos and unfortunately the inbuilt burning program doesn't give you the option to change the format.
You'll need to install a burning program that supports ISO9660 Just about all of them do, including free ones like ImgBurn
I installed imgburn, chose ISO9660 as my format and burned the disc. No luck, still the same error. Then I tried making the files (which are just the installation files for GUS) into an ISO with AnyToISO, configured the ISO to be in ISO9660 format (not Joliet or UDF) and chose the file structure as DOS 8.3. Then I burned that ISO on to a disk and... No luck.
EDIT : What brand/model is the optical drive in your retro machine .
You did say you use the "same kind of disk" as for the Windows 98 installation, I just want to be 100% clear on what was used .
This is a longshot, but have you tried wiping and re-writing the actual Windows 98 installation disk that worked ? Maybe some of the disks in the box are marginal . Also, I imagine you are writing all theses disks at the same speed ?
Apparrently getting angry was the solution. I got so annoyed at the Abort, Retry, Fail choices that I kept hammering at the Retry and suddenly there it was, the directory listing. So it seems my drive is capable of reading CD-RW, but is just reeeeeally picky about when it chooses to do the reading.
I don't know why but failing CD drives always got me more angry then floppies back in the day.
Unless your going for period correct build I'd actually avoid a period drive, as darry said the earlier drives have trouble with burnt discs, plus general wear and tear on older drives.
DVD drives or even burner's will have better success rate with RW discs.
I'm actually getting ready to set up a network. I've order a 3C509B-C networking card and trying to find a decent tutorial on how to setup DOS - Windows 10 network. If you know of one, I'd love a link.
I use a DVD-ROM drive in my 486 test bench. Works fine. In every later build, I use a DVD-RW but don't use rewritable blanks. I make Norton Ghost images of fresh installs and specialty installs, so I need to be period incorrect. Lately, some of these drives have been failing, so when I see a NOS IDE beige DVD-RW drive for a good price ($20 shipped), I usually jump on it.
I'm not a technicaluser I just didn't know what to put. Replies continue belowRecommended for youconst urltitle=document.getElementsByTagName("title")[0];urlin = urltitle.innerHTML;urlout=urlin.substring(0, urlin.length - 11);console.log(urlout);new MoreLikeThis( text: [urlout], pubCodes: ["ENGCOM"], include: postTypes: ["post"], limit: 4 ,); RE: ERROR"CD101" when reinstalling windows 98 se smah (MIS)14 Apr 04 11:11Unfortunately, this sounds like it might be a bad CD media. See MSKB 272094 for troubleshooting tips. RE: ERROR"CD101" when reinstalling windows 98 se BionicJohn (TechnicalUser)14 Apr 04 13:27Hi, ism3c,
"A CDR-101 error is a code that is generally returned by your CD-ROM when it detects any problem with the drive electronics. This can be anything from a dirty lens on your CD-ROM drive to a major problem with the motor. The most important thing to remember is that a CDR-101 error does not necessarily mean your CD-ROM is broken. It simply means that the drive is having trouble reading the CD that's in the drive. You could see the error if the CD is scratched or damaged, for example.
If you have access to a CD-ROM cleaning kit, use it to clean the lens in your drive. A dirty lens, much like the lens on a camera, will have trouble getting accurate information if dust or other particles have settled on the surface. Even if you are not getting CDR-101 errors, it is a good practice to maintain your CD-ROM lens on a regular basis."
Iechyd da! John
Glannau Mersi, Lloegr. RE: ERROR"CD101" when reinstalling windows 98 se isokocons (TechnicalUser)14 Apr 04 14:16Run windows 98 setup from another CD, your CD is bad, sometimes, if you clean it or wipe the surface, it might be fine or alternatively copy the Win98 folder into your hard-disk and run setup from there. RE: ERROR"CD101" when reinstalling windows 98 se edfair (TechnicalUser)14 Apr 04 20:53Would suggest that you follow the advice to put the install stuff on the hard drive and install from there.
Fdisk and format it from the floppy then transfer the install stuff over thru DOS. Read errors in DOS get retried several times and errors are noted.
Once you have it across you move to the c: and the install area and run setup. Ed Fair
Give the wrong symptoms, get the wrong solutions. googletag.cmd.push(function() googletag.display('div-gpt-ad-1406030581151-2'); ); Red Flag This PostPlease let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.
CancelRed Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.
I have a set of 4 Dell Diagnostics floppies for my 10-year-old Inspiron 7500 laptop. The first floppy is bootable, and the diagnostics program is spread out on these 4 floppies. To run the Diagnostics, all 4 floppies have to be completely read in, only then can the hardware diagnostics be started. The boot floppy of the 4 floppies boots into Windows 95. [Version 4.00.950]
Because reading in 4 floppies is so time-consuming, the diagnostic floppies were hardly ever used. I have now repackaged/converted successfully these 4 floppies into both a bootable CD and a bootable DVD. The Dell Diagnostics now boot and load in about 40 seconds.
Creating a bootable CD/DVD from a single bootable floppy can be done quite easily with Nero Burning ROM. But creating a bootable CD from a set of floppies, one of of them being bootable, is a little more involved. Below are my notes on how I tackled this task, maybe these notes helps others facing a similar task, and there may be other better approaches. Of interest may be also the DOS DVD driver by Panasonic, which can be set to generic with the /C35 switch.
My goal is to eventually build a DVD that I can use to install various Windows 9X versions and install all of my software that I use. It would be very helpful to have functional System Commander tools included on the DVD as well.
Well, two floppies would fit into a single 2.88 MB diskette image. So you could image the 1st floppy with WinImage, then expand the image size to 2.88MB within WinImage, then inject the contents of the 2nd floppy into the image, save it as, say, SysCommBootDisk.IMA and use it as the standalone bootable floppy image for the creation of the CD/DVD, which would contain the installers. With some adjustments to the autoexec.bat and config.sys to add drivers for the CD/DVD, it should work, and be perhaps simpler than what Multibooter described, in that System Commander would be fully contained and launched directly from the el-Torito emulated floppy. Of course, if I were you, I'd use shsucdx, instead of mscdex... but I think this still is a matter where we agree to disagree.
There is even a "third" - still "no limits" way - using hard disk emulation at the CD, but a lot of oldish machines may have probelms with this kind of El-Torito emulation (and a few newish ones too).
And as suggested n times by now, both MagicISO and Nero are not the best choices available (mkisofs and imgburn are), with the first ones you don't really know WHAT they do, whilst with the second ones you have total control.
Actually I don't use them either, it was just an idea. I've always just used the bootable CD if I had problems. The reason I took interest in the disks is I wanted to be able to add the System Commander DOS tools to my DVD project without actually sacrificing my current boot image. I was trying to figure out what files were needed from the disks to be able to run System Commander from the DVD, sort of like how the required files for running Partition Magic and Drive Image in DOS are listed here.
3a8082e126