Posts by DMR

Thanks to you as well :)

See you next week!

Ah, to be sure- we await your return with bated breath.

:mrgreen::mrgreen:

As Catweazle said, your best bet is to crack the case and check the model/part # of the battery. Many are the flat, round "watch-style" (CR-2032 or similar), but not all.

<end rant>

Sorry folks, but this forum is for discussing members' hardware problems and helping them resolve those problems.

It is not a venue for airing grudges or for verbal jousting between dissatisfied customers and representatives of the "accused" corporation.

We are indeed done here.

I have same problem. Nothing gets rid of it. The only difference between what I've tried and what you said is running in safe mode. I'll give it a shot.

Phaelax,

If you need to repost, please start your own thread insteAd of continuing here. To keep threads clear and concise, we ask that members abide by our policy of "one member, one problem" per thread.

Thanks :)

As YzK said, download and run HijackThis and post the log file it generates. That will allow us to see exactly what "guests" you've still got in your system.

Also, Ad Aware, SpyBot, and the like will usually nail 99% of the "malware" programs, but only if you keep them very up to date!!! Use the "check for new updates" functions of utilities often; updates are sometimes released within days of each other. Just like your anti-virus program, these utilites are useless if you don't keep them current.

Vanth!!!! Post in you own thread & have some consideration please.

Yes, Vanth- in the future, please start your own thread when you have a problem. Read the "Forum rules when posting" announcement posted at the top of this forum for more information on our posting policies.

I've (obviously) split your post and its responses into their own thread this time, but having to do so does make extra work for us.

Thanks for understanding. :)

-DMR

Have HJT fix the following entry:

O4 - HKLM\..\Run: [RunDLL] rundll32.exe "C:\WINDOWS\system32\bridge.dll",Load

Reboot and delete the C:\WINDOWS\system32\bridge.dll file if it still exists.

You also have the MySearch parasite; download and run SpyBot and Ad Aware to remove that and other possible "unwanted guests" from ytour system. Download links and instructions for SpyBot and Ad Aware have been posted in many recent threads here; have a look through those threads for more general "malware" removal suggestions as well.

I've split your post in the older, original "Pictures not showing up..." thread into its own thread here.

In the future, please start your own threads when you have problems, even if your problem is similar to one in an existing thread. When multiple people "piggyback" their questions onto someone else's thread it becomes increasingly difficult to keep track of whose answers relate to whose questions.

Thanks for understanding,

-DMR

:)

Moved to the new Security forum, as that's where virus/spyware/malware/etc. questions now belong.

:)

JoeOneEye:

I've split your posts (and their responses) into their own thread in the Security forum. The new thread is located here:
http://www.daniweb.com/techtalkforums/showthread.php?t=5839

In the future, please start your own threads when you have problems, even if your problem is similar to one in an existing thread. When multiple people "piggyback" their questions onto someone else's thread it becomes increasingly difficult to keep track of whose answers relate to whose questions.

Thanks for understanding,

-DMR

:)

It might not be blaster- make sure you have the latest virus definitions for your A-V program, and run a full system scan.

Give us the exact text of the error. Also have a read through the posts in this thread; a few causes of (and solutions to) svchost problems are discussed there.

Read through some of the posts in our Security forum for information on some of the recommended "malware" detection and removal tools. Try those programs and see if they find anything.

If the above suggestions don't give you the fix and you decide to post a HijackThis log, please do that in the Security forum, and be sure to include details of the troubleshooting steps you've taken up to that point.

You could try booting into the rescue console from you install disk. From there the automatic repair utility might be a ble to fix things. Even if not, you might be able to fix it manually or at least be able to poke around for clues.

What exact error do you get when you try to create the new partition?

have you:

- booted from a floppy which has the fdisk program on it
- run fdisk from there and deleted the partition
- written your changes
- rebooted
- tried the Win2k install again

It depends- what browser (including version) do you use?

Windows XP won't allow you to create FAT32 partitions any larger than 32Gb.

Right- I forgot about that, but it is true.

netfisher,

There you have it- the 3 places where you could hit the 32G limit are:

1. The BIOS
2. The 32G clip on the drive
3. The fact that XP won't create a FAT32 partition >32G. XP can handle FAT32 partitions >32G, it just won't let you create them (the max size of a FAT32 partition is 2TB).

Some of the differences between the FAT32 and NTFS filesystems are outlined here.

Hi mink, I see that this is your first post here, so first things first- welcome! :)

Because your problem seems Internet-related, and you say that you use Internet Explorer as your browser, my guess is that your system has become infested with one or more of the many "unwelcome" trojan/spyware/etc. programs that have been running rampant lately.

This might not be the case, but my intuition says that we should check for these problems first. Read though some of the threads in our Security forum to find info about how to download and use many of the (free) utilities that will remove these malicious programs, and post a new thread there (the Security forum) if the utilities do detect anything suspicious.

I'm sorry if our replies in you earlier thread seemed confusing, but instead of starting another separate thread on exactly the same subject, please continue posting any questions you have regarding the problem in your original thread.

I'm closing this thread so that any help you do get from here on doesn't end up getting spit between this thread and your original thread- thanks for understanding.

:)

Don't sweat it- any operating system is a steep learning curve if it's not not the one you're used to using.

A shameless plug that will help you if you want to learn Linux:

Both Alex (alc6379) and I moderate a very good Linux-oriented tech support site at www.justlinux.com. Check out the site and register as a member; we've got a lot of very knowledgeable members over there who are more than willing to help you make the "learning curve" less steep. :)

phatbacky,

We do ask that members start their own threads when they have problems, regardless of how similar a problem in an existing thread might seem. It becomes very difficult to keep track of whose responses are directed toward whose questions otherwise.

Please start a new thread of your own, and when you do, please include as much information as possible:

-Your version of Windows
-The make/model of CD drive
-The name and version # of the CD-ROM's driver which you are trying to install (and where you got the driver).
- The exact text of any error messages you may have gotten.

Very cool; you're welcome.

A nightmare perhaps, but if copying the contents of the i386 folder allowed you to fix the problem, then life is good. :)

(Marking this as solved)

Many programs, even legit ones (anti-virus software for example), can write to disk at random times. This will often cause disk maintenance programs to give you a warning to that effect, or to just restart their entire procedure from the beginning if they sense a change to disk contents in the middle of their run. As caperjack said, running in safe mode can often get around this.

What exactly do you have running? Post not only your running programs, but running processes as well.

Right-click on the My Computer icon and choose "properties". From there, navigate to Device Manager and see if the CD is listed there. If it is, does it have a yellow "!" or red X next to it?

Were you making any changes to the system just prior to the drive's disappearance (think carefully)?

If the IP you found the system assigned to itself was in the 169.254.x.x range, that means that your box could not connect to the DHCP server. Linux, Windows, and Mac boxen will all default to that range if unable to obtain a valid IP via DHCP.

You definitely do need to have a DHCP client running, and as already mentioned, if you accidentally installed and ran a DCHP server on the Linux box you'll have conflicts.

dhclient, dhcpcd, and pump are the three most-used DHCP client programs. You can see if you have one of them running by opening a terminal window and typing the following two commands:

ps ax |grep dhc
ps ax |grep pump

Also, posting the exact text of the "could not join..." error would be of great help. You can view your bootup message/error log with the following command; anything helpful in there?:

dmesg |less

Hi BATMAN, first of all- welcome! :)

A word of advice since you're new to this forum: In the future, please try to use a thread title which describes your problem more specifically than simply "Help!"; you'll catch the eyes and interest of those who can help with your particular problem more quickly. A more unique title will also help us track your thread as we work our way through the solution. (I've already edited the title of this thread for you).

Also, due to the huge increase in virus/spyware/adware-related problems that our members are experiencing, we've created a new Security forum specifically to address these problems; I'm moving your thread there now.

Have a good read through the other threads in Security; you've got a bunch of nasty guests on your system and a lot of information on how to remove them has already been posted in those threads. Try the removal utilities recommended in hte threads and post a new HJT log after you've run them.

netfisher,

Check the jumpers on the drive itself. Many larger drives have a "32GB clip" setting which forces the drive to report itself as being only 32G in size to accomodate the 32G limit present in some BIOSes. If you know that your BIOS can handle drives larger than 32G, set the clip jumper to "off". Check your drive's documentation if the jumper settings aren't printed directly on the drive.

The "06" is the error code for an invalid operation, and an incorrect or corrupt driver could certainly cause this error.

This error is returned if any one of the following conditions are true:
The processor tries to decode a bit pattern that does not correspond to any legal computer instruction.
The processor attempts to execute an instruction that contains invalid operands.
The processor attempts to execute a protected-mode instruction while running in virtual 8086 mode.
The processor tries to execute a LOCK prefix with an instruction that cannot be locked.

The remaining portion of the error is the pointer/offset combination specifying the location in memory where the invalid instruction occured. The numbers in this portion of the error will vary depending on the exact program/piece of code that caused the error.

alright for the moving but that doesn't help me.

Perhaps not, but it does help us keep all of these spyware/adware/malware posts in one place.
Also- patience is key here, and please remember that we do this on a volunteer basis.

caperjack and crunchie are very helpful and knowledgeable in this area; if the answers they've given you haven't solved your problems yet, don't worry- they'll be back to help soon. :)

At the very least, have HJT fix anything and everything related to "MyWebSearch".

just for the record !!Coolwebsearch browser hijack variants are not viruses!!

Picky, picky, picky....

:mrgreen:

Moving to the new Security forum, as this is spyware-related. :)

Moving to the Security forum. Please read through the other posts in Security to find out more about Ad Aware, SpyBot, and other trojan/spyware/malware removal tools.

Moved to the new Security forum, as this is a spyware/malware issue. :)

Moving to the Security forum, as this is a spyware/malware issue. :)

First of all, let's figure out if the problem might not be being caused by something malicious that didn't get removed. Could you run HijackThis again and post a copy of the log file here please? If you're system is clean, we can start looking at the possibility that you did indeed delete a necessary reg key.

Yes, you've got unwanted guests alright. I'm moving this to our new Security forum, as that is where we're concentrating spyware-related posts.

Instructions for removing the malicious programs from your computer have been posted many times in the other threads in the Security forum. Read through the threads to find out where to download the necessary removal utilities. Look for posts by our member "caperjack"; he has links to these utilities and other useful sites in his signature file.

Once you've run the recommended utilities, run HijackThis again and post your new log.

By the way, I see that this is your first post here- welcome! :)

As you seem to know, XP Home only has the Remote Desktop client software, but there are a couple of good (and free) third-party RD solutions which will do the job for you quite well. Both the client and the server components of these programs will also work on other versions of Windows. They work on Linux too, if you're *cough* *plug* interested in that OS. :D

Try VNC or TightVNC

The sasser worm is quite recent. If Norton wasn't updated regularly, the virus signature files wouldn't have identified it.

Yup; new sasser detection/removal tools were posted just two days ago.

If it is one of the recent virii, download and run McAfee's Stinger utility. It will deal with both the Sasser and MSBlaster worms. After that, definitely make sure that your anti-virus program is set to auto-update itself; even being a week or two out of date on your virus definitions can put you at risk.

OK, here's more info on the original error:

http://www.google.com/search?hl=en&lr=lang_en&ie=UTF-8&oe=UTF-8&q=%22IRQL_NOT_LESS_OR_EQUAL%22+NTOSKRNL.EXE&btnG=Search

You might have a hardware or driver problem; check Microsoft's Hardware Compatibility List (and search the web) to see if there are any known issues with your particular motherboard and system components.

As for the new drive, you might want to find a way to wipe the thing entirely; it sounds like problems are just getting compounded here. Since the CD-ROM approach doesn't seem to be getting you anywhere, a Win boot disk with the fdisk program on it, or putting the drive in another computer, are a couple of possibilities.

Yay, I downloaded a new driver and everything is good again. Thanks so much for the help Caperjack, and DMR. I really appreciate it.

Glad we could help you get it sorted- after all, that's why we're here. :mrgreen:

OK, glad you got it sorted.

I'll mark this thread as solved; hopefully that'll be true ;)

Hmm, it sounds like it's using the ATI driver, but you might try a driver update/reinstall anyway; it could have gotten corrupted somehow. Go to ATI's site and download whatever is the most current Win 98 driver package for your card.

Are there any other steps I need to take after this to help restore the color and size?

Sounds like something might have forced your card into using a generic VGA driver. Under your video card's properties in Device Manager, check to see which driver the card is currently using. If it's set to use a generic VGA/SVGA driver, either locate/reinstall the ATI driver for your card or download it from ATI's driver site.

Please post the exact and complete text of the error message; we need that information to make an accurate assesment.

If the error related to lsass.exe crashing, you almost certainly have a variant of the sasser worm. See this article for more information and a link to the removal utility.

BTW- I see that this is your first post. Welcome! :)

Please have a read through some of the other threads in this forum. In them you'll find instructions for downloading and running SpyBot, Ad Aware, CWShredder, and a few of the other recommended spyware/trojan removal utilities.

Once you've run those programs, run HijackThis again and post the new log.

error code 06:0028:00000002 press any key to continue or...

Is that the complete and exact text of the error? If not, please post the error exactly as it appears on your screen, along with any other info that might appear in the error dialog box.

What patch? Where does it hang?

The first thing you need to do is give us some details to go on. We'd love to help, but we can't read minds. :mrgreen:

- Post your system specifications.
- Post details of the problem, including the exact text of any errors/messages you get. Give us some history on the problem.
- Tell us exactly which patch you're refering to.

First of all- does it work if you boot into safe mode?

You've definitely got unwanted guests. :D
The first thing to do is to download and run these two (free) removal tools:

Ad Aware
SpyBot Search & Destroy

Close all programs, run one of the utilities (the order doesn't matter), allow it to fix everything it finds, reboot, run the other utility, lather, rinse, repeat.

Once both tools have done their job, run HJT again and post the new log.

(You should let HJT fix any "bridge.dll" references it finds. Once done, search your system for "bridge.dll and delete any files of that name.)

If you mean the "NTLDR missing" error, that can happen for a few reasons.

1. Sometimes the install just glitches, and a second try will work.

2. The drive's IDE cable isn't seated properly, or the Master/Slave jumpers on the drive are set incorrectly.

3. Your drive's geometry is incorrectly interpreted by the BIOS.

4. Your boot.ini file is misconfigured. Assuming a single partition on the Primary Master drive, the relevent boot.ini entries should be similar to:

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

Note the "multi", "disk", "rdisk", and "partition" values; they should be as given above. If they aren't, you'll have to boot from a floppy or the install CD and edit the file.

5. The NTLDR and/or NTDETECT.COM file is corrupt. You can try to fix this by booting into the rescue console from the CD. Locate the two file on the CD and copy them both to the root directory of your drive and reboot.