Corrupt and unreadable file in WINNT\System32\Drivers

File intelide.sys in the C:\WINNT\System32\Drivers folder is corrupt and
unreadable.

If I try running CHKDSK it deletes the file leaving a hole that prevents
bootup amd a BSOD But I've managed to use the computer by preventing disk
checking on bootup. However, I can't use Safe Mode because it gets to
the point when intelide.sys should load and BSODs. Fortunately, I have
GoBack installed and that saved my bacon, but I'm living on borrowed time.

I tried copying a good copy of intelide.sys into the folder with Windows
running, without success. Similarly, trying to delete or rename the file
is impossible.

My floppy drive is not working so I loaded the Windows 2000 cd and got it to
boot up into the Repair facility.

I'm no expert in the necessary DOS-type commands but, having put a good copy
into the C: directory for ease, I tried:

Copy c:\intelide.sys c:\WINNT\system32\drivers but it wouldn't accept
that - I can't remember why, I think it didn't see it as a valid path or
directory.

I tried renaming the file in the Repair facility and again it wouldn't allow
it ( I think the command I used was:
Rename c:\WINNT\system32\drivers\intelide.sys intelideOLD.sys ) If that
had worked I would then have tried the Copy command again. I certainly
wasn't trying a DEL command until I'd got some understanding of the correct
commands.

To run the Repair facility, I had to disable GoBack so one mistake and it's
a full OS reinstall.

Any help on replacing the corrupt file would be greatly appreciated.


Thanks

Martin

 

This article may help.





--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]



"Martin" wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> File intelide.sys in the C:WINNTSystem32Drivers folder is corrupt and
> unreadable.
>
> If I try running CHKDSK it deletes the file leaving a hole that prevents
> bootup amd a BSOD But I've managed to use the computer by preventing
> disk
> checking on bootup. However, I can't use Safe Mode because it gets to
> the point when intelide.sys should load and BSODs. Fortunately, I have
> GoBack installed and that saved my bacon, but I'm living on borrowed time.
>
> I tried copying a good copy of intelide.sys into the folder with Windows
> running, without success. Similarly, trying to delete or rename the file
> is impossible.
>
> My floppy drive is not working so I loaded the Windows 2000 cd and got it
> to
> boot up into the Repair facility.
>
> I'm no expert in the necessary DOS-type commands but, having put a good
> copy
> into the C: directory for ease, I tried:
>
> Copy c:intelide.sys c:WINNTsystem32drivers but it wouldn't accept
> that - I can't remember why, I think it didn't see it as a valid path or
> directory.
>
> I tried renaming the file in the Repair facility and again it wouldn't
> allow
> it ( I think the command I used was:
> Rename c:WINNTsystem32driversintelide.sys intelideOLD.sys ) If that
> had worked I would then have tried the Copy command again. I certainly
> wasn't trying a DEL command until I'd got some understanding of the
> correct
> commands.
>
> To run the Repair facility, I had to disable GoBack so one mistake and
> it's
> a full OS reinstall.
>
> Any help on replacing the corrupt file would be greatly appreciated.
>
>
> Thanks
>
> Martin
>
> <!--colorc--><!--/colorc-->

 

Hi Dave and many thanks for the article, which, in all my searchings I
hadn't come across. I was hoping I'd be saying 'piece of cake", but it
didn't work. Below is what I did in the hope it might trigger a thought.
I followed the article using the Recovery Console and typed

copy c:\intelide.sys c:\winnt\system32\drivers\intelide.sys (I had
put a good copy in the root c: directory beforehand)

I got the message "The file cannot be copied"

So for an experiment to locate the problem I typed

copy c:\intelide.sys c:\intelidecopy.sys and got the message "1 file
copied"

I then tried

copy c:\winnt\system32\drivers\intelide.sys
c:\winnt\system32\drivers\intelidecopy.sys and got the message

"The system cannot find the file specified"

I then tried

copy c:\winnt\system32\drivers\intelide.sys c:\intelidecopy.sys and
again got the message

"The system cannot find the file specified"

Nevertheless, on reboot I've checked with Windows Explorer and intelide.sys
(corrupted) is still in the drivers folder.

I suppose I could try the DEL command first before the copy command i.e.

DEL c:\winnt\system32\drivers\intelide.sys

and then try the COPY command again, but I figure I shouldn't need to
because the Copy command should have caused overwriting of the corrupt file.
And I'm a bit wary of using the deleting the corrupt file without a bit af
advice first.

Any thoughts?

Again, thanks for the article.

Martin





"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message
news:es4yKAMNKHA.1268@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> This article may help.
>
>
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
>
>
>
> "Martin" wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > File intelide.sys in the C:WINNTSystem32Drivers folder is corrupt and
> > unreadable.
> >
> > If I try running CHKDSK it deletes the file leaving a hole that prevents
> > bootup amd a BSOD But I've managed to use the computer by preventing
> > disk
> > checking on bootup. However, I can't use Safe Mode because it gets<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
to<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > the point when intelide.sys should load and BSODs. Fortunately, I<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
have<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > GoBack installed and that saved my bacon, but I'm living on borrowed<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
time.<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> >
> > I tried copying a good copy of intelide.sys into the folder with Windows
> > running, without success. Similarly, trying to delete or rename the<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
file<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > is impossible.
> >
> > My floppy drive is not working so I loaded the Windows 2000 cd and got<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
it<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > to
> > boot up into the Repair facility.
> >
> > I'm no expert in the necessary DOS-type commands but, having put a good
> > copy
> > into the C: directory for ease, I tried:
> >
> > Copy c:intelide.sys c:WINNTsystem32drivers but it wouldn't<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
accept<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > that - I can't remember why, I think it didn't see it as a valid path or
> > directory.
> >
> > I tried renaming the file in the Repair facility and again it wouldn't
> > allow
> > it ( I think the command I used was:
> > Rename c:WINNTsystem32driversintelide.sys intelideOLD.sys ) If<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
that<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > had worked I would then have tried the Copy command again. I<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
certainly<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > wasn't trying a DEL command until I'd got some understanding of the
> > correct
> > commands.
> >
> > To run the Repair facility, I had to disable GoBack so one mistake and
> > it's
> > a full OS reinstall.
> >
> > Any help on replacing the corrupt file would be greatly appreciated.
> >
> >
> > Thanks
> >
> > Martin
> >
> ><!--colorc--><!--/colorc-->
><!--colorc--><!--/colorc-->

 

From the RC I'd try

dir c:\winnt\system32\drivers

to see what's there.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]



"Martin" wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Dave and many thanks for the article, which, in all my searchings I
> hadn't come across. I was hoping I'd be saying 'piece of cake", but it
> didn't work. Below is what I did in the hope it might trigger a
> thought.
> I followed the article using the Recovery Console and typed
>
> copy c:intelide.sys c:winntsystem32driversintelide.sys (I had
> put a good copy in the root c: directory beforehand)
>
> I got the message "The file cannot be copied"
>
> So for an experiment to locate the problem I typed
>
> copy c:intelide.sys c:intelidecopy.sys and got the message "1
> file
> copied"
>
> I then tried
>
> copy c:winntsystem32driversintelide.sys
> c:winntsystem32driversintelidecopy.sys and got the message
>
> "The system cannot find the file specified"
>
> I then tried
>
> copy c:winntsystem32driversintelide.sys c:intelidecopy.sys and
> again got the message
>
> "The system cannot find the file specified"
>
> Nevertheless, on reboot I've checked with Windows Explorer and
> intelide.sys
> (corrupted) is still in the drivers folder.
>
> I suppose I could try the DEL command first before the copy command i.e.
>
> DEL c:winntsystem32driversintelide.sys
>
> and then try the COPY command again, but I figure I shouldn't need to
> because the Copy command should have caused overwriting of the corrupt
> file.
> And I'm a bit wary of using the deleting the corrupt file without a bit af
> advice first.
>
> Any thoughts?
>
> Again, thanks for the article.
>
> Martin <!--colorc--><!--/colorc-->

 

Hi Dave and thanks for your quick response,

DIR shows the file correctly listed along with its date and size info in the
Drivers folder.

Martin

"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message
news:uEKXuKYNKHA.3588@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> From the RC I'd try
>
> dir c:winntsystem32drivers
>
> to see what's there.
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
>
>
>
> "Martin" wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi Dave and many thanks for the article, which, in all my searchings I
> > hadn't come across. I was hoping I'd be saying 'piece of cake", but it
> > didn't work. Below is what I did in the hope it might trigger a
> > thought.
> > I followed the article using the Recovery Console and typed
> >
> > copy c:intelide.sys c:winntsystem32driversintelide.sys (I<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
had<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > put a good copy in the root c: directory beforehand)
> >
> > I got the message "The file cannot be copied"
> >
> > So for an experiment to locate the problem I typed
> >
> > copy c:intelide.sys c:intelidecopy.sys and got the message "1
> > file
> > copied"
> >
> > I then tried
> >
> > copy c:winntsystem32driversintelide.sys
> > c:winntsystem32driversintelidecopy.sys and got the message
> >
> > "The system cannot find the file specified"
> >
> > I then tried
> >
> > copy c:winntsystem32driversintelide.sys c:intelidecopy.sys<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
and<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > again got the message
> >
> > "The system cannot find the file specified"
> >
> > Nevertheless, on reboot I've checked with Windows Explorer and
> > intelide.sys
> > (corrupted) is still in the drivers folder.
> >
> > I suppose I could try the DEL command first before the copy command i.e.
> >
> > DEL c:winntsystem32driversintelide.sys
> >
> > and then try the COPY command again, but I figure I shouldn't need to
> > because the Copy command should have caused overwriting of the corrupt
> > file.
> > And I'm a bit wary of using the deleting the corrupt file without a bit<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
af<!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
> > advice first.
> >
> > Any thoughts?
> >
> > Again, thanks for the article.
> >
> > Martin<!--colorc--><!--/colorc-->
><!--colorc--><!--/colorc-->

 

Try;
copy c:\intelide.sys c:\winnt\system32\drivers\


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]



"Martin" wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Dave and thanks for your quick response,
>
> DIR shows the file correctly listed along with its date and size info in
> the
> Drivers folder.
>
> Martin <!--colorc--><!--/colorc-->

 

Many thanks for your kind patience. I booted into the Recovery Console
from the cd and:

copy c:\intelide.sys c:\winnt\system32\drivers

"The file could not be copied"

I then experimented:

copy c:\intelide.sys c:\winnt

"1 file copied"


copy c:\winnt\intelide.sys c:\winnt\system32\drivers

"The file could not be copied"


In desperation:

DEL c:\winnt\system32\drivers\intelide.sys

"The delete operation failed."


I then did DIR for the drivers folder and, as before, intelide.sys is still
listed and appears to have the same attibute as most of the other files,
namely, -a------


I suspect I'll just have to live with this until such time as either I'm
forced to do a clean install or when Microsoft ends critical security
patches for Windows 2000, at which time I'll have no choice but to trade up.

Anyway, if you still have the patience and have any more sugestions, I'd be
most grateful to hear and try them.

Thanks again

Martin






"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message
news:OU9KFtYNKHA.4816@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Try;
> copy c:intelide.sys c:winntsystem32drivers
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
>
>
>
> "Martin" wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi Dave and thanks for your quick response,
> >
> > DIR shows the file correctly listed along with its date and size info in
> > the
> > Drivers folder.
> >
> > Martin<!--colorc--><!--/colorc-->
><!--colorc--><!--/colorc-->

 

Hi Dave,

Using the message "the delete operation failed", I just found this:




I don't have Bart PE, and I don't think it works on Windows 2000. Still,
I'm willing to have a go using the Recovery Console. However, I'm not
familiar with XCOPY and the switches mentioned in the link above, so if you
would kindly tell me what to type, I'd be most grateful.

Regards


Martin




"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message
news:OU9KFtYNKHA.4816@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Try;
> copy c:intelide.sys c:winntsystem32drivers
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
>
>
>
> "Martin" wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi Dave and thanks for your quick response,
> >
> > DIR shows the file correctly listed along with its date and size info in
> > the
> > Drivers folder.
> >
> > Martin<!--colorc--><!--/colorc-->
><!--colorc--><!--/colorc-->

 

Don't know if this helps but my c:\winnt\system32\drivers directory is
marked as read-only. You could perhaps try changing the attributes for
the directory before the copy, e.g.

attrib -r c:\winnt\system32\drivers



Martin wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> copy c:intelide.sys c:winntsystem32drivers
>
> "The file could not be copied"
>
> I then experimented:
>
> copy c:intelide.sys c:winnt
>
> "1 file copied"<!--colorc--><!--/colorc-->

 

Hi and thanks for the kind suggestion

I ve just chesked the attributes using the Properties tab via Windows
Explorer and neither intelide.sys or any of its parent folders is read only
(nor hidden).

Martin



"Sid Elbow" <here@there.com> wrote in message
news:00211c62$0$1014$c3e8da3@news.astraweb.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Don't know if this helps but my c:winntsystem32drivers directory is
> marked as read-only. You could perhaps try changing the attributes for
> the directory before the copy, e.g.
>
> attrib -r c:winntsystem32drivers
>
>
>
> Martin wrote:
><!--coloro:green--><span style="color:green <!--/coloro-->
> > copy c:intelide.sys c:winntsystem32drivers
> >
> > "The file could not be copied"
> >
> > I then experimented:
> >
> > copy c:intelide.sys c:winnt
> >
> > "1 file copied"<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Curious.

You said you tried copying the c:\intelide.sys file to a directory other
than ......\drivers\ and it was fine.

Have you tried the "corollary" - that is copying a file *other than*
c:\intelide.sys to the .....\drivers\ directory ? Say a small text file
placed in c:\

I suppose it's possible (the MVP's here would know better than I whether
it's likely) that Windows could make the directory/file read only on
shutdown (or the RC might do so before it lets you "at it"). If it were
me I'd still verify the status using attrib from the RC.


Martin wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi and thanks for the kind suggestion
>
> I ve just chesked the attributes using the Properties tab via Windows
> Explorer and neither intelide.sys or any of its parent folders is read only
> (nor hidden).
>
> Martin
>
>
>
> "Sid Elbow" <here@there.com> wrote in message
> news:00211c62$0$1014$c3e8da3@news.astraweb.com...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Don't know if this helps but my c:winntsystem32drivers directory is
>> marked as read-only. You could perhaps try changing the attributes for
>> the directory before the copy, e.g.
>>
>> attrib -r c:winntsystem32drivers
>>
>>
>>
>> Martin wrote:
>><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> copy c:intelide.sys c:winntsystem32drivers
>>>
>>> "The file could not be copied"
>>>
>>> I then experimented:
>>>
>>> copy c:intelide.sys c:winnt
>>>
>>> "1 file copied"<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

Yes, I agree it is file system corruption. You can still try it from the RC.
You can;

REN c:\winnt\system32\drivers driversold
MD c:\winnt\system32\drivers
COPY c:\intelide.sys c:\winnt\system32\drivers\
COPY c:\winnt\system32\driversold\*.* c:\winnt\system32\drivers
answer no if prompted to overwrite on last copy command



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]



"Martin" wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Dave,
>
> Using the message "the delete operation failed", I just found this:
>
>
>
>
> I don't have Bart PE, and I don't think it works on Windows 2000. Still,
> I'm willing to have a go using the Recovery Console. However, I'm not
> familiar with XCOPY and the switches mentioned in the link above, so if
> you
> would kindly tell me what to type, I'd be most grateful.
>
> Regards
>
>
> Martin <!--colorc--><!--/colorc-->

 

Bit of a disaster I'm afraid after I finally got the Recovery Console to load.

the *.* prompted a message about wildcards being unsupoorted. To try and
recover, I deleted c:\winnt\system32\drivers and then tried to REN driversold
back to drivers. I got the message about being unable to find the folder,
or something like that. I could get it to REN back. Of course, with the
drivers folder gone I then tried emergency repair with Recovery Console.
Somehow, the intelide problem remained because Safe Mode crashed at the point
it should have loaded so both Safe Mode and Normal Mode were dead and I had
no choice but to reinstall Windows 2000, shich should keep me quiet for a few
weeks. Odd thing is that despite formatting the C drive, I didn't have to
install either the video card drivers or the sound card drivers - Windows
booted up for the first time with the drivers somehow installed and the video
and sound properties as normal. One less job to do.

Thanks for the help anyway; it was probably due a fresh install after having
run for 4 or 5 years without one. I think it was on the cards anyway but
well worth a try.


Martin

"Dave Patrick" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Yes, I agree it is file system corruption. You can still try it from the RC.
> You can;
>
> REN c:winntsystem32drivers driversold
> MD c:winntsystem32drivers
> COPY c:intelide.sys c:winntsystem32drivers
> COPY c:winntsystem32driversold*.* c:winntsystem32drivers
> answer no if prompted to overwrite on last copy command
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
>
>
>
> "Martin" wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi Dave,
> >
> > Using the message "the delete operation failed", I just found this:
> >
> >
> >
> >
> > I don't have Bart PE, and I don't think it works on Windows 2000. Still,
> > I'm willing to have a go using the Recovery Console. However, I'm not
> > familiar with XCOPY and the switches mentioned in the link above, so if
> > you
> > would kindly tell me what to type, I'd be most grateful.
> >
> > Regards
> >
> >
> > Martin <!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

In news:1C2040DE-18FD-4E60-A49D-1926DBA23E60@microsoft.com,
Martin typed on Thu, 17 Sep 2009 07:41:01 -0700:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> ... Odd thing is that despite formatting the C drive, I didn't
> have to install either the video card drivers or the sound card
> drivers - Windows booted up for the first time with the drivers
> somehow installed and the video and sound properties as normal. One<!--colorc--><!--/colorc-->
less job to do.

My two Toshiba 2595XDVD ('99 era) are like that. Windows 2000 installs
(retail versions) and everything, video, sound, pointer, IR, PCMCIA,
DVD, etc. all detected and installed drivers for everything. And these
laptops originally came with Windows 98FE which needed all kinds of
special drivers from Toshiba. Weird, eh?

--
Bill
Windows 2000 SP4 (5.00.2195)
Asus EEE PC 701G4 ~ 2GB RAM ~ 16GB-SDHC

 

I think I'd still run the manufacturer's diagnostic tools to check the disk
integrity.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]



"Martin" wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Bit of a disaster I'm afraid after I finally got the Recovery Console to
> load.
>
> the *.* prompted a message about wildcards being unsupoorted. To try
> and
> recover, I deleted c:winntsystem32drivers and then tried to REN
> driversold
> back to drivers. I got the message about being unable to find the
> folder,
> or something like that. I could get it to REN back. Of course, with
> the
> drivers folder gone I then tried emergency repair with Recovery Console.
> Somehow, the intelide problem remained because Safe Mode crashed at the
> point
> it should have loaded so both Safe Mode and Normal Mode were dead and I
> had
> no choice but to reinstall Windows 2000, shich should keep me quiet for a
> few
> weeks. Odd thing is that despite formatting the C drive, I didn't have
> to
> install either the video card drivers or the sound card drivers - Windows
> booted up for the first time with the drivers somehow installed and the
> video
> and sound properties as normal. One less job to do.
>
> Thanks for the help anyway; it was probably due a fresh install after
> having
> run for 4 or 5 years without one. I think it was on the cards anyway
> but
> well worth a try.
>
>
> Martin <!--colorc--><!--/colorc-->