If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Device CDROM 0 Has a Bad Block
Normally, I wouldn't cross post but I believe this is a situation where
there might be multiple causes from the KBs I'm seeing and information I'm reading, so I thought I would profit from input from 3 groups. When I saw the bad block errors, I reflexly ran chkdsk r/ on each drive, and defragged the MFT and Paging file. I kept getting these errors. An error was detected on device \Device\CD ROM0 during a paging operation. The device\Device\CDRom0 has a bad block. I was getting an error when I put in a CD for Omni Page Pro 12 (no others). I had trouble installing two SPs that I remedied when a message from Event Viewer said there was a file missing called wizard32.dat. I had backed up the file, so I copied the file into the OPP folders and installation went fine. What concerns me are the causes for "bad block" and the difficulty in getting any information on this. I don't know because a CD-ROM is being referenced as well as the paging file whether this refers to a hardware or software issue. Also do the numbers for Event Errors--this one included 51, have any significance. Thanks, Chad Harris |
Ads |
#2
|
|||
|
|||
Device CDROM 0 Has a Bad Block
Cd is stuffed. Try cleaning it in case it's just grease from a finger. =
The code part (as there is an icon part, a menu part) of program files = become part of the swap file. As it never changes there is no point = writing it to the main swap file. It can be read back from the original = file. --=20 ---------------------------------------------------------- 'Not happy John! Defending our democracy', http://www.smh.com.au/articles/2004/...392635123.html "Chad Harris" wrote in message = ... Normally, I wouldn't cross post but I believe this is a situation = where=20 there might be multiple causes from the KBs I'm seeing and information = I'm=20 reading, so I thought I would profit from input from 3 groups. When = I saw=20 the bad block errors, I reflexly ran chkdsk r/ on each drive, and = defragged=20 the MFT and Paging file. I kept getting these errors. =20 =20 An error was detected on device \Device\CD ROM0 during a paging = operation. =20 The device\Device\CDRom0 has a bad block. =20 I was getting an error when I put in a CD for Omni Page Pro 12 (no = others).=20 I had trouble installing two SPs that I remedied when a message from = Event=20 Viewer said there was a file missing called wizard32.dat. I had = backed up=20 the file, so I copied the file into the OPP folders and installation = went=20 fine. =20 What concerns me are the causes for "bad block" and the difficulty in=20 getting any information on this. I don't know because a CD-ROM is = being=20 referenced as well as the paging file whether this refers to a = hardware or=20 software issue. =20 Also do the numbers for Event Errors--this one included 51, have any=20 significance. =20 Thanks, =20 Chad Harris =20 =20 =20 =20 |
#3
|
|||
|
|||
Device CDROM 0 Has a Bad Block
Cd is stuffed. Try cleaning it in case it's just grease from a finger. =
The code part (as there is an icon part, a menu part) of program files = become part of the swap file. As it never changes there is no point = writing it to the main swap file. It can be read back from the original = file. --=20 ---------------------------------------------------------- 'Not happy John! Defending our democracy', http://www.smh.com.au/articles/2004/...392635123.html "Chad Harris" wrote in message = ... Normally, I wouldn't cross post but I believe this is a situation = where=20 there might be multiple causes from the KBs I'm seeing and information = I'm=20 reading, so I thought I would profit from input from 3 groups. When = I saw=20 the bad block errors, I reflexly ran chkdsk r/ on each drive, and = defragged=20 the MFT and Paging file. I kept getting these errors. =20 =20 An error was detected on device \Device\CD ROM0 during a paging = operation. =20 The device\Device\CDRom0 has a bad block. =20 I was getting an error when I put in a CD for Omni Page Pro 12 (no = others).=20 I had trouble installing two SPs that I remedied when a message from = Event=20 Viewer said there was a file missing called wizard32.dat. I had = backed up=20 the file, so I copied the file into the OPP folders and installation = went=20 fine. =20 What concerns me are the causes for "bad block" and the difficulty in=20 getting any information on this. I don't know because a CD-ROM is = being=20 referenced as well as the paging file whether this refers to a = hardware or=20 software issue. =20 Also do the numbers for Event Errors--this one included 51, have any=20 significance. =20 Thanks, =20 Chad Harris =20 =20 =20 =20 |
#4
|
|||
|
|||
Device CDROM 0 Has a Bad Block
Cd is stuffed. Try cleaning it in case it's just grease from a finger. =
The code part (as there is an icon part, a menu part) of program files = become part of the swap file. As it never changes there is no point = writing it to the main swap file. It can be read back from the original = file. --=20 ---------------------------------------------------------- 'Not happy John! Defending our democracy', http://www.smh.com.au/articles/2004/...392635123.html "Chad Harris" wrote in message = ... Normally, I wouldn't cross post but I believe this is a situation = where=20 there might be multiple causes from the KBs I'm seeing and information = I'm=20 reading, so I thought I would profit from input from 3 groups. When = I saw=20 the bad block errors, I reflexly ran chkdsk r/ on each drive, and = defragged=20 the MFT and Paging file. I kept getting these errors. =20 =20 An error was detected on device \Device\CD ROM0 during a paging = operation. =20 The device\Device\CDRom0 has a bad block. =20 I was getting an error when I put in a CD for Omni Page Pro 12 (no = others).=20 I had trouble installing two SPs that I remedied when a message from = Event=20 Viewer said there was a file missing called wizard32.dat. I had = backed up=20 the file, so I copied the file into the OPP folders and installation = went=20 fine. =20 What concerns me are the causes for "bad block" and the difficulty in=20 getting any information on this. I don't know because a CD-ROM is = being=20 referenced as well as the paging file whether this refers to a = hardware or=20 software issue. =20 Also do the numbers for Event Errors--this one included 51, have any=20 significance. =20 Thanks, =20 Chad Harris =20 =20 =20 =20 |
#5
|
|||
|
|||
Device CDROM 0 Has a Bad Block
Cd is stuffed. Try cleaning it in case it's just grease from a finger. =
The code part (as there is an icon part, a menu part) of program files = become part of the swap file. As it never changes there is no point = writing it to the main swap file. It can be read back from the original = file. --=20 ---------------------------------------------------------- 'Not happy John! Defending our democracy', http://www.smh.com.au/articles/2004/...392635123.html "Chad Harris" wrote in message = ... Normally, I wouldn't cross post but I believe this is a situation = where=20 there might be multiple causes from the KBs I'm seeing and information = I'm=20 reading, so I thought I would profit from input from 3 groups. When = I saw=20 the bad block errors, I reflexly ran chkdsk r/ on each drive, and = defragged=20 the MFT and Paging file. I kept getting these errors. =20 =20 An error was detected on device \Device\CD ROM0 during a paging = operation. =20 The device\Device\CDRom0 has a bad block. =20 I was getting an error when I put in a CD for Omni Page Pro 12 (no = others).=20 I had trouble installing two SPs that I remedied when a message from = Event=20 Viewer said there was a file missing called wizard32.dat. I had = backed up=20 the file, so I copied the file into the OPP folders and installation = went=20 fine. =20 What concerns me are the causes for "bad block" and the difficulty in=20 getting any information on this. I don't know because a CD-ROM is = being=20 referenced as well as the paging file whether this refers to a = hardware or=20 software issue. =20 Also do the numbers for Event Errors--this one included 51, have any=20 significance. =20 Thanks, =20 Chad Harris =20 =20 =20 =20 |
#6
|
|||
|
|||
Device CDROM 0 Has a Bad Block
Cd is stuffed. Try cleaning it in case it's just grease from a finger. =
The code part (as there is an icon part, a menu part) of program files = become part of the swap file. As it never changes there is no point = writing it to the main swap file. It can be read back from the original = file. --=20 ---------------------------------------------------------- 'Not happy John! Defending our democracy', http://www.smh.com.au/articles/2004/...392635123.html "Chad Harris" wrote in message = ... Normally, I wouldn't cross post but I believe this is a situation = where=20 there might be multiple causes from the KBs I'm seeing and information = I'm=20 reading, so I thought I would profit from input from 3 groups. When = I saw=20 the bad block errors, I reflexly ran chkdsk r/ on each drive, and = defragged=20 the MFT and Paging file. I kept getting these errors. =20 =20 An error was detected on device \Device\CD ROM0 during a paging = operation. =20 The device\Device\CDRom0 has a bad block. =20 I was getting an error when I put in a CD for Omni Page Pro 12 (no = others).=20 I had trouble installing two SPs that I remedied when a message from = Event=20 Viewer said there was a file missing called wizard32.dat. I had = backed up=20 the file, so I copied the file into the OPP folders and installation = went=20 fine. =20 What concerns me are the causes for "bad block" and the difficulty in=20 getting any information on this. I don't know because a CD-ROM is = being=20 referenced as well as the paging file whether this refers to a = hardware or=20 software issue. =20 Also do the numbers for Event Errors--this one included 51, have any=20 significance. =20 Thanks, =20 Chad Harris =20 =20 =20 =20 |
#7
|
|||
|
|||
Device CDROM 0 Has a Bad Block
Cd is stuffed. Try cleaning it in case it's just grease from a finger. =
The code part (as there is an icon part, a menu part) of program files = become part of the swap file. As it never changes there is no point = writing it to the main swap file. It can be read back from the original = file. --=20 ---------------------------------------------------------- 'Not happy John! Defending our democracy', http://www.smh.com.au/articles/2004/...392635123.html "Chad Harris" wrote in message = ... Normally, I wouldn't cross post but I believe this is a situation = where=20 there might be multiple causes from the KBs I'm seeing and information = I'm=20 reading, so I thought I would profit from input from 3 groups. When = I saw=20 the bad block errors, I reflexly ran chkdsk r/ on each drive, and = defragged=20 the MFT and Paging file. I kept getting these errors. =20 =20 An error was detected on device \Device\CD ROM0 during a paging = operation. =20 The device\Device\CDRom0 has a bad block. =20 I was getting an error when I put in a CD for Omni Page Pro 12 (no = others).=20 I had trouble installing two SPs that I remedied when a message from = Event=20 Viewer said there was a file missing called wizard32.dat. I had = backed up=20 the file, so I copied the file into the OPP folders and installation = went=20 fine. =20 What concerns me are the causes for "bad block" and the difficulty in=20 getting any information on this. I don't know because a CD-ROM is = being=20 referenced as well as the paging file whether this refers to a = hardware or=20 software issue. =20 Also do the numbers for Event Errors--this one included 51, have any=20 significance. =20 Thanks, =20 Chad Harris =20 =20 =20 =20 |
#8
|
|||
|
|||
Device CDROM 0 Has a Bad Block
On Tue, 29 Jun 2004 00:07:40 -0400, Chad Harris wrote:
What concerns me are the causes for "bad block" and the difficulty in getting any information on this. I don't know because a CD-ROM is being referenced as well as the paging file whether this refers to a hardware or software issue. See my follow-up to the guy with the DVD problem in microsoft.public.windowsxp.hardware You can pick a up CD-ROM for $10 new so you might want to just replace the drive or you can upgrade to a DVD or CD-RW. -- Best Regards, Keith http://kilowatt-radio.org/ NW Oregon Radio Page Tried of Virus, Spyware, Adware and Popups? Switch To Mozilla Web Browser and Email http://mozilla.org/ Recommended by the US Government Computer Security Team http://www.cert.gov/ |
#9
|
|||
|
|||
Device CDROM 0 Has a Bad Block
Cd is stuffed. Try cleaning it in case it's just grease from a finger. =
The code part (as there is an icon part, a menu part) of program files = become part of the swap file. As it never changes there is no point = writing it to the main swap file. It can be read back from the original = file. --=20 ---------------------------------------------------------- 'Not happy John! Defending our democracy', http://www.smh.com.au/articles/2004/...392635123.html "Chad Harris" wrote in message = ... Normally, I wouldn't cross post but I believe this is a situation = where=20 there might be multiple causes from the KBs I'm seeing and information = I'm=20 reading, so I thought I would profit from input from 3 groups. When = I saw=20 the bad block errors, I reflexly ran chkdsk r/ on each drive, and = defragged=20 the MFT and Paging file. I kept getting these errors. =20 =20 An error was detected on device \Device\CD ROM0 during a paging = operation. =20 The device\Device\CDRom0 has a bad block. =20 I was getting an error when I put in a CD for Omni Page Pro 12 (no = others).=20 I had trouble installing two SPs that I remedied when a message from = Event=20 Viewer said there was a file missing called wizard32.dat. I had = backed up=20 the file, so I copied the file into the OPP folders and installation = went=20 fine. =20 What concerns me are the causes for "bad block" and the difficulty in=20 getting any information on this. I don't know because a CD-ROM is = being=20 referenced as well as the paging file whether this refers to a = hardware or=20 software issue. =20 Also do the numbers for Event Errors--this one included 51, have any=20 significance. =20 Thanks, =20 Chad Harris =20 =20 =20 =20 |
Thread Tools | |
Display Modes | |
|
|