Re: Bad DLL? Bad device driver?

Lord Gazwad of Grantham wrote:
> sbb78247, <sbb78247@don'tknowdon'tcare.invalid>, the friendless,
> infective grinner, and examiner of food on sale at the markets,
> prattled:
>
>> Lord Gazwad of Grantham wrote:
>>> sbb78247, <sbb78247@don'tknowdon'tcare.invalid>, the
>>> bacteria-infested, beetle-browed art teacher, and upholstery
>>> stuffer, beefed:
>>>
>>>> Lord Gazwad of Grantham wrote:
>>>>> sbb78247, <sbb78247@don'tknowdon'tcare.invalid>, the cowardly,
>>>>> tinkling grease monkey, and mender of hoes, wanted to
>>>>> talkee-talkee about:
>>>>>
>>>>>> Lord Gazwad of Grantham wrote:
>>>>>>> Malcolm, <user@xxxxxxxxxxxxxx>, the mendicant, indecent arse
>>>>>>> pirate, and gambling prostitute, skulked:
>>>>>>>
>>>>>>>> Came in to find Symantec reporting that I had a
>>>>>>>> Trojan.ByteVerify infection. It had quarantined the file. I
>>>>>>>> then had to: turn off System Restore, restart in Safe Mode,
>>>>>>>> re-scan the computer (took ages, found nothing), and then boot
>>>>>>>> normally, and restore System Restore. Plus whenever I get the
>>>>>>>> Properties of My Computer, I get a dialogue that says:
>>>>>>>>
>>>>>>>> The application or DLL C:\WINDOWS\system32\netid.dll is not a
>>>>>>>> valid Windows image. Please theck this against your
>>>>>>>> installation diskette.
>>>>>>>>
>>>>>>>> I have no idea what this means but it can't be good. I have
>>>>>>>> several other "bad DLL" boxes come up at times too.
>>>>>>>>
>>>>>>>> I'd not been able to hibernate for a while before this
>>>>>>>> happened. I've received a dialog box about inability to
>>>>>>>> hibernate that says:
>>>>>>>>
>>>>>>>> "The device driver for the 'IEEE 1284.4 compatible printer'
>>>>>>>> device is preventing the machine from entering hibernation.
>>>>>>>> Please close all applications and try again. If the problem
>>>>>>>> persists, you may need to update this driver."
>>>>>>>>
>>>>>>>> The WEIRDEST thing by far is that when I run Visual dBase and
>>>>>>>> do a browse, whatever I type is replaced by the old value
>>>>>>>> after a moment or two!
>>>>>>>>
>>>>>>>> Can anyone make a recommendation?
>>>>>>>>
>>>>>>>> It's a Dell that was brand new last February.
>>>>>>>
>>>>>>> In the first instance, back-up all your data.
>>>>>>> Find out the manufacturer of the hard drive and use a utility to
>>>>>>> run some thorough diagnostics and then to write zeros to the
>>>>>>> drive. Then use the disks that came with the machine to put it
>>>>>>> back to how it was when purchased.
>>>>>>> You should then ensure you are adequately protected against
>>>>>>> viruses, trojans, spyware etc.
>>>>>>> See if the problems come back, it could be something malicious
>>>>>>> or it could be a fucked hard drive, often the diagnostics would
>>>>>>> give you adequate warning but not always. It's also a good move
>>>>>>> to use another utility to display the values of the S.M.A.R.T.
>>>>>>> data held on your disk.
>>>>>>>
>>>>>>> You may find upon inspection that the machine is full of dust
>>>>>>> bunnies, blow out any dust with a can of compressed air. Lack of
>>>>>>> cooling could cause problems with the hard drive. You might as
>>>>>>> well go the whole hog and run some diagnostics on your RAM too.
>>>>>>
>>>>>> uh oh, better watch out! that cuntfart w-tom or something like
>>>>>> that will tell you that heat and dust are not a problem but then
>>>>>> later contradict himself after he advises you to get out the
>>>>>> multimeter.
>>>>>
>>>>> I used a multimeter in connection with a PC once. Well, strictly
>>>>> speaking it wasn't a PC and I also used a soldering iron and a
>>>>> wooden mallet.
>>>>
>>>> tools of the modding trade
>>>
>>> If you add pliers and a blowtorch, yes.
>>
>> and a spray gun - beige is quite the boring color
>
> Of what do you speak? I have aluminium cases for my PCs.

Us po' folks only have one aluminum in the lot. the other 2 are steel
premod jobs that i am constantly updating for better air flow, pimp lighting
or what ever.
--

sbb78247

Speak the truth and leave shortly there after.


.

Quantcast