PC Review


Reply
Thread Tools Rate Thread

the annoying windows xp error code 39!!!!

 
 
New Member
Join Date: Jun 2008
Posts: 7
 
      20th Jun 2008
hi,
i tried to install a wifi dongle, but got an error 39 when i installed the drivers. i tried EVERYTHING any forum has told me to do, and yet nothing.
if this helps, i tried earlier in the year, to install an ethernet card, which also failed with error code 39. all of the network adapters seem to be getting an error code 39.

i am running windows xp SP2, and have tried both devices on other windows pc’s, and they work great.

i’ve updated chipset, bios, even done things on regedit, no luck.

any advice to fix this annoying error would be VERY MUCH GREATLY appreciated.

cheers

ps. i have formatted, reformatted, and did it again. i've tried doing vague things on regedit, which resulted in the system not recognizing ANY net adapters. now i am back on ground zero with this. please please reply!!
 
Reply With Quote
 
 
 
 
New Member
Join Date: Jun 2008
Posts: 7
 
      20th Jun 2008
oh, i thought i'd just add, it was a pre manufactured computer, and someone was throwing it out.
so since then, the hard drive has changed (i think it was FAT32 40GB to run windows ME) to NFTS 80GB(XP SP2)
but as i've said, i've done numerous formats, and im exhausted on any other ideas as to solutions..
 
Reply With Quote
 
sugar 'n spikes
floppybootstomp's Avatar
Join Date: Mar 2002
Location: Greenwich
Posts: 16,347
 
      20th Jun 2008
It looks as if the machine you're using is quite old and may be having problems recognising/using the components you're trying to use.

From what you've said, these components are not faulty so it's obviously a problem with the computer's hardware, it's motherboard and associated componets.

You've also updated the BIOS so I really am at a loss.

Have you gone through the BIOS and satisfied yourself that every setting is correct?

If so, in view of what you've said, I honestly don't think the dongle is going to work with that thrown out manufactured computer (Dell? Compaq?).

I do hope I'm wrong but I'm not optimistic.

 
Don Van Vliet 1941 - 2010. And the acid gold bar swirled up and down, up and down.
 
Reply With Quote
 
Senior Member
itsme's Avatar
Join Date: Apr 2005
Location: United Kingdom
Posts: 6,151
 
      21st Jun 2008
FBS is correct. As it is OLD like me No worky correct.



Code 39

Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
Recommended resolution

Reasons for this error include a driver that is not present; a binary file that is corrupted; a file I/O problem, or a driver that references an entry point in another binary file that could not be loaded.

Uninstall the driver, and then click Scan for hardware changes to reinstall or upgrade the driver.

On the General Properties tab of the device, click Troubleshoot to start the Troubleshooting Wizard.

 
If MS ever make anything that does not suck it will be a> Vacuum cleaner



In nature, nothing is ever right. Therefore, if everything is going right... something is wrong.
 
Reply With Quote
 
New Member
Join Date: Jun 2008
Posts: 7
 
      21st Jun 2008
Quote:
Originally Posted by floppybootstomp
It looks as if the machine you're using is quite old and may be having problems recognising/using the components you're trying to use.

From what you've said, these components are not faulty so it's obviously a problem with the computer's hardware, it's motherboard and associated componets.

You've also updated the BIOS so I really am at a loss.

Have you gone through the BIOS and satisfied yourself that every setting is correct?

If so, in view of what you've said, I honestly don't think the dongle is going to work with that thrown out manufactured computer (Dell? Compaq?).

I do hope I'm wrong but I'm not optimistic.
thanks for the replies
hi, it isn't that old, not old enough for components to not work, as other ones work completely fine.
and before i got it, there was a network card on it (factory) but the previous owner obviously needed/wanted that, so they took it out. and then no other network adapters, and network adapters only, have been working on this pc.

Quote:
Originally Posted by itsme
Reasons for this error include a driver that is not present; a binary file that is corrupted; a file I/O problem, or a driver that references an entry point in another binary file that could not be loaded.
what is this binary or I/O thing? it sounds related, maybe i should fiddle with that? how do i get to it?

(i've uninstalled and done the lot,)



what are the odds of pc world pc clinic being able to fix it? the people in the clinic in my area don't seem to very competant, and they failed to fix 2 of my previous problems..
 
Reply With Quote
 
sugar 'n spikes
floppybootstomp's Avatar
Join Date: Mar 2002
Location: Greenwich
Posts: 16,347
 
      21st Jun 2008
PC World clinic are generally incompetent and over priced. Your last words confirm this.

And did you check the BIOS settings?

And what type of port does the dongle plug into?

 
Don Van Vliet 1941 - 2010. And the acid gold bar swirled up and down, up and down.
 
Reply With Quote
 
Senior Member
itsme's Avatar
Join Date: Apr 2005
Location: United Kingdom
Posts: 6,151
 
      21st Jun 2008
Quote:

what is this binary or I/O thing? it sounds related, maybe i should fiddle with that? how do i get to it?

Input output.

Quote:
(i've uninstalled and done the lot,)
What you mean! the OS?

Quote:
what are the odds of pc world pc clinic being able to fix it? the people in the clinic in my area don't seem to very competant
About 1 in 1000

There are quite a number of us on this forum who could fix it but not being able to see it in front of them it is quite difficult. Glad you have sorted it

 
If MS ever make anything that does not suck it will be a> Vacuum cleaner



In nature, nothing is ever right. Therefore, if everything is going right... something is wrong.
 
Reply With Quote
 
New Member
hollydolly's Avatar
Join Date: Jun 2008
Location: Macungie, Pa
Posts: 17
 
      21st Jun 2008
this is what ms says "Code 39 Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
Recommended resolution

Reasons for this error include a driver that is not present; a binary file that is corrupted; a file I/O problem, or a driver that references an entry point in another binary file that could not be loaded.

Uninstall the driver, and then click Scan for hardware changes to reinstall or upgrade the driver.

On the General Properties tab of the device, click Troubleshoot to start the Troubleshooting Wizard. "


other searches make reference to registry errors but I do not think these are related to you.
 
Reply With Quote
 
New Member
Join Date: Jun 2008
Posts: 7
 
      22nd Jun 2008
[QUOTE=hollydolly]
Reasons for this error include a driver that is not present; a binary file that is corrupted; a file I/O problem, or a driver that references an entry point in another binary file that could not be loaded.

[QUOTE]

could someone please explain this binary thing please? it is not the driver nor the registry, as i have formatted my computer several times, and also, the driver works on other computers.

but binary file... hmm sounds interesting.. any tips?
cheers
 
Reply With Quote
 
Senior Member
itsme's Avatar
Join Date: Apr 2005
Location: United Kingdom
Posts: 6,151
 
      22nd Jun 2008
If you feel you can do it be careful http://www.angelfire.com/country/ald...aryFileIO.html

 
If MS ever make anything that does not suck it will be a> Vacuum cleaner



In nature, nothing is ever right. Therefore, if everything is going right... something is wrong.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

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

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows XP Media Center - Very annoying error message Captain Jack Sparrow Windows XP 4 19th Oct 2008 05:44 PM
Failed Windows Update for Flash causing annoying error on bootup.. =?Utf-8?B?Sm9zaEdmcm9tUG9ydGxhbmQ=?= Windows XP General 6 16th Feb 2007 09:08 PM
Annoying Windows Explorer error elorahd Windows XP General 5 7th Sep 2005 01:17 AM
windows XP annoying error messages JR Windows XP General 2 12th May 2004 06:24 AM
How to Disable Media Sense for TCP/IP in Windows or stop annoying error message Joe Windows XP Networking 1 14th Oct 2003 08:10 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 09:54 AM.