XP Bug still in W7, a unreadable disk brings the whole system down.

FreeStream · 29 Jul 2009 at 20:28

Why is MS incapable of making a system that isn't brought to a standstill because it can't read a disk?

And people are paying £100+ for this? lol.

Anyway, I shall soldier on. This disk must be read.

Caged · 29 Jul 2009 at 20:34

This thread is both detailed and useful. Thanks for sharing!

FreeStream · 29 Jul 2009 at 20:36

Well now I have some more details for you.

OS X is reading it (albeit slowly - but I can use the system).

For your information is a Medal of Honor Spearhead disk that has been through the wars.

I just thought it was shocking that such a simple operation such as... installing from a dodgy disk could bugger a system up.

Edit: And nor can IMGburn read from one SATA DVD drive while installing from the other. Oh I do despair

Caged · 29 Jul 2009 at 20:38

I've never had Windows taken down by a dodgy disk. Ever.

But anecdotal evidence is fun, remember it wasn't that long ago that Mac OS X losing the connection to a networked resource would bring Finder crumbling to its knees.

You're better off trying to polish the disc up a bit before trying to get a PC to read it. There's various guides around the 'net.

Dano · 29 Jul 2009 at 20:48

Caged said:
I've never had Windows taken down by a dodgy disk. Ever.

I have, numerous times. Want me to film it next time it happens?

Caged · 29 Jul 2009 at 20:51

Only if that would make you feel better, I'll believe you either way.

Spyhop · 29 Jul 2009 at 21:07

Speaking of ever-present annoyances..

Will Windows Explorer ever stop taking it upon itself to occasionally display folders in one of the many retarded custom views?

An "I want to use this one view, with these columns, at these sizes, for every folder. Every ****ing one of them. Forever. No exceptions. I'm being serious, here. Every ****ing one." option that works would be appreciated.

neil_g · 29 Jul 2009 at 21:14

cant say ive ever had this problem either to be honest.. it makes a hell of a racket before you can eject the disk but its never crashed everything..

Elfmeister. · 29 Jul 2009 at 21:17

wush said:
Speaking of ever-present annoyances..

Will Windows Explorer ever stop taking it upon itself to occasionally display folders in one of the many retarded custom views?

An "I want to use this one view, with these columns, at these sizes, for every folder. Every ****ing one of them. Forever. No exceptions. I'm being serious, here. Every ****ing one." option that works would be appreciated.

Errm I'm pretty sure this can be sorted in folder options! and OP I think its time you got a new DVD Rom.

Spyhop · 29 Jul 2009 at 21:19

That option mostly works, but does not hold 100% of the time.

There was some freeware add-on for Vista that tried to solve the problem. Can't remember the name.

james.miller · 29 Jul 2009 at 21:22

yeah folder views are still a pain at times. ive no idea why, its one of those things MS just havent seemed to get to grips with.

FreeStream · 29 Jul 2009 at 21:28

Elfmeister. said:
Errm I'm pretty sure this can be sorted in folder options! and OP I think its time you got a new DVD Rom.

I will order a new one, however at the moment I've thankfully found my original backups of these disks. So thankfully I can install as normal but use the damage disk to do its disk check.

So im sorted

Caged said:
I
But anecdotal evidence is fun, remember it wasn't that long ago that Mac OS X losing the connection to a networked resource would bring Finder crumbling to its knees.

You're better off trying to polish the disc up a bit before trying to get a PC to read it. There's various guides around the 'net.

OS X has had that bug fixed now. Few years later for XP...

Aod · 30 Jul 2009 at 02:58

in windows, access to Disk drives is coupled directly to the OS's I/O system. this allows for faster and direct access, in OSX it's abstracted from the OS by a transfer layer, which means that intensive disk access will have a greater impact on system performance.

ShakenNstirred · 30 Jul 2009 at 06:15

cant say i`ve had my system fall to it knees because it cant read a disk

Nick1881 · 30 Jul 2009 at 08:39

Don't try to read dodgy disks, simples

NathanE · 30 Jul 2009 at 08:47

This really comes down to your motherboard chipset drivers. Ever since about 2001-2002, the Intel Chipset Drivers haven't had this problem due to improvements they made back then during the XP/2000 era.

If you have this problem then chances are you either don't have any chipset drivers installed or, perhaps, nForce/VIA/whatever are crap?

Vista's handling of 'bad drives' was made even better because that OS implemented Cancellable I/O. And Windows Explorer was improved to make use of it. So if a drive is being annoying or slow, a simple click of the Cancel button will sort it out. And that click of the Cancel button will be instantaneous - no waiting around.

Kainz · 30 Jul 2009 at 09:30

I would have this issue back with XP a lot, when I would read old dvdr's. I have had Vista x64 lockup during the read of a bad one, but the moment I hit the eject button - the system would resume from it's locked state without problem.

It is a long standing device driver issue more than anything, rather than windows being at fault. I've got 12 HD's tied to my system now because I just hate backing stuff up to cd/dvd.

Burnsy2023 · 30 Jul 2009 at 10:17

NathanE said:
This really comes down to your motherboard chipset drivers. Ever since about 2001-2002, the Intel Chipset Drivers haven't had this problem due to improvements they made back then during the XP/2000 era.

If you have this problem then chances are you either don't have any chipset drivers installed or, perhaps, nForce/VIA/whatever are crap?

Vista's handling of 'bad drives' was made even better because that OS implemented Cancellable I/O. And Windows Explorer was improved to make use of it. So if a drive is being annoying or slow, a simple click of the Cancel button will sort it out. And that click of the Cancel button will be instantaneous - no waiting around.

I have had this issue with my X48 chipset workstation with all latest drivers.

FreeStream · 30 Jul 2009 at 11:39

NathanE said:
This really comes down to your motherboard chipset drivers. Ever since about 2001-2002, the Intel Chipset Drivers haven't had this problem due to improvements they made back then during the XP/2000 era.

If you have this problem then chances are you either don't have any chipset drivers installed or, perhaps, nForce/VIA/whatever are crap?

Vista's handling of 'bad drives' was made even better because that OS implemented Cancellable I/O. And Windows Explorer was improved to make use of it. So if a drive is being annoying or slow, a simple click of the Cancel button will sort it out. And that click of the Cancel button will be instantaneous - no waiting around.

Its a workstation X58 motherboard with Xeons (2009 Mac Pro).

And this "instant click" is rubbish. If W7 has it it doesn't work, try and control - alt - delete yeilds nothing, then eventually after about 10 mins a blank, blue/purple screen covers everything. Control - shift - esc doesn't work either.

mr_x_plosion @ some disks you don't notice can't be read, a tiny scratch on one sector, etc.

As for OS X, its performance is identical to that of W7? Transfer rates are the same :/ Edit: Actually basically your saying it uses more system resources? Well who cares when I have more than one core doing the business!

QlimaxUK · 30 Jul 2009 at 17:58

i know what you mean but 'brings the whole system down' is a little OTT

its just a light 'freeze' fixed by a simple end task

just end explorer.exe
click file>new task (run...)
type: explorer.exe
enter

FIXED