camieabz

One thing I have twigged... It is reporting the number of times that Windows prevented the process. Not Norton after all. So if I was on for a while there are more chances of more results on boot up next time. Warm reboots show nothing, because they've not had time to generate an error.

Thanks for the welcome folks... Guess what. Booted up this evening and..."Hi there, I'm that Generic thingy that you hate, and I'm back!" Maybe it's a cold boot issue? Worked fine for 5 warm boots last night. Aw well. Anyone tried threatening their PC yet?

FTP Commander here. Does the job.

Hallo folks. I googled for Generic Host etc etc. You know the issue by now. Right. I checked out most of the possible trojans / viri via updates, fixes and regedit values. Clean! I ran the Windows hotfix mentioned earlier. No difference! I disabled the SSDP service (recommended in another link). No difference. I tried the unticking of the bi-directional support, and ding ding! Seems to have stopped for now. I too have a new XP PRo setup with XP2. In fact it's a brand new self-build. The one thing that I left until last was the installation of the HP Officejet 7310 All-In -One. Initially this problem did not occur, but after a while Norton IS 2005 flagged this and stopped the communication. I had two other programs which would try to install on startup (occuring at the same time as this problem). One was trying to install my integrated printer fax machine capability (not currently an option for me, due to phone line reasons), and the other was trying to install..."photo gallery". I kept pressing cancel to stop them at boot up. Looking in my startup folder I found two shortcuts:- HP Image Zone Fast Start - Deleting this disabled the photo gallery one. HP Digital Imaging Monitor - and bang went the other! Now I have no reason to belive that either had a direct influence over the Generic Host issue, but there's three issues and it would seem that all are or were caused by HP device software. When I first set it up, I had lots of problems getting an ethernet connection on the printer (wanted one for remote printing). Seems that the rinter has a default IP, and on installation you're given the option to change the IP. I changed mine to be one number up from the new PC on the internal network. This wouldn't work. However, on changing the install to default IP it worked fine??? (Default IP is 169.254 with a class B mask, and my network was class C public). Food for thought. I went HP because they gave a decent piece of kit for the buck (print, scan, fax, copy, duplex attachment.) My Dad has a similar three year old model and I had one hard time ironing out several conflicts between HP software and varios other pieces of kit. Not knocking HP, but for the price and 700MB of software, you would expect seamless functionality. It seems that the ethernet connection can cause quite a lot of hassle. There's my tuppence. Hope it helps or gives ideas. Camie.