CDR101 problem installing Windows XP Pro with Matshita DVD..

[adam]

My ASUS N61JQ laptop is running Ubuntu 10.04.
As far as I can tell from VirtualBox, this system has
a Matshita DVD-RAM UJ890AS optical drive,
which keeps giving the following message ...

"CDR101: Not ready reading drive R
Abort, Retry, Fail?"

during ...

1) setup of Windows XP Pro (with MSDN CD) guest OS via VirtualBox; and
2) xcopy of MSDN CD contents to C: drive
[xcopy is an attempt to workaround the Windows XP setup problem]

AFAIK, files being processed when this error message occurs are ...

GDIPLUS.CAT 7,236 bytes
gdiplus.dll 1,700,352 bytes
GDIPLUS.MAN 391 bytes

in the \english\winxp\pro\i386\asms\1000\msft\windows\gdiplus directory.
There may be other files that can cause this error message.

Any ideas?

[adam]

"T.C." <Devil505@spamfence.net> wrote in message
news:ffbmm6l88elokn1r9jt70qv80b0qbo40q7@4ax.com...
> > My ASUS N61JQ laptop is running Ubuntu 10.04.
> > As far as I can tell from VirtualBox, this system has
> > a Matshita DVD-RAM UJ890AS optical drive,
> > which keeps giving the following message ...
> >
> > "CDR101: Not ready reading drive R
> > Abort, Retry, Fail?"
> >
> > during ...
> >
> > 1) setup of Windows XP Pro (with MSDN CD) guest OS via VirtualBox; and
> > 2) xcopy of MSDN CD contents to C: drive
> > [xcopy is an attempt to workaround the Windows XP setup problem]
> >
> > AFAIK, files being processed when this error message occurs are ...
> >
> > GDIPLUS.CAT 7,236 bytes
> > gdiplus.dll 1,700,352 bytes
> > GDIPLUS.MAN 391 bytes
> >
> > in the \english\winxp\pro\i386\asms\1000\msft\windows\gdiplus directory.
> > There may be other files that can cause this error message.
> >
> > Any ideas?
>
> You've tried the obvious already?, i.e.:
> - the MSDN CD is readable in other drives?
> - the UJ890AS is reading other CDs without problems?
>
> ...as a WAG of mine I'd say that either the CD is scratchy/ dirty or
> the DVD drive is starting to fail (most often due to dirty optics) -
> or both in conjunction - if you suspect the CD to be too scratchy you
> could try to make a copy of it using another CD/ DVD-writer and use
> that one for installing...
>
> Cleaning the drive optics can help (using compressed air), but the
> more the drive has been in use, the more it usually gets dirty -
> unfortunately quite often in a way that can't be cleaned that easily,
> as one of the major problems with time is dust being "baked" to the
> lenses by the laser - a problem that would require dismantling of the
> optics (not THAT difficult), cleaning and reassembling (quite
> difficult as the lenses usually have to be readjusted again)...
>
> T.C.


Thanks!! Please reference my response to Paul.
Also, I did copy the MSDN CD contents to my HDD then
burned a new CD. Similar problem. This leads me to
believe that Microsoft sent me a bad CD.

[adam]

"Paul" <nospam@needed.com> wrote in message
news:ikgr5u$m6u$1@news.eternal-september.org...
> Adam wrote:
> > My ASUS N61JQ laptop is running Ubuntu 10.04.
> > As far as I can tell from VirtualBox, this system has
> > a Matshita DVD-RAM UJ890AS optical drive,
> > which keeps giving the following message ...
> >
> > "CDR101: Not ready reading drive R
> > Abort, Retry, Fail?"
> >
> > during ...
> >
> > 1) setup of Windows XP Pro (with MSDN CD) guest OS via VirtualBox; and
> > 2) xcopy of MSDN CD contents to C: drive
> > [xcopy is an attempt to workaround the Windows XP setup problem]
> >
> > AFAIK, files being processed when this error message occurs are ...
> >
> > GDIPLUS.CAT 7,236 bytes
> > gdiplus.dll 1,700,352 bytes
> > GDIPLUS.MAN 391 bytes
> >
> > in the \english\winxp\pro\i386\asms\1000\msft\windows\gdiplus directory.
> > There may be other files that can cause this error message.
> >
> > Any ideas?
> >
> >
>
> I have an MSDOS boot floppy prepared using a Win98SE system.
>
> I did a "dd" and dumped the 1440KB of info to a file on my
> hard drive. By searching the image with a hex editor, I can
> see things like this.
>
> CDR101: Not ready
> CDR102: EMS memory no longer valid
> CDR103: CDROM not High Sierra or ISO-9660 format
> CDR104: Door open
>
> In other words, those seem to be "error numbers", rather
> than a model number of an optical drive. One web page, suggested
> the source is mscdex.exe driver.
>
> Paul
>


Thanks!! Like you, I thought the problem may be due to
the driver since the Win98SE bootdisk and driver are old but
the hardware is relatively new. So, I tried to create the VM on
a dinosaur Win98SE system (yeah, old systems still come in handy).
Anyways, similar problem occurs on the old system as well so
I no longer think the driver is the problem.
Like John, I now think the problem may be due to the CD media.

I just called Microsoft regarding the bad MSDN media,
they said they can't replace it since the MSDN subscription has expired.
<sigh>

Anyone know where I can download the ISO for Windows XP Pro (32-bit)?

[adam]

"Paul" <nospam@needed.com> wrote in message
news:ikgr5u$m6u$1@news.eternal-september.org...
> Adam wrote:
> > My ASUS N61JQ laptop is running Ubuntu 10.04.
> > As far as I can tell from VirtualBox, this system has
> > a Matshita DVD-RAM UJ890AS optical drive,
> > which keeps giving the following message ...
> >
> > "CDR101: Not ready reading drive R
> > Abort, Retry, Fail?"
> >
> > during ...
> >
> > 1) setup of Windows XP Pro (with MSDN CD) guest OS via VirtualBox; and
> > 2) xcopy of MSDN CD contents to C: drive
> > [xcopy is an attempt to workaround the Windows XP setup problem]
> >
> > AFAIK, files being processed when this error message occurs are ...
> >
> > GDIPLUS.CAT 7,236 bytes
> > gdiplus.dll 1,700,352 bytes
> > GDIPLUS.MAN 391 bytes
> >
> > in the \english\winxp\pro\i386\asms\1000\msft\windows\gdiplus directory.
> > There may be other files that can cause this error message.
> >
> > Any ideas?
> >
> >
>
> I have an MSDOS boot floppy prepared using a Win98SE system.
>
> I did a "dd" and dumped the 1440KB of info to a file on my
> hard drive. By searching the image with a hex editor, I can
> see things like this.
>
> CDR101: Not ready
> CDR102: EMS memory no longer valid
> CDR103: CDROM not High Sierra or ISO-9660 format
> CDR104: Door open
>
> In other words, those seem to be "error numbers", rather
> than a model number of an optical drive. One web page, suggested
> the source is mscdex.exe driver.
>
> Paul
>


Thanks!! Like you, I thought the problem may be due to
the driver since the Win98SE bootdisk and driver are old but
the hardware is relatively new. So, I tried to create the VM on
a dinosaur Win98SE system (yeah, old systems still come in handy).
Anyways, similar problem occurs on the old system as well so
I no longer think the driver is the problem.
Like John, I now think the problem may be due to the CD media.

I just called Microsoft regarding the bad MSDN media,
they said they can't replace it since the MSDN subscription has expired.
<sigh>

Anyone know where I can download the ISO for Windows XP Pro (32-bit)?

[mike s.]

In article <ikh07n$irr$1@news.eternal-september.org>,
Adam <adam@no_thanks.com> wrote:
>
>"T.C." <Devil505@spamfence.net> wrote in message
>news:ffbmm6l88elokn1r9jt70qv80b0qbo40q7@4ax.com...
>> > My ASUS N61JQ laptop is running Ubuntu 10.04.
>> > As far as I can tell from VirtualBox, this system has
>> > a Matshita DVD-RAM UJ890AS optical drive,
>> > which keeps giving the following message ...
>> >
>> > "CDR101: Not ready reading drive R
>> > Abort, Retry, Fail?"
>> >
>> > during ...
>> >
>> > 1) setup of Windows XP Pro (with MSDN CD) guest OS via VirtualBox; and
>> > 2) xcopy of MSDN CD contents to C: drive
>> > [xcopy is an attempt to workaround the Windows XP setup problem]
>> >
>> > AFAIK, files being processed when this error message occurs are ...
>> >
>> > GDIPLUS.CAT 7,236 bytes
>> > gdiplus.dll 1,700,352 bytes
>> > GDIPLUS.MAN 391 bytes
>> >
>> > in the \english\winxp\pro\i386\asms\1000\msft\windows\gdiplus directory.
>> > There may be other files that can cause this error message.
>> >
>> > Any ideas?
>>
>> You've tried the obvious already?, i.e.:
>> - the MSDN CD is readable in other drives?
>> - the UJ890AS is reading other CDs without problems?
>>
>> ...as a WAG of mine I'd say that either the CD is scratchy/ dirty or
>> the DVD drive is starting to fail (most often due to dirty optics) -
>> or both in conjunction - if you suspect the CD to be too scratchy you
>> could try to make a copy of it using another CD/ DVD-writer and use
>> that one for installing...
>>
>> Cleaning the drive optics can help (using compressed air), but the
>> more the drive has been in use, the more it usually gets dirty -
>> unfortunately quite often in a way that can't be cleaned that easily,
>> as one of the major problems with time is dust being "baked" to the
>> lenses by the laser - a problem that would require dismantling of the
>> optics (not THAT difficult), cleaning and reassembling (quite
>> difficult as the lenses usually have to be readjusted again)...
>>
>> T.C.
>
>
>Thanks!! Please reference my response to Paul.
>Also, I did copy the MSDN CD contents to my HDD then
>burned a new CD. Similar problem. This leads me to
>believe that Microsoft sent me a bad CD.

Check the CD (or the ISO) with the Microsoft crc.exe utility. IIRC the MS
ISO files have an embedded CRC verification checksum which the MS utility
can use to verify the integrity.

[tim meddick]

The cause of the error messages is one of dust or microscopic damage to the
surface of the cd-rom. The problem is the cd/dvd's read-head laser cannot
correctly interpret the section[s] of the disk on which the "problem" files
reside.

Thus you get such error messages as ; "Not ready reading drive X
Abort, Retry, Fail?"

You could try rinsing the cd-rom in a very weak solution of warm water and
washing-up detergent, then drying off with tissue paper.

But, quite often, the problem is caused by anything from microscopic to
large, visible scratches or inconsistencies on the disk's surface.

[Obviously] the Windows XP installation cd-rom, is till fully copyrighted
and protected by Microsoft, and, as a currently supported Microsoft
Operating System (SP3), is NOT classed as "orphaned" software. Therefore,
Windows XP is not available anywhere to download - legally.

Your idea of transferring the entire contents of the cd-rom into a folder
/sub-folder structure on your hard-drive, is a brilliant one - this is how
I eventually solved the self-same problem.

It's possible that the installation will complete without the odd missing
file (depending on what, and how important, the missing file[s] may
actually be).

However, there's a very good chance of you being able to get hold of
missing (corrupted) files as a download...

I know you can download [gdiplus.dll] by following the link below :
http://www.dll-files.com/dllindex/dll-f ... ml?gdiplus

....and possibly, you can find the others on the internet by doing a general
search for them, cross-referenced with the terms "XP SP3" and
"download"....

Hope this helps....

==

Cheers, Tim Meddick, Peckham, London.




"Adam" <adam@no_thanks.com> wrote in message
news:ikgvq8$eml$1@news.eternal-september.org...
>
> "Paul" <nospam@needed.com> wrote in message
> news:ikgr5u$m6u$1@news.eternal-september.org...
>> Adam wrote:
>> > My ASUS N61JQ laptop is running Ubuntu 10.04.
>> > As far as I can tell from VirtualBox, this system has
>> > a Matshita DVD-RAM UJ890AS optical drive,
>> > which keeps giving the following message ...
>> >
>> > "CDR101: Not ready reading drive R
>> > Abort, Retry, Fail?"
>> >
>> > during ...
>> >
>> > 1) setup of Windows XP Pro (with MSDN CD) guest OS via VirtualBox;
>> > and
>> > 2) xcopy of MSDN CD contents to C: drive
>> > [xcopy is an attempt to workaround the Windows XP setup
>> > problem]
>> >
>> > AFAIK, files being processed when this error message occurs are ...
>> >
>> > GDIPLUS.CAT 7,236 bytes
>> > gdiplus.dll 1,700,352 bytes
>> > GDIPLUS.MAN 391 bytes
>> >
>> > in the \english\winxp\pro\i386\asms\1000\msft\windows\gdiplus
>> > directory.
>> > There may be other files that can cause this error message.
>> >
>> > Any ideas?
>> >
>> >
>>
>> I have an MSDOS boot floppy prepared using a Win98SE system.
>>
>> I did a "dd" and dumped the 1440KB of info to a file on my
>> hard drive. By searching the image with a hex editor, I can
>> see things like this.
>>
>> CDR101: Not ready
>> CDR102: EMS memory no longer valid
>> CDR103: CDROM not High Sierra or ISO-9660 format
>> CDR104: Door open
>>
>> In other words, those seem to be "error numbers", rather
>> than a model number of an optical drive. One web page, suggested
>> the source is mscdex.exe driver.
>>
>> Paul
>>
>
>
> Thanks!! Like you, I thought the problem may be due to
> the driver since the Win98SE bootdisk and driver are old but
> the hardware is relatively new. So, I tried to create the VM on
> a dinosaur Win98SE system (yeah, old systems still come in handy).
> Anyways, similar problem occurs on the old system as well so
> I no longer think the driver is the problem.
> Like John, I now think the problem may be due to the CD media.
>
> I just called Microsoft regarding the bad MSDN media,
> they said they can't replace it since the MSDN subscription has expired.
> <sigh>
>
> Anyone know where I can download the ISO for Windows XP Pro (32-bit)?
>
>
>

[tim meddick]

As I wrote in my previous post : "Windows XP installation cd-rom, is still
fully copyrighted
and protected by Microsoft" so is not available to legally download.

However, some files on the XP Service Pack 3 cd-rom (ISO download) MAY
provide suitable replacements for any missing files after copying what you
can of your original cd-rom to a folder on your hard-drive, external USB
drive or removable "pen" drive (memory "stick").

The XP Service Pack 3 cd-rom is available as an ISO-file download from
Microsoft at :

Windows XP Service Pack 3 - ISO-9660 CD Image File (544.9MB)
http://www.microsoft.com/downloads/deta ... laylang=en

If I got it wrong, and you are only installing XP SP2, then here is the
link to download the SP2 Installation "package" executable :

Windows XP Service Pack 2 Network Installation Package for IT Professionals
and Developers
http://www.microsoft.com/DOWNLOADS/deta ... 368d3cdb5a

Because it's not an ISO-file, you will have to use a utility such as
"WinZip" to extract all the files from within the executable
(self-extracting cabinet file) to a folder, and then copy the "missing"
files to the folder where you copied the files from the Installation disk.

*NB The Service Pack 3 ISO download will NOT work as a complete XP Install
disk!
You will have to copy what you can of your OWN Installation cd-rom to a
folder on your hard-drive and then "fill in the gaps" with files from
either the SP3 ISO-file or the SP2 Install *.EXE (exacted with WinZip).

As long as the folder you copy all the XP Installation files to is on a FAT
/ FAT32 drive, you can boot your PC with a simple DOS boot-disk and install
XP Pro by executing the file :

WINNT.EXE

==

Cheers, Tim Meddick, Peckham, London.

[tester]

I would use Microsoft's setup disks to speed up the installation:

<http://support.microsoft.com/kb/310994>

hth


Paul wrote:

> It's possible to install WinXP, without booting the CD. In fact,
> the very reason I have that floppy diskette in the first place, is
> it was used to install WinXP. The same WinXP being used to type
> this message.
>
> The technique is:
>
> 1) Create two partitions on the hard drive. C: is first. D: is second.
> You install to C:. You copy i386 and the ~5000 files inside it, to
> D:. Now, you have an empty C:, and D:\i386. I made both of them
> FAT32 partitions, because that's what a Win98 MSDOS floppy can read
> You can convert C: to NTFS later if you want.
>
> If you screw up the details on this step, the install goes on the
> wrong partition. Ask me how I know that It took me more than one
> try, to get this right.
>
> 2) Prepare an MSDOS floppy to boot the target computer. It should
> include SMARTDRV, which is a caching driver of some sort. Without
> it, the install could take a few hours longer than necessary, but
> it isn't absolutely essential. If you're patient, perhaps a vanilla
> MSDOS boot floppy would work. If you can't make one, you might get
> one from a site like bootdisk.com . Mine originated from a Win98
> system, long ago.
>
> 3) This is one of the control files on my floppy. There are various
> CD driver files available as well. mscdex may handle some drive
> types, but for some reason I also have a copy of xcdrom on my floppy
> as well. I used to know what all this stuff meant. The SMARTDRV
> parameters are cranked up, in an attempt by me to see whether allocating
> a larger cache, helped speed up the install. It doesn't. SMARTDRV
> has some sort of issue with handling memory, in that it gets slow
> some times. I didn't manage to fix that. It's not possible to
> set the memory allocation high enough, that it doesn't "run out"
> and have to fumble around.
>
> AUTOEXEC.BAT
>
> mscdex /D:MSCD001 /L:R
> pause
> a:\smartdrv.exe /V 32768 32768 /E:32768
>
> 4) This is the second control file. The question mark after DEVICE causes
> the execution of this file to pause after each line. I run it that
> way, so I can watch what happens. It took me the better part of a day,
> to learn enough about MSDOS, to get this stinking thing to work
> I had a resource conflict as well, and it took many reboots until
> I got the correct values by trial and error.
>
> CONFIG.SYS
>
> DEVICE?=HIMEM.SYS /TESTMEM:OFF
> ;DEVICE?=EMM386.EXE /RAM
> DEVICE?=EMM386.EXE NOEMS X=A000-CFFF <--- workaround for
> motherboard issue
> DEVICE?=XCDROM.SYS /D:MSCD001
> FILES=20
> BUFFERS=20
> DOS=HIGH,UMB
> STACKS=9,256
>
> 5) Once booted, A:, C:, and D: should be accessible. Now, change
> directory to
> D:\i386. In there, are two setup files. One runs in Windows, one runs
> in DOS.
> (WINNT32.EXE and WINNT.EXE ?) Using one of those EXE files, you can
> "kick off"
> the installation. The first stage will involve the setup program
> copying the
> files from D:\i386 over to C:. SMARTDRV speeds up the copy (where the
> word
> "speed" means sluggish).
>