Please Wait message on XP start up

Hi all ... 'fraid I'm back! Many thanx again to you all for the help - unfortunately, though, I still have the same problems inasmuch that I still get 'the beeps' (8 short ones on restart, only resolved by turning off at the wall socket and leaving for five minutes or so - it starts again if I turn it on earlier than that) and I still get the 'Please Wait' message with around two lines of white dots!
Having just had another look at the Event Viewer, the only error message still showing up now is the DHCP one as follows:-

Event Type: Error
Event Source: Dhcp
Event Category: None
Event ID: 1002
Date: 13/08/2008
Time: 18:40:47
User: N/A
Computer: HOME
Description:
The IP address lease 192.168.1.2 for the Network Card with network address 0030BD71EABD has been denied by the DHCP server 0.0.0.0 (The DHCP Server sent a DHCPNACK message).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

... but I don't know if that's what's causing the problem. Sorry Bobbye, I deleted the Foxit and Photo Gallery as suggested but, with regards the DHCP, I cottoned on to where to read up about it but couldn't seem to get to what to do about it!

'DHCP server 0.0.0.0'

http://technet.microsoft.com/en-us/library/cc757164.aspx#BKMK_1

"The DHCP client does not have an IP address configured or indicates that its IP address is 0.0.0.0.
Cause: The client was not able to contact a DHCP server and obtain an IP address lease, either because of a network hardware failure or because the DHCP server is unavailable.

Solution: Verify that the client computer has a valid functioning network connection. First, check that related client hardware (cables and network adapters) are working properly at the client using basic network and hardware troubleshooting steps.

If the client hardware appears to be prepared and functioning properly, check that the DHCP server is available on the network by pinging it from another computer on the same network as the affected DHCP client."

Thanks CCT. Everything appears plugged in and working but tried pinging my IP address and timed out on all four attempts - also pinged localhost with no failures. Sure you know more about all this than I do?

My last advice: copy the following into Notepad and save as Flush.bat then click on it to activate it.

echo off

cd\

ipconfig /release

ipconfig /flushdns

ipconfig /registerdns

ipconfig /renew

netsh winsock reset catalog

netsh int ip reset reset.log

netsh winsock reset

cmd /k

pause


edit: well, you could try this too: Start, Control Panel, Network Connections, right click on the connection, click Properties, Properies again and make sure both bopxes are set for automatic. Then click advanced abd make sure 'DHCP enabled' appears under IP address and that 'automatic metric' is checked.

@echo off

By the way

Lousy cut and paster - good Googler!


LOL

Well, thanks again for all your help fellas - unfortunately none of this has worked, so, taking your point about this being your 'last advice', I guess it's now time to get someone in to sit in front of the machine. As I say, I'm very grateful you even tried though ... much appreciated.

a couple of thoughts for emcee47

Hi,

Just found your posts & thought I'd have a go, if you're still in need.

You're running Windoze XP Home, my commiserations.

Your I.P Address seems to be set as 192.168.1.2, is this a manual configuration or assigned by DHCP; if the latter, what is your DHCP server, a classic server or a broadband AP/modem/router? It's worth checking that your DHCP server is actually set to assign IPs and that your Ethernet connection is set to receive them.

Open Control Panel > Network Connections, right click on your LAN connection & choose 'Properties'. Scroll down the list and double click 'Internet Protocol (TCP/IP)', ensure that 'Obtain an IP Address automatically' is selected, you can assign an alternate manual configuration at this point by choosing the appropriate tab. If you choose to do this, select 'User configuration' and assign an IP (would suggest that you use 192.168.1.2, as I assume your server is 192.168.1.1), assign this as the Default Gateway and the Subnet Mask should automatically be completed with 255.255.255.0. This procedure should (hopefully) allow your Ethernet connection to either be assigned an IP by DHCP or to choose its own which will allow successful Pings and access to any permitted network.

To set up your DHCP server refer to the documentation that came with any modem/router or Access Point or post the model specs & I'll see what I can find. Also, for Server 2003, 2008, SBS or Apache, supply the details & I'll try & sort a walkthrough for DHCP assignment. In the event you're running both a modem/router/AP AND a classic server, ensure they're not BOTH set to assign IPs by DHCP as this can cause interesting problems.

Your beep issues are probably either faulty RAM or a graphics issue. It's worth testing your RAM with Memtest 86 (you'll need to Google it as I'm not yet permitted to post a link), unzip, burn the ISO to disc & then either use the boot menu (usually F12) or reconfigure the BIOS to boot from CD/DVD; use a floppy instead, if you have one. The software will run automatically and stress test your RAM, you may not completely follow the results but a pass or fail is obvious.

Seem to have run out of space, will address the graphics issue shortly.

Excellent post anoddball :grinthumb although the last reply was 11 days ago ! (and therefore possibly resolved now)
At least anyone viewing this thread in future may be helpend by it though.

No guys - in actual fact, the problem is still as it was before - but, although the beeps are still present, they are restricting themselves to one in every three restarts now! The 'please wait' hasn't changed. Am very grateful though for this most recent post. Have noticed you're a 'newey' like myself oddball ... but that seems to be where the similarity ends! I'm certainly a dummy in this field whereas you sure seem to know what you're talking about - so will get a translator in and start ploughing through your post! Either way, much obliged to you and will let you know the result ....

Right ... (have had a little bit of help at home to try and interpret this!) :
Have processed your second paragraph and configured it as suggested.
For para.3, I have copied this:-

Models:

Router - Netgear WGR614 v6
Cable Modem - (VirginMedia) NTL250 (Model Number - 0E08C007)

Notes: Router is setup to assign by DHCP and so is LAN.

I have consigned para.4 to be my next step!

FAO emcee47

Have been wrestling with Windoze since 3.1 and the one thing I know to be constant: you will never know it all.

If you can log into your router the problem becomes more interesting. Try to ping 127.0.0.1 as this will test your Ethernet card through the default loopback settings. Four replies means at least something is working. If you disable (right click the icon in Network Connections > 'Disable') or remove any second Ethernet card (not the onboard one); or have another machine, perhaps a wirelessly connected laptop, try to ping by computer name (I assume 'Home', from a previous post). This will show an address, if it is NOT within the range 192.168.1.x, then there is a clash between DHCP assignments.

You could try a hard reset of the router (a small inset button near the aerial, you may need to unfold a paperclip). Then log into it through your browser and reconfigure your internet access and DHCP settings, ensure that the range you set for assignment is all within the same subnet - if your router is 192.168.1.1, ensure the range is 192.168.1.x, would suggest you use 192.168.1.9 - 192.168.1.254 as this leaves 192.168.1.2 - 8 free for manual assignment if necessary.

If you can log into the router before a hard reset, check the DHCP assignment settings or, turn off DHCP and manually assign an IP address to your Ethernet card, again ensuring it falls within the correct range, as above.

Your default router login details: type '.routerlogin.net' after the usual first 10 characters of a URL in your address bar; the Username is: admin, Password: password (would suggest you change these).

Let me know the results and will see what else we can try.

With regard to the beeps and the long pause at boot, if your RAM passes the test, it's probably a graphics issue, I believe your monitor is connected to your nVidea GeForce2 MX card? The horizontal blue 15 pin connection on the back of your rig? If memory serves, this is an AGP card, it's worth checking the BIOS settings are set to use this card before the onboard VGA. You could remove the card from your motherboard and connect to the onboard VGA, see if that makes a difference. Before you try this, visit Gigabyte's website, find and install the latest onboard VGA drivers for your board. If you need, can provide brief instructions for safe removal of the card.

Let me know how it goes, eventually we'll crack it & you'll have learned something new.

Meant to say, "Thanks kimsland", I've had untold help from various forums over the years & I try to give back when I can: what goes around...

A further thought or two for emcee47: if you have 2 NICs, ensure they're not both set to use the same subnet - if one is assigned an address in the range 192.168.1.x, the other must be assigned a different address range such as 192.168.0.x or 192.168.2.x. Also, check that your router is actually assigned an IP of its own; if not, give it 192.168.1.1 for the sake of simplicity.

If you need translations or an expanded 'how to', just post the request. Kinda wanna see how this resolves - it all adds to the knowledge base.

Reading through your router manual now so I'll be able to construct any walkthroughs for DHCP or IP assignment, if you need them.

!!!!
Sorry fellas - gotta come completely clean and say I haven't got a clue what you're talking about here or how to go about checking any of this! I know I said I was a dummy from the offset but I don't think any of us (including me) realised how much of a dummy 'til now. I feel embarrassed for wasting your time through sheer ignorance - but if any of you would be kind enough to point me in the direction of anyone or any site who could be patient enough to speak a language I understand, I'd be very grateful! (... and I mean a 'step-by-step' guide to what they suggest I do and where they want me to look for it).

OK - one component at least on your comp is in trouble - I would bet on video card ram problems but that's a guess.

Since you are NOT a Geek BUT are an aspiring geek I suggest you seek hands-on help that will help you learn.

Is there a way to check locally for a computer club or Library Club that works on comps etc?

Great way to meet people that like the technology AND you get help.

OR, just take it to a shop and say 'FIX THIS!'. (which I have done with internal combustion engines but Never a comp).

Apologies emcee47

Sorry mate, sometimes get carried away; let's see if I can break this down a bit.

In my last post, when I say "if you have 2 NICs", that's Network Interface Cards, the card your broadband router is plugged into. Your post on page 1 shows you have a 'Network Adapter TE100-PCBUSR 32-Bit Cardbus PC Card' which, if memory serves, is a PCMCIA card and should be easy to remove by pressing the button next to it. If your router is connected to this card, disconnect it and plug it into the other Ethernet socket (near the USB ports). Click Start > Control Panel > Network Connections and right click on the LAN connection, you should only have 1 now. Choose properties and configure the settings as detailed in my first post. This should set your card to send and receive.

Then click Start > Run and type "cmd" (without the quotes), press return. When the command prompt appears, type "ping 192.168.1.1" (again, without the quotation marks). If you receive 'Request timed out' responses four times let me know; if not, open Firefox (or your browser of choice) and type "192.168.1.1" (again, without the quote marks) in the address bar & press return. You should be asked for a username and password which are: "admin" and "password" respectively (again, without...).

Let me know how you get on up to this point and then I'll walk through the next few steps.

Tend to agree with CCT about the graphics RAM issue, if your system RAM passed Memtest86 then it is worth considering the removal of the card; post if you want a walkthrough.

Have had a complete novice read this through and he reports it's not entirely incomprehensible.