A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » Networking
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

How does windows find the correct device driver?



 
 
Thread Tools Display Modes
  #1  
Old May 9th 06, 01:56 AM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
external usenet poster
 
Posts: n/a
Default How does windows find the correct device driver?

I have been having a load of trouble trying to install an ethernet card
10/100 NIC thingy, I have an installation disk but that didn't seem to
work properly so I have been trying to do it 'manually' too, by downloading
various drivers which look 'likely suspects'.

Anyway at first when I booted up with the new card in it would detect
it and go to driver installation dialogue and I would point it to where
the driver I wanted to try was. Invariably it would find it, try to install
it, and then fail.
However now when I try the procedure again after making some
adjustment, or just wanting to try it again it doesn't seem to find the
drives in places it had previously found them. It is almost as if it had
remembered "oh that one didn't work before so I will ignore it!!"
Either that or it deleted then or something.

So.. what I want to know is how windows associates a driver
with a device. I mean if there were a load of drivers in a folder,
which one would it pick, and how does it make it's decision?

The device is question is an ethernet card which has rtl8139(d)
on the chip, however before it detected it as an rtl8129 when
I used the installation disk setup with it, so I aint too sure and I
am a bit confused.

Another point is that initially when I used the installation disk
and some time with out it, when it did find a driver it was happy
with it would prompt me to put my original windows disk in so it
could get some more 'stuff' (drivers etc...). However it never
found what it wanted untill I unzipped a load of the .cab files
(mainly net??.cab), then it did find them (it wanted about 40+
files), it would then say some files were older versions of the files
and ask if I wanted to replace the existing version, I would say no,
this would continue untill it got to telnet.exe (IIRC), I would say
no don't replace it, then my system would hang/crash.
After that I clicked yes to replace telnet.exe to see it that helped
but it didn't.
Now however I said earlier, it will never find the first driver so
I can't get to that stage anymore.
I am at a loss to figure out what is going on and I would reallly
appreciate any advice, especally from folks who understand
what is going on and what to do,as the whold thing seems to be pretty
inconsistant and I can't seem to go back too 'square one'.

My computer still works find though (am using it now), but I
just can't for the life of me get windows to install a drive for the card.


TIA.


  #2  
Old May 9th 06, 06:44 AM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
external usenet poster
 
Posts: n/a
Default How does windows find the correct device driver?

Bazzer Smith wrote:
I have been having a load of trouble trying to install an ethernet
card 10/100 NIC thingy, I have an installation disk but that didn't
seem to work properly so I have been trying to do it 'manually' too,
by downloading various drivers which look 'likely suspects'.

Anyway at first when I booted up with the new card in it would detect
it and go to driver installation dialogue and I would point it to
where the driver I wanted to try was. Invariably it would find it,
try to install it, and then fail.
However now when I try the procedure again after making some
adjustment, or just wanting to try it again it doesn't seem to find
the drives in places it had previously found them. It is almost as if
it had remembered "oh that one didn't work before so I will ignore
it!!"
Either that or it deleted then or something.

So.. what I want to know is how windows associates a driver
with a device. I mean if there were a load of drivers in a folder,
which one would it pick, and how does it make it's decision?

The device is question is an ethernet card which has rtl8139(d)
on the chip, however before it detected it as an rtl8129 when
I used the installation disk setup with it, so I aint too sure and I
am a bit confused.

Another point is that initially when I used the installation disk
and some time with out it, when it did find a driver it was happy
with it would prompt me to put my original windows disk in so it
could get some more 'stuff' (drivers etc...). However it never
found what it wanted untill I unzipped a load of the .cab files
(mainly net??.cab), then it did find them (it wanted about 40+
files), it would then say some files were older versions of the files
and ask if I wanted to replace the existing version, I would say no,
this would continue untill it got to telnet.exe (IIRC), I would say
no don't replace it, then my system would hang/crash.
After that I clicked yes to replace telnet.exe to see it that helped
but it didn't.
Now however I said earlier, it will never find the first driver so
I can't get to that stage anymore.
I am at a loss to figure out what is going on and I would reallly
appreciate any advice, especally from folks who understand
what is going on and what to do,as the whold thing seems to be pretty
inconsistant and I can't seem to go back too 'square one'.

My computer still works find though (am using it now), but I
just can't for the life of me get windows to install a drive for the
card.


TIA.


Shouldn't be that hard. Realtek has the drivers he

http://www.realtek.com.tw/downloads/...&Software=True

As far as where how Windows finds the driver, find the entry in the ENUM key
corresponding to your device, then look up (e.g. Google) to see what info
Windows is obtaining from the device.

http://www.microsoft.com/technet/arc....mspx?mfr=true

More here from Google:

http://www.google.com/search?hl=en&l...um+98+registry



  #3  
Old May 9th 06, 06:44 AM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
mdp
External Usenet User
 
Posts: 13
Default How does windows find the correct device driver?

Bazzer Smith wrote:
I have been having a load of trouble trying to install an ethernet
card 10/100 NIC thingy, I have an installation disk but that didn't
seem to work properly so I have been trying to do it 'manually' too,
by downloading various drivers which look 'likely suspects'.

Anyway at first when I booted up with the new card in it would detect
it and go to driver installation dialogue and I would point it to
where the driver I wanted to try was. Invariably it would find it,
try to install it, and then fail.
However now when I try the procedure again after making some
adjustment, or just wanting to try it again it doesn't seem to find
the drives in places it had previously found them. It is almost as if
it had remembered "oh that one didn't work before so I will ignore
it!!"
Either that or it deleted then or something.

So.. what I want to know is how windows associates a driver
with a device. I mean if there were a load of drivers in a folder,
which one would it pick, and how does it make it's decision?

The device is question is an ethernet card which has rtl8139(d)
on the chip, however before it detected it as an rtl8129 when
I used the installation disk setup with it, so I aint too sure and I
am a bit confused.

Another point is that initially when I used the installation disk
and some time with out it, when it did find a driver it was happy
with it would prompt me to put my original windows disk in so it
could get some more 'stuff' (drivers etc...). However it never
found what it wanted untill I unzipped a load of the .cab files
(mainly net??.cab), then it did find them (it wanted about 40+
files), it would then say some files were older versions of the files
and ask if I wanted to replace the existing version, I would say no,
this would continue untill it got to telnet.exe (IIRC), I would say
no don't replace it, then my system would hang/crash.
After that I clicked yes to replace telnet.exe to see it that helped
but it didn't.
Now however I said earlier, it will never find the first driver so
I can't get to that stage anymore.
I am at a loss to figure out what is going on and I would reallly
appreciate any advice, especally from folks who understand
what is going on and what to do,as the whold thing seems to be pretty
inconsistant and I can't seem to go back too 'square one'.

My computer still works find though (am using it now), but I
just can't for the life of me get windows to install a drive for the
card.


TIA.


Shouldn't be that hard. Realtek has the drivers he

http://www.realtek.com.tw/downloads/...&Software=True

As far as where how Windows finds the driver, find the entry in the ENUM key
corresponding to your device, then look up (e.g. Google) to see what info
Windows is obtaining from the device.

http://www.microsoft.com/technet/arc....mspx?mfr=true

More here from Google:

http://www.google.com/search?hl=en&l...um+98+registry



  #4  
Old May 9th 06, 03:12 PM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
external usenet poster
 
Posts: n/a
Default How does windows find the correct device driver?


"mdp" wrote in message
...
Bazzer Smith wrote:
I have been having a load of trouble trying to install an ethernet
card 10/100 NIC thingy, I have an installation disk but that didn't
seem to work properly so I have been trying to do it 'manually' too,
by downloading various drivers which look 'likely suspects'.

Anyway at first when I booted up with the new card in it would detect
it and go to driver installation dialogue and I would point it to
where the driver I wanted to try was. Invariably it would find it,
try to install it, and then fail.
However now when I try the procedure again after making some
adjustment, or just wanting to try it again it doesn't seem to find
the drives in places it had previously found them. It is almost as if
it had remembered "oh that one didn't work before so I will ignore
it!!"
Either that or it deleted then or something.

So.. what I want to know is how windows associates a driver
with a device. I mean if there were a load of drivers in a folder,
which one would it pick, and how does it make it's decision?

The device is question is an ethernet card which has rtl8139(d)
on the chip, however before it detected it as an rtl8129 when
I used the installation disk setup with it, so I aint too sure and I
am a bit confused.

Another point is that initially when I used the installation disk
and some time with out it, when it did find a driver it was happy
with it would prompt me to put my original windows disk in so it
could get some more 'stuff' (drivers etc...). However it never
found what it wanted untill I unzipped a load of the .cab files
(mainly net??.cab), then it did find them (it wanted about 40+
files), it would then say some files were older versions of the files
and ask if I wanted to replace the existing version, I would say no,
this would continue untill it got to telnet.exe (IIRC), I would say
no don't replace it, then my system would hang/crash.
After that I clicked yes to replace telnet.exe to see it that helped
but it didn't.
Now however I said earlier, it will never find the first driver so
I can't get to that stage anymore.
I am at a loss to figure out what is going on and I would reallly
appreciate any advice, especally from folks who understand
what is going on and what to do,as the whold thing seems to be pretty
inconsistant and I can't seem to go back too 'square one'.

My computer still works find though (am using it now), but I
just can't for the life of me get windows to install a drive for the
card.


TIA.


Shouldn't be that hard. Realtek has the drivers he

http://www.realtek.com.tw/downloads/...&Software=True

As far as where how Windows finds the driver, find the entry in the ENUM
key corresponding to your device, then look up (e.g. Google) to see what
info Windows is obtaining from the device.



I think you may have misunderstood me a little, how does windows know
what information to put in the ENUM key, bacially how does it know what
type of device I have plugged into a slot.

Or to put it another way how does windows know what to put int
the EMUN keys in the registry, when you plpug a new device in?



http://www.microsoft.com/technet/arc....mspx?mfr=true

More here from Google:

http://www.google.com/search?hl=en&l...um+98+registry





  #5  
Old May 9th 06, 03:12 PM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
Bazzer Smith
external usenet poster
 
Posts: 19
Default How does windows find the correct device driver?


"mdp" wrote in message
...
Bazzer Smith wrote:
I have been having a load of trouble trying to install an ethernet
card 10/100 NIC thingy, I have an installation disk but that didn't
seem to work properly so I have been trying to do it 'manually' too,
by downloading various drivers which look 'likely suspects'.

Anyway at first when I booted up with the new card in it would detect
it and go to driver installation dialogue and I would point it to
where the driver I wanted to try was. Invariably it would find it,
try to install it, and then fail.
However now when I try the procedure again after making some
adjustment, or just wanting to try it again it doesn't seem to find
the drives in places it had previously found them. It is almost as if
it had remembered "oh that one didn't work before so I will ignore
it!!"
Either that or it deleted then or something.

So.. what I want to know is how windows associates a driver
with a device. I mean if there were a load of drivers in a folder,
which one would it pick, and how does it make it's decision?

The device is question is an ethernet card which has rtl8139(d)
on the chip, however before it detected it as an rtl8129 when
I used the installation disk setup with it, so I aint too sure and I
am a bit confused.

Another point is that initially when I used the installation disk
and some time with out it, when it did find a driver it was happy
with it would prompt me to put my original windows disk in so it
could get some more 'stuff' (drivers etc...). However it never
found what it wanted untill I unzipped a load of the .cab files
(mainly net??.cab), then it did find them (it wanted about 40+
files), it would then say some files were older versions of the files
and ask if I wanted to replace the existing version, I would say no,
this would continue untill it got to telnet.exe (IIRC), I would say
no don't replace it, then my system would hang/crash.
After that I clicked yes to replace telnet.exe to see it that helped
but it didn't.
Now however I said earlier, it will never find the first driver so
I can't get to that stage anymore.
I am at a loss to figure out what is going on and I would reallly
appreciate any advice, especally from folks who understand
what is going on and what to do,as the whold thing seems to be pretty
inconsistant and I can't seem to go back too 'square one'.

My computer still works find though (am using it now), but I
just can't for the life of me get windows to install a drive for the
card.


TIA.


Shouldn't be that hard. Realtek has the drivers he

http://www.realtek.com.tw/downloads/...&Software=True

As far as where how Windows finds the driver, find the entry in the ENUM
key corresponding to your device, then look up (e.g. Google) to see what
info Windows is obtaining from the device.



I think you may have misunderstood me a little, how does windows know
what information to put in the ENUM key, bacially how does it know what
type of device I have plugged into a slot.

Or to put it another way how does windows know what to put int
the EMUN keys in the registry, when you plpug a new device in?



http://www.microsoft.com/technet/arc....mspx?mfr=true

More here from Google:

http://www.google.com/search?hl=en&l...um+98+registry





  #6  
Old May 9th 06, 04:26 PM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
external usenet poster
 
Posts: n/a
Default How does windows find the correct device driver?

"Bazzer Smith" wrote in
:


I think you may have misunderstood me a little, how does windows know
what information to put in the ENUM key, bacially how does it know
what type of device I have plugged into a slot.

Or to put it another way how does windows know what to put int
the EMUN keys in the registry, when you plpug a new device in?


All plug&play devices have a standard way to give a product- and a vendorID
(both 16 bits) to the OS. The ENUM key is a munged version of these.
  #7  
Old May 9th 06, 04:26 PM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
Ingeborg
External Usenet User
 
Posts: 217
Default How does windows find the correct device driver?

"Bazzer Smith" wrote in
:


I think you may have misunderstood me a little, how does windows know
what information to put in the ENUM key, bacially how does it know
what type of device I have plugged into a slot.

Or to put it another way how does windows know what to put int
the EMUN keys in the registry, when you plpug a new device in?


All plug&play devices have a standard way to give a product- and a vendorID
(both 16 bits) to the OS. The ENUM key is a munged version of these.
  #8  
Old May 9th 06, 04:28 PM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
external usenet poster
 
Posts: n/a
Default How does windows find the correct device driver?




"Bazzer Smith" wrote in message
...

"mdp" wrote in message
...
Bazzer Smith wrote:
I have been having a load of trouble trying to install an ethernet
card 10/100 NIC thingy, I have an installation disk but that didn't
seem to work properly so I have been trying to do it 'manually' too,
by downloading various drivers which look 'likely suspects'.

Anyway at first when I booted up with the new card in it would detect
it and go to driver installation dialogue and I would point it to
where the driver I wanted to try was. Invariably it would find it,
try to install it, and then fail.
However now when I try the procedure again after making some
adjustment, or just wanting to try it again it doesn't seem to find
the drives in places it had previously found them. It is almost as if
it had remembered "oh that one didn't work before so I will ignore
it!!"
Either that or it deleted then or something.

So.. what I want to know is how windows associates a driver
with a device. I mean if there were a load of drivers in a folder,
which one would it pick, and how does it make it's decision?

The device is question is an ethernet card which has rtl8139(d)
on the chip, however before it detected it as an rtl8129 when
I used the installation disk setup with it, so I aint too sure and I
am a bit confused.

Another point is that initially when I used the installation disk
and some time with out it, when it did find a driver it was happy
with it would prompt me to put my original windows disk in so it
could get some more 'stuff' (drivers etc...). However it never
found what it wanted untill I unzipped a load of the .cab files
(mainly net??.cab), then it did find them (it wanted about 40+
files), it would then say some files were older versions of the files
and ask if I wanted to replace the existing version, I would say no,
this would continue untill it got to telnet.exe (IIRC), I would say
no don't replace it, then my system would hang/crash.
After that I clicked yes to replace telnet.exe to see it that helped
but it didn't.
Now however I said earlier, it will never find the first driver so
I can't get to that stage anymore.
I am at a loss to figure out what is going on and I would reallly
appreciate any advice, especally from folks who understand
what is going on and what to do,as the whold thing seems to be pretty
inconsistant and I can't seem to go back too 'square one'.

My computer still works find though (am using it now), but I
just can't for the life of me get windows to install a drive for the
card.


TIA.


Shouldn't be that hard. Realtek has the drivers he

http://www.realtek.com.tw/downloads/...&Software=True

As far as where how Windows finds the driver, find the entry in the ENUM
key corresponding to your device, then look up (e.g. Google) to see what
info Windows is obtaining from the device.



I think you may have misunderstood me a little, how does windows know
what information to put in the ENUM key, bacially how does it know what
type of device I have plugged into a slot.

Or to put it another way how does windows know what to put int
the EMUN keys in the registry, when you plpug a new device in?



http://www.microsoft.com/technet/arc....mspx?mfr=true

More here from Google:

http://www.google.com/search?hl=en&l...um+98+registry






if you boot into "safe mode" then remove all references of the NIC in device
manager , it should start the process over when you reboot (and let you
select the location you want)

you probably have a few ghost entries in there messing with you :

ps. when it asked for the win98 cd to load additional files ...point it at
c:\windows or c:\windows\system (alternate , if its not found in one , try
the other)
it should find what it needs already there...

hth


  #9  
Old May 9th 06, 04:28 PM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
Haggis[_2_]
external usenet poster
 
Posts: 234
Default How does windows find the correct device driver?




"Bazzer Smith" wrote in message
...

"mdp" wrote in message
...
Bazzer Smith wrote:
I have been having a load of trouble trying to install an ethernet
card 10/100 NIC thingy, I have an installation disk but that didn't
seem to work properly so I have been trying to do it 'manually' too,
by downloading various drivers which look 'likely suspects'.

Anyway at first when I booted up with the new card in it would detect
it and go to driver installation dialogue and I would point it to
where the driver I wanted to try was. Invariably it would find it,
try to install it, and then fail.
However now when I try the procedure again after making some
adjustment, or just wanting to try it again it doesn't seem to find
the drives in places it had previously found them. It is almost as if
it had remembered "oh that one didn't work before so I will ignore
it!!"
Either that or it deleted then or something.

So.. what I want to know is how windows associates a driver
with a device. I mean if there were a load of drivers in a folder,
which one would it pick, and how does it make it's decision?

The device is question is an ethernet card which has rtl8139(d)
on the chip, however before it detected it as an rtl8129 when
I used the installation disk setup with it, so I aint too sure and I
am a bit confused.

Another point is that initially when I used the installation disk
and some time with out it, when it did find a driver it was happy
with it would prompt me to put my original windows disk in so it
could get some more 'stuff' (drivers etc...). However it never
found what it wanted untill I unzipped a load of the .cab files
(mainly net??.cab), then it did find them (it wanted about 40+
files), it would then say some files were older versions of the files
and ask if I wanted to replace the existing version, I would say no,
this would continue untill it got to telnet.exe (IIRC), I would say
no don't replace it, then my system would hang/crash.
After that I clicked yes to replace telnet.exe to see it that helped
but it didn't.
Now however I said earlier, it will never find the first driver so
I can't get to that stage anymore.
I am at a loss to figure out what is going on and I would reallly
appreciate any advice, especally from folks who understand
what is going on and what to do,as the whold thing seems to be pretty
inconsistant and I can't seem to go back too 'square one'.

My computer still works find though (am using it now), but I
just can't for the life of me get windows to install a drive for the
card.


TIA.


Shouldn't be that hard. Realtek has the drivers he

http://www.realtek.com.tw/downloads/...&Software=True

As far as where how Windows finds the driver, find the entry in the ENUM
key corresponding to your device, then look up (e.g. Google) to see what
info Windows is obtaining from the device.



I think you may have misunderstood me a little, how does windows know
what information to put in the ENUM key, bacially how does it know what
type of device I have plugged into a slot.

Or to put it another way how does windows know what to put int
the EMUN keys in the registry, when you plpug a new device in?



http://www.microsoft.com/technet/arc....mspx?mfr=true

More here from Google:

http://www.google.com/search?hl=en&l...um+98+registry






if you boot into "safe mode" then remove all references of the NIC in device
manager , it should start the process over when you reboot (and let you
select the location you want)

you probably have a few ghost entries in there messing with you :

ps. when it asked for the win98 cd to load additional files ...point it at
c:\windows or c:\windows\system (alternate , if its not found in one , try
the other)
it should find what it needs already there...

hth


  #10  
Old May 9th 06, 08:32 PM posted to microsoft.public.win98.gen_discussion,microsoft.public.win98.networking
external usenet poster
 
Posts: n/a
Default How does windows find the correct device driver?


"Haggis" wrote in message
...



"Bazzer Smith" wrote in message
...

"mdp" wrote in message
...
Bazzer Smith wrote:
I have been having a load of trouble trying to install an ethernet
card 10/100 NIC thingy, I have an installation disk but that didn't
seem to work properly so I have been trying to do it 'manually' too,
by downloading various drivers which look 'likely suspects'.

Anyway at first when I booted up with the new card in it would detect
it and go to driver installation dialogue and I would point it to
where the driver I wanted to try was. Invariably it would find it,
try to install it, and then fail.
However now when I try the procedure again after making some
adjustment, or just wanting to try it again it doesn't seem to find
the drives in places it had previously found them. It is almost as if
it had remembered "oh that one didn't work before so I will ignore
it!!"
Either that or it deleted then or something.

So.. what I want to know is how windows associates a driver
with a device. I mean if there were a load of drivers in a folder,
which one would it pick, and how does it make it's decision?

The device is question is an ethernet card which has rtl8139(d)
on the chip, however before it detected it as an rtl8129 when
I used the installation disk setup with it, so I aint too sure and I
am a bit confused.

Another point is that initially when I used the installation disk
and some time with out it, when it did find a driver it was happy
with it would prompt me to put my original windows disk in so it
could get some more 'stuff' (drivers etc...). However it never
found what it wanted untill I unzipped a load of the .cab files
(mainly net??.cab), then it did find them (it wanted about 40+
files), it would then say some files were older versions of the files
and ask if I wanted to replace the existing version, I would say no,
this would continue untill it got to telnet.exe (IIRC), I would say
no don't replace it, then my system would hang/crash.
After that I clicked yes to replace telnet.exe to see it that helped
but it didn't.
Now however I said earlier, it will never find the first driver so
I can't get to that stage anymore.
I am at a loss to figure out what is going on and I would reallly
appreciate any advice, especally from folks who understand
what is going on and what to do,as the whold thing seems to be pretty
inconsistant and I can't seem to go back too 'square one'.

My computer still works find though (am using it now), but I
just can't for the life of me get windows to install a drive for the
card.


TIA.

Shouldn't be that hard. Realtek has the drivers he

http://www.realtek.com.tw/downloads/...&Software=True

As far as where how Windows finds the driver, find the entry in the ENUM
key corresponding to your device, then look up (e.g. Google) to see what
info Windows is obtaining from the device.



I think you may have misunderstood me a little, how does windows know
what information to put in the ENUM key, bacially how does it know what
type of device I have plugged into a slot.

Or to put it another way how does windows know what to put int
the EMUN keys in the registry, when you plpug a new device in?



http://www.microsoft.com/technet/arc....mspx?mfr=true

More here from Google:

http://www.google.com/search?hl=en&l...um+98+registry






if you boot into "safe mode" then remove all references of the NIC in
device manager , it should start the process over when you reboot (and let
you select the location you want)


I will try that but I may need some futher help/advice.


you probably have a few ghost entries in there messing with you :

ps. when it asked for the win98 cd to load additional files ...point it
at c:\windows or c:\windows\system (alternate , if its not found in one ,
try the other)
it should find what it needs already there...


Thanks I tried something similar to that, I unzipped some of
the cab files into a folder, I probably should have done it as you
said but anyway it dis seem to find what it wanted but it still
resulted in failure!!

hth



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Win98SE constant problems-ole32,shell32,other MEB General 14 January 15th 06 05:39 AM
Can't listen audio/realone files while MSN Tuning vizard is working Thaqalain General 0 October 22nd 05 10:37 PM
Device Manager Problem cpojano General 9 October 6th 05 07:25 AM
windows fails to detect sound card Damon Setup & Installation 28 September 30th 05 03:42 PM
New Install of Windows & W-TShooters question Star General 26 August 30th 04 07:48 AM


All times are GMT +1. The time now is 12:33 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.