Mini-Me
09-15-2006, 04:42 AM
I am so frustrated by this.
The problem has been covered before, but just to recap: This problem is extremely common in Windows XP, in that you take a CD out, put a completely new one in, and Windows presents you with a tree of the previous CD's contents - but not the one you just put in - if you try to access anything, naturally enough, you get fatal errors, as those files and that disc are no longer in the drive...
It makes me so mad, I can't tell you...
:mad:
:mad:
:mad:
MS know of this problem, but seem to be doing nothing about it.
With all the daily updates possible via Automatic Updates, you would think they would have addressed this major access problem by now...
I prey to the God of technology, that Vista does not suffer from this issue(but I would not be surprised to find that it does...)
Anyway, for now, I have resorted to accessing the disc on a Win98 box, which reads the disc just fine - go figure.
I don't wish to bleet, but why the hell has this problem not been fixed via an Automatic Update by now??!?!??!??!
Why, why why!?!?!??!!
The problem has been covered before, but just to recap: This problem is extremely common in Windows XP, in that you take a CD out, put a completely new one in, and Windows presents you with a tree of the previous CD's contents - but not the one you just put in - if you try to access anything, naturally enough, you get fatal errors, as those files and that disc are no longer in the drive...
It makes me so mad, I can't tell you...
:mad:
:mad:
:mad:
MS know of this problem, but seem to be doing nothing about it.
With all the daily updates possible via Automatic Updates, you would think they would have addressed this major access problem by now...
I prey to the God of technology, that Vista does not suffer from this issue(but I would not be surprised to find that it does...)
Anyway, for now, I have resorted to accessing the disc on a Win98 box, which reads the disc just fine - go figure.
I don't wish to bleet, but why the hell has this problem not been fixed via an Automatic Update by now??!?!??!??!
Why, why why!?!?!??!!