Posts by DMR

Is the pattern of the beeps always consistent? If so, what is the pattern/duration and how many times does it repeat? For example: one lonng beep-two short beeps- two long beeps.

Definitely try to clear up the issues with the sound and video card; chances are pretty good that you problem will stop then. If not, I'd swap RAM sticks next, or run memtest86 to stress-test the RAM.

:o Awww, come on now- we're just humble little geeks tryin' to help. :)

Sorry- don't have much time to reply right now, but have HJT fix these for starters:

R3 - URLSearchHook: (no name) - _{CFBFAE00-17A6-11D0-99CB-00C04FD64497} - (no file)
O10 - Hijacked Internet access by WebHancer
O10 - Hijacked Internet access by WebHancer
O10 - Hijacked Internet access by WebHancer
O10 - Hijacked Internet access by WebHancer
O10 - Hijacked Internet access by WebHancer
O16 - DPF: {56336BCB-3D8A-11D6-A00B-0050DA18DE71} (RdxIE Class) - http://207.188.7.150/26606925564226...ip/RdxIE601.cab
O16 - DPF: {08BEF711-06DA-48B2-9534-802ECAA2E4F9} (PlxInstall Class) - http://www.plaxo.com/activex/PlaxoInstall.cab
O18 - Filter: text/html - {70A3F011-A9C0-4929-A84E-CC1C6B92FEE6} - C:\WINDOWS\SYSTEM\FBP.DLL
O18 - Filter: text/plain - {70A3F011-A9C0-4929-A84E-CC1C6B92FEE6} - C:\WINDOWS\SYSTEM\FBP.DLL

Delete the contents of all Temp, Temporary Internet Files, and Cookie folders. Empty your recycle bin. reboot.

also... u might want to try and update ur hijack this becuase ur thing didnt find the 018 files like mine did...

Good catch Silent; thanks. Yes- HJT is currently at version 1.98.

LSchwartz0,

Download and run the latest version of HJT and post a fresh log so that we can verify that you're clean; a lot of these nasties will pop back to life if you haven't removed every single bit of them.

Guilty here as well- sometimes I'm just trying to audit as many posts as possible that I skim over the obvious. Oh well, one of the downsides of our being both responders and mods I guess...

Your log file is missing important header information. Please close all open programs (especially your web browser), run HJT again, choose the option of saving the logfile (don't have it fix anything yet!), open the logfile in Windows Notepad, and cut-n-paste the entire contents of the file here.

You'd be surprised how quickly dirt and dust can build up inside your computer's case- it isn't a bad idea to check on the accumulation every couple of months.

#1- Uninstall NoAdware; the program is bogus. More on the reasons why here:

http://www.spywarewarrior.com/rogue_anti-spyware.htm

You're fairly well infested; I'm moving this to our Security forum so that our virus/spyware experts can look through your log. (By the way, just for future reference you should be aware that the Security forum is the only forum on this site where HJT logs should be posted).

D-oh! Sorry Terry- missed that... :o

Normally I would agree with you Alex, but get this- the size of HP's recovery partition can be on the order of GigaBytes these days. I know that a lot of vendors have found that to be a cheap and easy way of giving customers some sort of a recovery solution without the vendor having to manufacture and ship a separate set of recovery CDs, but:

A) A set of recovery CDs may still be obtainable if you contact the vendor., and they may come at no cost if you request them within a certain time-frame after purchasing the computer. This is a more robust solution IMHO anyway- what if your whole drive gets seriously whacked? Having your recovery data on the same drive as the operating system isn't going to help in a case like that. I can attest to that scenario, because I've had to deal with it personally.

B) Those "diagnostic" or "recovery" partitions can play holy hell with many partitioning/formatting utilities, especially when it comes to setting up multi-boot systems. You've probably run across over at JL; I know I have.

I will say that Catweazle's suggestion of simply adding another drive is the safest approach, especially for those not comfortable with advanced/complex partition management. 40G or so drives are comparatively dirt-cheap these days, and you can free up a lot of space on your system drive just by moving much of your data files to such a drive. The other good thing …

A) Remove Spyware Begone- the program is bogus. See the following link for an explanation:

http://www.spywarewarrior.com/rogue_anti-spyware.htm

B) You should download and run Ad Aware and SpyBot, as well as do an online virus scan; that will clear up a lot of your problems. Instructions for doing so, as well as other solutions which address some of your exact problems, can be found in the link below:

http://forums.thatcomputerguy.us/index.php?showtopic=4703

C) Once you've done the above:

- create a new, separate folder for HijackThis somewhere on your hard drive that is not inside a Temp/Temporary/Temporary Internet folder (C:\HijackThis, for example). Move HJT to that folder and run it from there from now on.

- close all open programs, especially Internet Explorer; HJT cannot perform all of its fixes if IE is running.

- run HJT again and post a fresh log.

Hi dmm5702, welcome to TechTalk :)

We ask that members not tag their questions on to a thread previously started by another member (regardless of how similar your problem might seem). Not only does it divert the focus of the thread away from the original poster's problem, but it also makes it less likely that you yourself will get the individual attention that you need.

Please start your own thread and post your question there. When you do, please try to give us as much specific info as possible regarding the problem (exact error messages, system specs, etc.).

For a full description of our posting guidelines and general rules of conduct, please see this page:

http://www.daniweb.com/techtalkforu...b_faq#faq_rules

Thanks for understanding.

Do the following commands show the proper default gateway and routing information?:

ipconfig /all
route print

If so, you might want to look further into the possibility of damage by a malicious program. Look through the threads in our Security form for information on using Ad Aware, SpyBot, HijackThis, and other tools. If running those tools leads you to suspect an infection, start a new thread in Security and post as much info there as possible in terms of waht you've done and the results you've gotten.

The trick is to change the hidden recovery partition's type code to make it "visible", and then use a partition manager such as Partition Magic to merge the space into your system drive. There are a few ways to do this, including using some freely available Linux utilities; there are a number of suggestions in this thread:

http://www.experts-exchange.com/Miscellaneous/Q_21013072.html

Check out:

http://support.microsoft.com/default.aspx?kbid=822798

http://support.microsoft.com/default.aspx?kbid=828031

... or the switch port you are plugging into does not correctly negotiate autoconnect...

Yes- if changing the cable doesn't hep, try a different port as well.

If those suggestions don't do the trick, it might be time to look "inside the box":

- Have you verified that the TCP/IP stack is functioning correctly by pinging the loopback device?:

ping 127.0.0.1
or
ping localhost

- Can you ping the IP of the NIC? Can you ping the computer by its hostname?

- When you say that it isn't sending or receiving packets, what utility are you using to determine this?

<edit>

This being essentially a networking question, I'll move this thread to the networking forum...

</edit>

Those stop errors point either to faulty RAM or a kernel-level process gone haywire. Have you changed any hardware or upgraded drivers or other critical software lately? Also, what kind of sound card do you have? The second stop code can be related to a driver issue with Audigy sound cards.

That's fine. If your current programs do the job for you and run properly in Classic mode there's really no need to spend extra $$ getting the native OS X versions.

I agree with Alex- configuring Samba through SWAT or Webmin doesn't always work the way you want/expect it to; setting up your smb.conf file by hand is not only more reliable, but it will give you a deeper knowledge of how Samba really works.

Both Alex and I also work at another tech support site (which is totally Linux-oriented), and our archive there contains a lot of helpful instructions, links, etc. on Samba-related isssues. If you have a read through some of the archived threads there, you'll find answers to a wide range of questions that commonly crop up when learning to set up Samba for the first time. Here's a link to many of those threads:

http://www.justlinux.com/forum/search.php?action=showresults&searchid=993899&sortby=lastpost&sortorder=descending

About the fans and dust and that. all my fans are working perfectly i guess. Havent opend the "main" fan. should I?

You probably don't need to do that. You can usually tell if the main power supply fans are running without taking anything apart.

Still about this Memtest program, i dont get it. I run install.bat getting in to the dos. and what should i write after that? it says it need a formated disk in a or b. i dont got any disks. do i need?

Unfortunately, memtest86 wants to be run from a bootable floppy disk. If you don't have any IBM-formatted floppy disks, you need to get one. If your computer doesn't have a floppy drive, memtest is also supposed to be able to be burned to a CD-ROM, but I've never used it that way so I don't know how difficult that would be to do.

Ahha, about safemode. I only go to Safemode when iam getting rid of Virus. never really been there for along time..

Right- people usually only go in to safe mode for short periods of time to do something like a virus scan or a quick repair. Since you've said that it may take up to a week for the problem to happen, booting into safe mode probably isn't going to be able to tell us anything. You won't really be able to use the computer in safe mode that long if you need …

djwazzup06

make an own thread :P

Yes.

djwazzup06,

We ask that members not post their own questions to a thread started by another member, regardless of how similar the problems might seem. Doing so takes the focus of the troubleshoot away from the original poster's problem and just generally makes the thread more confusing. Additionally, your question won't get the individual attention in needs either.

Please start your own thread here and post your info in that thread.

Thanks :)

FTP is the File Transfer Protocol (I think). I don't know what you've been using before, but if you've not heard of ftp then you're probably uploading via a form type interface I guess.

"File Transfer Protocol" is correct, and yes- I'd guess rhiannon is currently using a Web (HTTP) form-based interface. The only problem with trying an FTP upload is that, because it is a different network service/protocol than HTTP and uses different ports than HTTP, the server to which you want to upload has to have FTP set up on its side as well. If not, it won't understand your FTP request and you won't be able to connect.

rhiannon- is it possible that although the hosting site allows uploads of up to 50K, your ISP might have a lower cap on filesizes? Just a thought...

Your right Terry- I think the trick probably is ages old; I know it was many years ago that I heard about it. I never did have the "luxury" of trying it before now though; the companies I've worked for in the past knew their data was mission-critical and always has RAID redundancy, extremely current backups, and/or spare controller cards that I could swap onto a dead drive. My clients currently are mostly small office/home office operations, many of whom I find to have little or no backup strategy in place... I guess that means I'll probably get to try this little trick again in the near future. ;)

In the different discussions I read, people had varying levels of success, and many different "recipes" for the procedure, including freeze times ranging from 15 minutes to 24 hours. Having already identified an overheating chip on the controller card (and not having a replacement card) I knew that the freeze method could be a one-shot, last-chance procedure for me, so I opted to leave the beast in the freezer overnight just in case.

One creative technique mentioned in one of the discussions was to rest the drive on top of one of those plastic "Blue Ice" reusable freeze blocks (the kind made for camping/picnic coolers) once you remove the drive from the freezer and hook it back up. The freeze block keeps the drive from heating back up as quickly as it normally would, thus extending your …

SWAT is the Samba Web Administration Tool, and you'll need instructions to get that going if you want to use the tool; Webmin is a more comprehensive Web-based administration utlity which gives you admin control over much more than Samba. I'll try to post more info tomorrow, but right now the steak is coming off the grill, so it's time for me to chow!.

BTW- thanks for following up on this Christian. :)

It's time for dinner for me, so I can't walk you through the process right now. If someone else doesn't follow up on this for you before tomorrow, I'll try to post more info then.

i downloaded the program "Motherboard Monitor", wich is keep saying tht my case is over 65 degress all the time. to high?

That's not high enough to definitely be the problem, but have you opened you computer's case and made sure that all of your fans are still running and that the inside of the case is free of dust?

I downloaded the RAM prog. but didnt udnerstand it so well. It said something about a floppy disc. So i pretty much unistalled it.

What they are saying is that memtest86 runs from a bootable floppy disk. Once you download and unzip memtest86, go to the memtest86 folder and run the "install.bat" file. That will walk you through the process of creating the floppy.

But i only got 256 ddr ram.

The type, size, and number of total RAM sticks doesn't matter- you should still run memtest86.

The other 2 things i dont really understand. So can´t really give u an answer for it.

To boot into Safe Mode, hit the F8 key just as Windows first starts up when you boot. A menu of boot choices will come up; choose the straight "Safe Mode" option from the menu. Windows will then start up using only the most necessary files/progams it needs to run. If your problem is due to a piece of software on your system, there's a good chance that you won't see the problem in safe mode.

In terms of removing PCI cards from your system, …

Could be a DNS issue- can you reach sites if you put their actual IP address in IE's address bar? Try it with Google's IP:

http://64.233.167.99

Also open up a DOS box and type these two commands:

ping www.google.com
ping 64.233.167.99

Let us know the exact results you get.

In terms of Spyware/Adware and the like, did Ad Aware find and fix things? If so, do you remember the names of any of the "nasties"? Some of the spyware programs out there can be very hard to remove entirely, and IE can sometimes get broken in the removal process.

To begin with, your max upload/download speeds are primarily dependent on the specific type of connection package that your ISP gave you, and that can vary between ISPs. Residential DSL is usually ADSL; the "A" standing for Asynchronous. This means that your max upload speed could be capped at a much lower rate than your max download speed. The residential service most common is 768K down/128K up, so if that's the package you have you're doing fine.

More info would really help us:

- When did this start to happen? Had you added/changed any software or settings which might have caused the problem?

- What type of Internet connection are you using? Have you verified that your network card, modem, and any other network devices are all functioning properly and that your TCP/IP settings are correct?

- Have you checked your system thoroughly for viruses and spyware? Those mailicious programs can interfere with or "break" your Internet connectivity.

From the "Trippy but True Hardware Fixes" department:

For any of you out there who've had the wonderful misfortune of having a hard drive go totally belly-up on you, but recovering the data on the drive is absolutely necessary, check this out:

One of my clients' old Maxtor drives finally went South on her this weekend, just as I was in the middle of migrating her data over to her brand new computer. The drive just suddenly died- whir!, click!, spin down, vanished, kaput. I couldn't get it to spin up again on a few subsequent power-cyclings of the machine, and not wanting to damage either of her computers, I took it back to my shop to try to revive it. I put it in three different computers (running Windows and Linux), but it refused to engage in any of them at all; all I got from the drive were a few sick-sounding whines, and one of the controller chips began to get really hot.

I was just about to call her and give her the bad news when I remembered a really off-the-wall fix that I read about ages ago: wrap the drive in an anti-static bag, wrap that in couple of zip-lock baggies, and stick the beast in the freezer overnight. I Googled around a bit and found that this was considered to be a huge "Urban Legend" by many folks, but others said that the fix had indeed worked for them.

WTF I …

Actually, you usually need to upgrade to the OS X version of your OS 9 programs. Since OS X works entirely differently "under the hood" than previous Mac OSes, it's usually not as simple as just downloading an update for your current programs. OS X versions of most of your current programs should be available though; check the company websites, your local computer store, and online software outlets to see what your options (and possible costs) are.

You're welcome- glad you got it sorted out. :)

There are other possible causes aside from temperature issues.

- Does your computer exhibit the problem if you're working while booted into safe mode? If not, you're probably looking at a software issue.

- Does the computer manage to log any possibly helpful error messages before it dies? Review your log files by using the Event Viewer program in your Administrative Tools folder.

- Bad RAM can cause random shutdowms. Download and run memtest86; it will run some pretty intensive tests on your RAM and report on any errors it finds.

- Viruses and "Spyware" can, in extreme instances, cause random shutdowns and/or restarts. Look through the posts in our Security forum for more information on ways you can detect and remove these pests.

- A faulty PCI add-in card could be the culprit. If you have PCI network, sound, modem, etc. cards, removing them one by one can help you narrow down the culprit.

- If heat is the issue, open your case and blow/brush out any dust and debris that might have accumulated; that crud clogs your fans and impedes airflow.

Right then, thanks for the follow-up!

The port you connect to will depend on the protocol you are using to communicate and what service you expect to have listening for a connection on the machine you're connecting to. The official list of port assignments can be found here:

http://www.iana.org/assignments/port-numbers

Just out of curiousity- why do you need to write your own drivers; is this a school project or something like that? The only reason I ask is that Linux drivers are open-source, so you are free to examine the code written by others; you'll get a lot of information just by examining that code.

In terms of network drivers in particular, Donald Becker is the author/maintainer of many of these drivers; visit the site below to see much of his (and other Linux driver developers') work:

http://www.scyld.com/network.html

Personally, I use PuTTY for Windows to connect to all of my Linux boxes. You just open the program, and type in the IP address of the server, and it should go.

As for your second request, there are loads of Samba tutorials out there for your perusal. You don't need samba to use SSH, but if you do a Google search for "samba tutorial", you should find some results that will suit you.

Alex is right- putty is your friend in terms of a good front-end for an ssh connection, but if you're just concerned about accessing shares between Win and Linux boxen on a LAN, Samba is all you need. If you only want the Linux box to connect to shares on the Win boxen you only need to install the "client" component of Samba, but if you also want the Win boxen to be able to access share on the Linux box, you should install the full server package of Samba on the Linux box.

The results of this (rather broad) Google-for-Linux (G4L) search has lots of usefull links:

http://www.google.com/linux?hl=en&lr=&ie=UTF-8&q=samba+windows+tutorial&btnG=Google+Search

Be aware that there are lot of differences between simply using Samba to integrate your Linux box into a Windows workgroup (fairly easy) and using Samba in a Windows AD domain setting (more complex). For the best integration with a Win AD domain you want to make sure that you are using the lastest version of …

Forget my post above !:(

Sorry man, no can do- it gave me such a good giggle that I think l'll be remembering it for a while... :p

delete it from ur registry and reinstall or if your system restore goes back to when u didnt have this problem then do that

More info on that can found in the links returned from this Google search:

http://www.google.com/search?hl=en&ie=UTF-8&q=%22internet+explorer%22+reinstall+registry&btnG=Google+Search

Have you checked your system for Adware/Spyware infections? They can cause the type of problems you describe, and it would be good to determine if they play a part in your problems.

Have a read through the posts in our Security forum for information about how to get and use most-often recommended (and free) program that you can run to detect and remove any malicious pests that might have infested your system. Links to some of the utilities are are also in my sig file below.

*Note that if you do find Spyware/Adware/etc. to be part of the issue, please start a separate thread in the Security forum which details what you've found; we really want to keep "malware"-related questions concentrated in that forum rather than have them spread throughout the other forums.

Give this a try !run it on all users .

EDIT : for gethis if you seen it all ready wrong Variant!!

Erm... WTF cj, havin' a Bad Typing Day or something?

Could you translate that into something that we Earthlings might understand please? :mrgreen:

Have you tried contacting the folks at the site you're trying to upload to? They might have run across the problem before.

Also, do you have any other sites you could use to try to replicate the problem? It would be helpful to know if the problem was specific to one site or not.

Another thought: Is FTP an upload option for you? I've whacked some pretty huge .mpg movies up to sites via FTP and never had them choke.

Maybe it will work if right click on the VBasic ,icon in winxp ,and choose compadiability and choose run in win98 mode

Can't hurt to try it, although there still might be problems with VB stuff that was originally compiled in the Win 98 environment. You might also run into the issues that Alex is talking about.

Well- for starters, not all programs that run under Win 9.x are compatible with XP, period. There's not much you can do in that case except get an XP-compatible version of the program (if it exists).

In terms of something like VB, I'd imaging you would probably run into problems like version mismatches of the runtime libraries and/or other key components. What version of VB do have? Is it supposed to be XP-compatible?

IRQL_NOT_LESS_THAN_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA

Yup, those two errors almost always indicate a memory problem.
Glad you got sorted- marking this thread as "solved"...

It doesn't really make any sense at all to me, even Linux have nice tools to set up LILO, and works pretty well and without much hassles and hurdles.

The difference there is that third-party boot loaders such as lilo and Grub are pretty much independent of the operating systems they can boot. Those bootloaders don't care if they're booting Windows, Linux, BSD, etc., nor do they really care what particular versions of those operating systems you have. Also, the files those bootloaders use don't integrate/conflict with any of the boot programs/files used by Windows.

Your problem may lie with the bootsect.dos file, and you might be able to avoid a full reinstall by recreating that file. Here's the deal: when you use the Win 2k or XP bootloader to boot a previous, non-NT based OS like Win 9.x or ME), the bootloader reads information in the bootsect.dos file for instructions on where to find and how to boot the older OS. I'm not positive about this, but my guess is that because ME was not already installed when you installed XP, the bootsect.dos file that XP created during its installation process doesn't contain any information about the ME install. That might cause XP's loader to fail on ME, because bootsect.dos is the file the boot process jumps to when you choose the ME option in boot.ini.

Again, I'm not sure if rebuilding bootsect.dos will work, but if you want to give it a try you can find …

Its not a a BIOS password he said it is a HDD password...

It never hurts to clarify though- people will often mix up technical terms, and it this case the differentiation is important. :)

Thanks Alex- looks like you're right about that. I wasn't at my multi-boot Win 98/2K Pro/XP Pro system (well OK- it also has three distros of Linux on it as well, but who's counting, right...) when I posted, but I'm looking at my boot.ini on that system now and my entry for Win 98 is:

C:\ = "Windows 98"

so your equivalent entry for ME should work. Just to put this out there though- I did perform my Windows installs in the recommended "oldest to newest" order.

Well, I inserted a page break, rearranged the text that described the visio object (Figure #1), deleted the object from the doc and pasted into a new Visio drawing then moved it back into the document on the blank page.

Good job!

Lo and behold, the document doesn't choke word down when I scroll. Unfortunately, however, the document is owned by the legal departments of two separate corporate entities who most likely won't accept the change to the format.

Oh no- *groan*... :eek:

Oh, well. Sometimes you're the windshield...

Yup- some days you eat the bear, some days the bear eats you. :mrgreen: