Jump to content

Win XP SP2 and Blank CD Media


WhiteKnight77

Recommended Posts

Here is the deal, I tried to back up some files today and when inserting a blank CD-ROM, my rig crashed and I had to reboot via the reset switch. I tried with 2 different brands of media and starting Nero Burning ROM 5 with no disk in the rig and then inserting the disk after getting the program up, but it crashed either way.

I had no such problems with Win2000 and my current hardware (save for the HD and specs for rig in sig), yet with XP I am crashing. Has anyone else had problems with XP SP2 and blank media crashing their system? Anyone have any ideas what could be causing it?

I can use previously written disks without any problems, it is just blank media. :wacko:

Link to comment
Share on other sites

Hmm, I've installed CD burners on pretty much every system I've built, and haven't come across this problem. I usually use Roxio's Easy CD Creator, Nero or Window's default copying (based on Roxio's)

First thing I'd suggest is to turn off AutoPlay to see if it stops your system from crashing ... several ways to do it in XP here:

http://www.annoyances.org/exec/show/article03-018

Then I would check msconfig to see if your CD burning program turns on at startup and disable it.

Link to comment
Share on other sites

Hmmmm...I did mine on Thursday. If that update didn't fix it, then I'd say you have been victimized by Uncle Bill's SP2, and should consider uninstalling it and going back to SP1a and re-installing your updates. As I never use SP2 after having problems with it upon install, I never put it back on my PC, and in fact deleted it from my updates folder.

And quite frankly, the advertised benefits of SP2 are probably benefits you wouldn't use anyway, the main one being the updated XP firewall and the Security center, and I use that term very loosely where Winblows is concerned.

IMO, the hassles of SP2 are not justified by the benefits. There just weren't that many, bro.

My PC totally locked up and went nuts when I did an FFR and clean install of SP2. I then did another FFR and got rid of the downloaded file as well, and will not allow it on any PC in our network. So far, I have never had another issue, and only run SP1a, and update it about once a month unless a critical comes out that I deem worthy of a trip to the MS DL site. :thumbsup:

Edited by =UE=Phantom
Link to comment
Share on other sites

I'm sure a friend of mine told me he had problems with SP2 and his cdwriter not working once it was installed so there may be compatibility issues with SP2 and your drive, in which case Uncle Bill has screwed you. If I can get a hold of the guy I'll ask if he managed to resolve it.

Link to comment
Share on other sites

Doesn't sound good. Have you tried a fresh reformat yet?

Personally, 90% of the computers I've installed SP2 in have had no probs. The 10% I did have probs were fixed with a fresh reinstall. Don't know if this makes a diff, but they were all Intel systems (P3's and P4's)

I agree Windows Firewall and Security Center isn't great (I use the free version of ZoneAlarm myself) but one of the benefits of having SP2 is that it allows you to install all further critical patches available post SP2.

Link to comment
Share on other sites

I bit the bullet and updated to SP2 as well.

The "scared" feeling hasn't gone away yet.

On the upside, 99% of my applications have tested negative for problematic side-effects...yay for patches.

With regard to WK's topic, I haven't been able to duplicate it. Tried media from 3 different manufacturers.

Quite peculiar indeed.

Link to comment
Share on other sites

Hmm, tricky one WK..

Have you tried uninstall IDE drivers, reboot and re-install those?

If you have more than one drive on that IDE cable, have you tried to swap the master/slave, possibly remove that second drive and see if that works?

Properties>Recording must be checked but I believe that's done per default.

What mobo you got, bios update?

Edit: Read somewhere that there can be different types of blank media and some writers do while others don't recognize them.

Link to comment
Share on other sites

OK, here is the deal and what sorted everything out. I run 5 IDE drives, 3 optical and 2 HD. In order to run 3 optical drives, I had to install an IDE controller and that is where my burner was connected to by itself. The CD-ROM and DVD-ROM were on the motherboards secondary channel (the HDs are on the primary channel).

After putzing around in my system yesterday, Phantom suggested that maybe swapping the drives around would help. I didn't think so as the config I was using worked just fine with Win2000 Pro. Well, I swapped the drives around this morning and low and behold, Winblows didn't crash when I inserted a blank CD. I reconnected everything, buttoned everything back up and burned a test disk with some FS2004 terrain mesh. I even verified the data at the end and everything checked out fine. My burner is back in business.

I guess, if you have to run an IDE controller, burners need to be on the motherboards channels and not the controllers with SP2 now as shown above. What I don't get is why mess something up that worked before?

Link to comment
Share on other sites

It's like I told you and several others as well. XP is an entirely different animal. About the only similiarities between XP and 2K are SOME of the drivers.

It runs a different version of NTFS than 2K does, it has a different HAL than 2K does, and it is TOTALLY PnP, unlike 2K. You can't for the most part treat XP like 2K.

It never has liked optical drives on add in controllers, at least most that I worked with.

On the other hand, that controller will save you alot of headache when adding an HDD bigger than 137GB, because Winblows doesn't see them unless it's been fixed.

But anyway, glad ya got it working. And just so ya know, WK, I hooked my opticals up the same way you had yours and switched my HDD's to the Primary and Secondary mobo ports with Burner and DVD on the Promise controller, and it did the same to me, and I run SP1a, and will NOT go to SP2.

So it is an XP thing, not a service pack thing.

Edited by =UE=Phantom
Link to comment
Share on other sites

My new HD is a 200GB drive and Windows saw it all at startup, before installation.

I do know that Win2k SP4 can see drives bigger than 137GB. I am glad everything got worked out. I was about to go bald really,,,from yanking my hair out. ;)

Cool. Then that means they got that little issue squared away. I remember it was hell trying to install my new 250 and have Winblows see it as anything but a 137.

That WAS a limititation with XP. Glad it isn't anymore. :thumbsup:

Edited by =UE=Phantom
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...