iosubsys problem

Hi Mart;
I followed you advice and found 4 leftover ATI files in INF and 1 in
INF\OTHER, renamed them and tried again but no luck. I then tried searching
Windows for ATI* and found 41 files in
c:\Windows\System\REINSTALLBACKUPS\PCI#VEN_1002&DE V_5144&SUBSYS_108A1002
from their ages, they look to be the originals that came with the machine(
There are also 22 files in REINSTALLBACKUPS\DevMgr which I assume are for
the card, itself). Might it be possible to drag and drop these files to get
back the original driver? Or is there some even easier way to invoke the
backup?
Thanks in advance for your help - I can almost feel hope being reborn :-)

George J. Wallace

George,

The two folders you mentioned sounds like part of an OEM installation so I
can't really advise except to suggest you try your idea (after setting an SR
point of course!!) It can't make things any worse g Might even be worth
copying the files to a CD (or other media) for safe keeping before you
start. Do you still have the original User Manual?

In the meantime, I tried a bit of searching today regarding catalyst drivers
(which appear to have a poor reputation with WinMe compatibility) and found
the following in my WinMe News Groups archive which *might* also be of some
use. It's a few years old and is credited to someone called 'Peter' and I
hope it helps :-

Hi,

I have a friend who have the similiar problems when tried
to re-install the ATI Radeon 8500 drivers on his Win ME
machine. The machine could not load in normal mode after
changing the display to VGA mode and install the ATI
drivers. I fixed the problems with the following steps:

Ca disable any antiVirus software before performing
installation of display drivers. run msconfig to
temporary disable antivirus software to run at the
background.

1. download the catalyst drivers from ATI and save it to
a specific folder (do not save it to desktop)
2. boot in safe mode and change the display to VGA mode,
do not reboot.
3. open the specific folder and double click the icon to
install the catalyst drivers. Note: the drivers start to
load and at the end you will receive a warning that the
drivers could not load properly and instruct you to
change the display mode to VGA mode.
4. reboot the computer to safe mode again.
5. go to device manager and look for the display adapter.
You may see 2 display adapters on the drop down list; one
is the Radeon display adapter with a big red X mark on it
and the other is VGA adapter. Right click on the Radeon
display adapter and click remove then reboot the computer
to normal.
6. If you computer can load in normal mode, go to device
manager again to ensure the radeon drivers is properly
installed then adjust your display resoultion.

Hope it helps.
Peter


Best of luck

Mart


"George J. Wallace" wrote in message
...
Hi Mart;
I followed you advice and found 4 leftover ATI files in INF and 1 in
INF\OTHER, renamed them and tried again but no luck. I then tried
searching
Windows for ATI* and found 41 files in
c:\Windows\System\REINSTALLBACKUPS\PCI#VEN_1002&DE V_5144&SUBSYS_108A1002
from their ages, they look to be the originals that came with the machine(
There are also 22 files in REINSTALLBACKUPS\DevMgr which I assume are for
the card, itself). Might it be possible to drag and drop these files to
get
back the original driver? Or is there some even easier way to invoke the
backup?
Thanks in advance for your help - I can almost feel hope being reborn :-)

George J. Wallace

This is the LAST machine that I ever work on without first ripping Norton
out by the entrails!
Ooooooo, can I watch? will it be like william wallace and done on
a table.
Stooopid bloody Norton.
Gekko
Noel Paton (MS-MVP 2002-2006, Windows)

It may be worth clearing the swapfile is case it's corrupted - either boot
to DOS with a floppy, or boot to XP (if it can see the ME install) and
delete the file WIN386.SWP (there will probably be two copies - one in C:\
and one in C:\Windows - delete both)

See if that helps

Noel Paton (MS-MVP 2002-2006, Windows)

Noel,
forgive the intrusion on the thread, but when I see something I dont quite
understand I have to satisfy myself.
I noticed that the win386.swp is talked about with relative ease when
considering deleting it; wouldnt this be a solution in itself if windows
creates a new empty one?
I did google first to read up as much as I could, but couldnt find anything
that sat right.
Damn but its taxing trying to soak up 20 or more topics at one time.
(did my first registry hack today.....)
Cheers
Gekko

"Gekko" wrote in message
...

It may be worth clearing the swapfile is case it's corrupted - either
boot
to DOS with a floppy, or boot to XP (if it can see the ME install) and
delete the file WIN386.SWP (there will probably be two copies - one in
C:\
and one in C:\Windows - delete both)

See if that helps

Noel Paton (MS-MVP 2002-2006, Windows)

Noel,
forgive the intrusion on the thread, but when I see something I dont quite
understand I have to satisfy myself.
I noticed that the win386.swp is talked about with relative ease when
considering deleting it; wouldnt this be a solution in itself if windows
creates a new empty one?
I did google first to read up as much as I could, but couldnt find
anything
that sat right.
Damn but its taxing trying to soak up 20 or more topics at one time.
(did my first registry hack today.....)
Cheers
Gekko


WIN386.SWP is a huge file in most circumstances - anywhere from 20MB to 2GB.
One of the reasons that Windows doesn't re-create it every boot is that it
takes time, and requires that Windows not be running at the time
It is (IIRC) possible to force a deletion/re-creation of the file on every
boot - but what's the point, when corruption is an uncommon happening?
I'm not sure exactly what you're asking here - can you be more specific?
--
Noel Paton (MS-MVP 2002-2006, Windows)

Nil Carborundum Illegitemi
http://www.crashfixpc.com

http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

GOOOOOAL! And the crowd goes wild!
In Mart's last msg, it was suggested that I set a sysrestore point before
continuing. In my 2nd msg, I'd said that sysrestore had failed so fixing
that seemed to be my 1st task. I did a scanreg /restore to my latest good
registry (7/15/05 !) then entered devicemanager and clicked update driver
for the Radeon card. It searched, made me an offer, and I clicked ok but it
then needed the file I'd renamed in the INF\Other folder. I restored the
original name, told devicemanager to update the driver and Woowoo! Huah!
Ooh baby, ooh baby, ooh baby! And the crowd shouts "Go Mart, Go Mart, Go
Mart".
Seriously, you all have my deepest gratitude: Mike for getting me up and
running again in safe mode, Noel for helping to eliminate a whole bunch of
things and planting the key ideas, and Mart for finding an answer in the
archives. Since I got this pc 5 yrs ago, I've been dropping in on this
forum and you folks ARE THE BEST!
The whole nation rejoices, singing "here we go, here we go, here we go"!
Thanks again.

George J. Wallace

I guess it's fixed then ?

Glad to have been of some assistance!

thanks for the feedback - and Good Luck

--
Noel Paton (MS-MVP 2002-2006, Windows)

Nil Carborundum Illegitemi
http://www.crashfixpc.com

http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
"George J. Wallace" wrote in message
...
GOOOOOAL! And the crowd goes wild!
In Mart's last msg, it was suggested that I set a sysrestore point before
continuing. In my 2nd msg, I'd said that sysrestore had failed so fixing
that seemed to be my 1st task. I did a scanreg /restore to my latest good
registry (7/15/05 !) then entered devicemanager and clicked update driver
for the Radeon card. It searched, made me an offer, and I clicked ok but
it then needed the file I'd renamed in the INF\Other folder. I restored
the original name, told devicemanager to update the driver and Woowoo!
Huah! Ooh baby, ooh baby, ooh baby! And the crowd shouts "Go Mart, Go
Mart, Go Mart".
Seriously, you all have my deepest gratitude: Mike for getting me up and
running again in safe mode, Noel for helping to eliminate a whole bunch of
things and planting the key ideas, and Mart for finding an answer in the
archives. Since I got this pc 5 yrs ago, I've been dropping in on this
forum and you folks ARE THE BEST!
The whole nation rejoices, singing "here we go, here we go, here we go"!
Thanks again.

George J. Wallace

George, as you are well aware, goals can be scored from many different
angles and like most things 'Windows', the parallel is that there are many
ways of skinning the same cat g The video problem had to be driver related
and you successfully resolved it. You did it 'your way!' The other earlier
issues needed the forensic approach outlined by Mike and Noel which again,
you achieved successfully and hopefully, enhanced your learning curve too.

Congratulations and very well done. And thanks for the feedback, it's
appreciated.

Mart


"George J. Wallace" wrote in message
...
GOOOOOAL! And the crowd goes wild!
In Mart's last msg, it was suggested that I set a sysrestore point before
continuing. In my 2nd msg, I'd said that sysrestore had failed so fixing
that seemed to be my 1st task. I did a scanreg /restore to my latest good
registry (7/15/05 !) then entered devicemanager and clicked update driver
for the Radeon card. It searched, made me an offer, and I clicked ok but
it then needed the file I'd renamed in the INF\Other folder. I restored
the original name, told devicemanager to update the driver and Woowoo!
Huah! Ooh baby, ooh baby, ooh baby! And the crowd shouts "Go Mart, Go
Mart, Go Mart".
Seriously, you all have my deepest gratitude: Mike for getting me up and
running again in safe mode, Noel for helping to eliminate a whole bunch of
things and planting the key ideas, and Mart for finding an answer in the
archives. Since I got this pc 5 yrs ago, I've been dropping in on this
forum and you folks ARE THE BEST!
The whole nation rejoices, singing "here we go, here we go, here we go"!
Thanks again.

George J. Wallace

George,

I'm pleased to read you've managed to solve the problem. Well done.
--
Mike Maltby



George J. Wallace wrote:

GOOOOOAL! And the crowd goes wild!
In Mart's last msg, it was suggested that I set a sysrestore point
before continuing. In my 2nd msg, I'd said that sysrestore had
failed so fixing that seemed to be my 1st task. I did a scanreg
/restore to my latest good registry (7/15/05 !) then entered
devicemanager and clicked update driver for the Radeon card. It
searched, made me an offer, and I clicked ok but it then needed the
file I'd renamed in the INF\Other folder. I restored the original
name, told devicemanager to update the driver and Woowoo! Huah! Ooh
baby, ooh baby, ooh baby! And the crowd shouts "Go Mart, Go Mart, Go
Mart". Seriously, you all have my deepest gratitude: Mike for
getting me up and running again in safe mode, Noel for helping to
eliminate a whole bunch of things and planting the key ideas, and
Mart for finding an answer in the archives. Since I got this pc 5
yrs ago, I've been dropping in on this forum and you folks ARE THE
BEST! The whole nation rejoices, singing "here we go, here we go,
here we go"! Thanks again.

George J. Wallace

Tried to send this via Google and the bloody thing ate my post! So now I had
to set up an OE account just to send this!

Its a privacy/secrecy thing, isn't it Noel? Though I'd say *for the paranoid
only!*, ie if you delete MRU lists, browsing history, run history etc etc
etc as a matter of course - or if you think that one day you *might* want to
regularly shred everything, ie if secrecy really matters (like you send
encrypted e-mails?) then maybe you should get into the habit of deleting the
swapfile too?

I, of course, use the Real Mode hack. Or at least, have it available (since
it increases boot time, so usually it's disabled). In that Autoexec.bat is
the line ECHO.C:\WINDOWS\WIN386.SWP which 'instantly' reduces that massive
file to 2-bytes in length. Its so easy I couldn't be bothered *not* to do
it! But for the vast majority it is surely unnecessary - as is the
scrambling for anti-spyware updates like women in the January sales, but
there's no shortage of participants for *that* one is there! vbg

Shane

WIN386.SWP is a huge file in most circumstances - anywhere from 20MB to
2GB.
One of the reasons that Windows doesn't re-create it every boot is that it
takes time, and requires that Windows not be running at the time
It is (IIRC) possible to force a deletion/re-creation of the file on every
boot - but what's the point, when corruption is an uncommon happening?
I'm not sure exactly what you're asking here - can you be more specific?
--
Noel Paton (MS-MVP 2002-2006, Windows)

Nil Carborundum Illegitemi
http://www.crashfixpc.com

http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's