falcon051997
asked on
Very long boot up time (upto 3 minutes)
For over a month or so, I have been experiencing this strage problem My Pc appears to be taking for ever to boot up. Almost 3 or so minutes. It was not like this before.
1. I have recently installed network card and connected my PC with another one at home. However, the other PC is working normally.
2. I have a PIII 450 homebuilt system win 98 second edition operating system. I have Mc Cafee virus scan and Norton System works 2 both in the background. However, even without these programs the computer is taking the same long boot up time, so I have to rule out these being culprits.
3. I also noticed that during the boot up.. it spends max. time when windows 98 standard logo appears. Then i get the log on to network message, which comes in 640x480 resolution with 16 colors mode. THis is indeed strange. Here I usually click "OK" since I have not set up any password etc. after that the system in a few secs switches over to the usual 1028X764 resolution with 32 bit true color mode. This started happening only like during the last three or 4 days.. I dont understand this. I have a MGA millinium vedeo card.
I know the question is long and it has several parts to answer. I am willing to spend 500 points for any suggestions leading to the clean up of my system and restoring to what it used to be like. Thanks in advance. Falcon
1. I have recently installed network card and connected my PC with another one at home. However, the other PC is working normally.
2. I have a PIII 450 homebuilt system win 98 second edition operating system. I have Mc Cafee virus scan and Norton System works 2 both in the background. However, even without these programs the computer is taking the same long boot up time, so I have to rule out these being culprits.
3. I also noticed that during the boot up.. it spends max. time when windows 98 standard logo appears. Then i get the log on to network message, which comes in 640x480 resolution with 16 colors mode. THis is indeed strange. Here I usually click "OK" since I have not set up any password etc. after that the system in a few secs switches over to the usual 1028X764 resolution with 32 bit true color mode. This started happening only like during the last three or 4 days.. I dont understand this. I have a MGA millinium vedeo card.
I know the question is long and it has several parts to answer. I am willing to spend 500 points for any suggestions leading to the clean up of my system and restoring to what it used to be like. Thanks in advance. Falcon
Virus scanners
--
Each time you start windows, each virus scanner attemps (and of course succeeds) in starting a program called a virus shield (or Vshield). It's important to run it as soon as possible, because a lot of files are accessed during boot.
So 1: 2 scanners will make your pc longer to boot.
Network adaptor
--
This is what causes your computer to boot so slow. It also causes your pc to wait so long before logo appears and your hard disk won't do anything at that time. If you look at the back of your pc, you will see that the LED of your network adaptor (=NIC) is blinking. Your network is scanning the net for other NICs. What causes it to examine the network so long is probably a wrong network setting on that pc.
What you should do
--
First of all, you might want to check the settings of your network. If necessary reinstall it.
Second: check your physical network. Are connectors plugged in right? Isn't your cable broken (especially check this if you use coax)?
Third: You don't really need two virusscanners, but I don't say you shouldn't use two either. It will make your bootup slower (actually it will make everything slower), but you'll get some extra security. This is your choice.
Fourth: How many programs are run at startup? All those that aren't necessary, kill the from startup.
3408
Any questions? Ask!
--
Each time you start windows, each virus scanner attemps (and of course succeeds) in starting a program called a virus shield (or Vshield). It's important to run it as soon as possible, because a lot of files are accessed during boot.
So 1: 2 scanners will make your pc longer to boot.
Network adaptor
--
This is what causes your computer to boot so slow. It also causes your pc to wait so long before logo appears and your hard disk won't do anything at that time. If you look at the back of your pc, you will see that the LED of your network adaptor (=NIC) is blinking. Your network is scanning the net for other NICs. What causes it to examine the network so long is probably a wrong network setting on that pc.
What you should do
--
First of all, you might want to check the settings of your network. If necessary reinstall it.
Second: check your physical network. Are connectors plugged in right? Isn't your cable broken (especially check this if you use coax)?
Third: You don't really need two virusscanners, but I don't say you shouldn't use two either. It will make your bootup slower (actually it will make everything slower), but you'll get some extra security. This is your choice.
Fourth: How many programs are run at startup? All those that aren't necessary, kill the from startup.
3408
Any questions? Ask!
Falcon,
Prolong boot-up as I perceived is the computer in trying to search for networking server either LAN or VPN (virtual private networking server) etc.
Since you have not entering any password for a proper setup and logon window as a client of Microsoft network, your system is logging into the local machine without the active desktop setting in 640x480 resolution with 16 colours mode. Then it log on the current user normal desktop with active desktop enabled that you have configured resolution to be 1028X764 resolution with 32-bit true colour mode.
I would suggest: -
Go to the control panel, network icon. At the Configuration Tab, make certain Client for Microsoft Networks component is installed. Remove the adapter and protocol for VPN (Virtual Private Networking).
At the Primary Network Logon: select the [Client for Microsoft Networks ].
At the Identification Tab, entering a computer name and a workgroup name. Computer name is unique for your computer to identify in the LAN. Workgroup name should be all the same in the LAN.
Exit the control panel. Restart the computer. When asked to log on window as Client for Microsoft Networks, the computer name is showing and you have to put in a password and press [OK].
After booting into the window, go to Start-Settings-Active Desktop, de-select the “view as active desktop”.
Go to start-Log Off current name, log off current user to the local machine.
It should look like: “Start-Log Off…”.
Go to the control panel and change the resolution to 800X600 resolution with 16-bit high colour.
Go to shut down the computer.
Next time, start it from cold and inspect the booting time. Any improvement.
Pslh
Prolong boot-up as I perceived is the computer in trying to search for networking server either LAN or VPN (virtual private networking server) etc.
Since you have not entering any password for a proper setup and logon window as a client of Microsoft network, your system is logging into the local machine without the active desktop setting in 640x480 resolution with 16 colours mode. Then it log on the current user normal desktop with active desktop enabled that you have configured resolution to be 1028X764 resolution with 32-bit true colour mode.
I would suggest: -
Go to the control panel, network icon. At the Configuration Tab, make certain Client for Microsoft Networks component is installed. Remove the adapter and protocol for VPN (Virtual Private Networking).
At the Primary Network Logon: select the [Client for Microsoft Networks ].
At the Identification Tab, entering a computer name and a workgroup name. Computer name is unique for your computer to identify in the LAN. Workgroup name should be all the same in the LAN.
Exit the control panel. Restart the computer. When asked to log on window as Client for Microsoft Networks, the computer name is showing and you have to put in a password and press [OK].
After booting into the window, go to Start-Settings-Active Desktop, de-select the “view as active desktop”.
Go to start-Log Off current name, log off current user to the local machine.
It should look like: “Start-Log Off…”.
Go to the control panel and change the resolution to 800X600 resolution with 16-bit high colour.
Go to shut down the computer.
Next time, start it from cold and inspect the booting time. Any improvement.
Pslh
ASKER
comments:
As I mentioned in my question, I dont think either Norton or mc cafee are the culprits. Because even without those two I have the same problem.
I dont have both set up for virus scans. Only Mc.Cafee scans for viruses and Norton is only for other utilities. But once again, i dont think either of them are the problems.
I like the suggestion regarding Network. I think it has fouled up something because the installation may not have gone thru well. I need to check the details based upon PSLH's suggestions.
I will be back after doing some checking etc. and post here as comment as to what has happened.
Thanks again.
Falcon
As I mentioned in my question, I dont think either Norton or mc cafee are the culprits. Because even without those two I have the same problem.
I dont have both set up for virus scans. Only Mc.Cafee scans for viruses and Norton is only for other utilities. But once again, i dont think either of them are the problems.
I like the suggestion regarding Network. I think it has fouled up something because the installation may not have gone thru well. I need to check the details based upon PSLH's suggestions.
I will be back after doing some checking etc. and post here as comment as to what has happened.
Thanks again.
Falcon
A lot of valuable input and things for you to check so don't want to add to your workload until results are known. Do, though, want to agree very much with the slow boot process as it regards the network setup AND running these background programs. We use both as well, but not loading at boot unless we've taken actions that MAY introduce virus activity -- personal choice, of course or plan to go online, then invoke 'as needed'. Again, personal choice.
Re. McAfee,Norton running ... a lot depends on how you've got your environment setup, imagine if you have large files and your setup scans ALL FILES, including Compressed files and scans at boot ... regardless of processor speed, this is time intensive. It has to impact your boot time.
Re. McAfee,Norton running ... a lot depends on how you've got your environment setup, imagine if you have large files and your setup scans ALL FILES, including Compressed files and scans at boot ... regardless of processor speed, this is time intensive. It has to impact your boot time.
first you have to figure out what it is doing you can do this a few ways
look at win.ini and see it has c:anything
try autoexec.bat
and config.sys
these are hidden files
and check what programs run on startup
the way to do this is with in windows run msconfig
hope this helps
as always
Mr. Happy
look at win.ini and see it has c:anything
try autoexec.bat
and config.sys
these are hidden files
and check what programs run on startup
the way to do this is with in windows run msconfig
hope this helps
as always
Mr. Happy
If the problem started after installing the NIC then that's most likely the culprit. Another suggestion is to only use what you need in the network properties... additional protocols and services take more overhead.
You may want to also check which IRQ the network card is using (r.click computer in device manager. A shared IRQ for a NIC, depending on the shared device, can create a substantial lag in boot times, and network access times. You can change the IRQ settings either in BIOS or in safe mode by overriding the automatic settings.
at the win98 logo screen, hit the escape key.
the screen behind there will tell you whats hanging the boot up.
kj
the screen behind there will tell you whats hanging the boot up.
kj
ASKER
comment to pslh: and to others as well.
I have eliminated the possibility of Norton or McCafee slowing me down. I removed them from auto startup and tried to boot up. After the bios initialization etc... there come windows 98 screen and stay there exactly 2 min. and 15 sec.. every single time, Norton/Mcafee or not.. it does not matter.. Ater that the log on screen appears. Now the 640 X 480 resolution problem is solved following "pslh"'s suggestions..
However, my long boot is still unsolved.
I checked my network and here are the various things I noticed in the window
1. Client for Microsoft Networks
2. Dial Up Adapter
3. Linksys LNE PCI II PCI Ethernet Adapter
4. IPX/SPX - Compatible Protocol -> Dial Up Adapter
5. IPX/SPX - Compatible Protocol -> Lynksys LNE PCI II PCI Ethernet Adapter
6. TCP/IP -> Dial UP Adapter
7. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
8. File and printer Sharing for Microsoft Networks.
So if any of the above causing problems please let me know.
But I dont think either Norton or McCafee is the problem anymore.
The resolution problem is successfully solved by "PSLH"'s suggestion.
comment for Kind4ME... sorry I checked autoexec.bat config.sys etc.. for any extraneous stuff.. they have mccafee virus scan stuff initialization.. nothing else. Also McCafee is only set to check the program files. and Often i noticed the virus shield only starts after "loggin on to Network" .. not before.. and the delay is mostly before loggin on.. not after.
comment asteac: I am not sure whether Mccafee scans before logging on.. However, I shall double check to see what files it is scanning. However, Like I said before, I diabled mc Cafee using a "start up manager" utility program.. which lets me disable any TSR completely.
Falcon
I have eliminated the possibility of Norton or McCafee slowing me down. I removed them from auto startup and tried to boot up. After the bios initialization etc... there come windows 98 screen and stay there exactly 2 min. and 15 sec.. every single time, Norton/Mcafee or not.. it does not matter.. Ater that the log on screen appears. Now the 640 X 480 resolution problem is solved following "pslh"'s suggestions..
However, my long boot is still unsolved.
I checked my network and here are the various things I noticed in the window
1. Client for Microsoft Networks
2. Dial Up Adapter
3. Linksys LNE PCI II PCI Ethernet Adapter
4. IPX/SPX - Compatible Protocol -> Dial Up Adapter
5. IPX/SPX - Compatible Protocol -> Lynksys LNE PCI II PCI Ethernet Adapter
6. TCP/IP -> Dial UP Adapter
7. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
8. File and printer Sharing for Microsoft Networks.
So if any of the above causing problems please let me know.
But I dont think either Norton or McCafee is the problem anymore.
The resolution problem is successfully solved by "PSLH"'s suggestion.
comment for Kind4ME... sorry I checked autoexec.bat config.sys etc.. for any extraneous stuff.. they have mccafee virus scan stuff initialization.. nothing else. Also McCafee is only set to check the program files. and Often i noticed the virus shield only starts after "loggin on to Network" .. not before.. and the delay is mostly before loggin on.. not after.
comment asteac: I am not sure whether Mccafee scans before logging on.. However, I shall double check to see what files it is scanning. However, Like I said before, I diabled mc Cafee using a "start up manager" utility program.. which lets me disable any TSR completely.
Falcon
well you definitely don't need IPX/SPX on the dial-up adapter so that can be deleted. depending on which protocol you are using on your network... either IPX/SPX or TCP/IP could possible be removed from your NIC. If you're using TCP/IP on your network then do you have a TCP/IP address set? If not then this could be your problem... it's looking for a DHCP server to assign an address. Unless you are comfortable with TCP/IP addresses... i'd suggest you use IPX/SPX on the NIC and leave TCP/IP on the dialup adapter.
Falcon, Glad that the resolution problem solved.
For the boot up time, go to the CMOS/BIOS, checking the hard disks at the first page.
If it is now set as “AUTO”, try to write down all data and set it to be user-defined with the exact data detected for your hard disk. This will help in suppressing the detection for your hard disk every time during boot up.
Try to remove following protocols.
IPX/SPX - Compatible Protocol -> Dial Up Adapter
IPX/SPX - Compatible Protocol -> Lynksys LNE PCI II PCI Ethernet Adapter
Go to Start-programs-accessories
Go to the control panel, Add/remove program, window set up, un-install the VPN virtual networking and ISDN. Restart the computer.
See if any help. Pslh
For the boot up time, go to the CMOS/BIOS, checking the hard disks at the first page.
If it is now set as “AUTO”, try to write down all data and set it to be user-defined with the exact data detected for your hard disk. This will help in suppressing the detection for your hard disk every time during boot up.
Try to remove following protocols.
IPX/SPX - Compatible Protocol -> Dial Up Adapter
IPX/SPX - Compatible Protocol -> Lynksys LNE PCI II PCI Ethernet Adapter
Go to Start-programs-accessories
Go to the control panel, Add/remove program, window set up, un-install the VPN virtual networking and ISDN. Restart the computer.
See if any help. Pslh
ASKER
comment majus: I would like to try your suggestion. I am not very well versed with these different protocol terminologies.. I used to only have dial up adapter with Tcp/ip in past and my ISP provider used to give the address.
After I added Network card etc.. when I ran the disk that came with it, it include all these extra ones and i am not sure which ones i really need. And I am pretty sure i am not setting any TCP/IP adress.. if I do I dont know how to check for it.
Could you be a bit more specific and tell me exactly which ones I need to remove (please use the numbers I gave, then it would be easy for me to understand). Thanks.
Falcon
After I added Network card etc.. when I ran the disk that came with it, it include all these extra ones and i am not sure which ones i really need. And I am pretty sure i am not setting any TCP/IP adress.. if I do I dont know how to check for it.
Could you be a bit more specific and tell me exactly which ones I need to remove (please use the numbers I gave, then it would be easy for me to understand). Thanks.
Falcon
ASKER
comment pslh:
Regarding your suggestion with Bios, it only take like a few secs and quickly goes to windows 98 screen. Than part has always been like that. pretty fast and I dont think is the reason for hang up.
I checked for ISDN as per suggestion. I dont think there is anything like that. I only see "DIal up Networking", "DIrent Cable", "Hyper Terminal", and " Phone Dialer".
I will now check removing Ipx stuff from Network config and see if that improves the situation.
Thanks again
Regarding your suggestion with Bios, it only take like a few secs and quickly goes to windows 98 screen. Than part has always been like that. pretty fast and I dont think is the reason for hang up.
I checked for ISDN as per suggestion. I dont think there is anything like that. I only see "DIal up Networking", "DIrent Cable", "Hyper Terminal", and " Phone Dialer".
I will now check removing Ipx stuff from Network config and see if that improves the situation.
Thanks again
1. Client for Microsoft Networks
2. Dial Up Adapter
3. Linksys LNE PCI II PCI Ethernet Adapter
4. IPX/SPX - Compatible Protocol -> Dial Up Adapter
5. IPX/SPX - Compatible Protocol -> Lynksys LNE PCI II PCI Ethernet Adapter
6. TCP/IP -> Dial UP Adapter
7. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
8. File and printer Sharing for Microsoft Networks.
OK. #4 is definitely out of there...
this will leave your dial-up adapter only using TCP/IP, which is all it needs.
OK. You have both IPX/SPX and TCP/IP bound to your ethernet adapter. For simplicity sake, I'd suggest removing #7, the TCP/IP bound to the ethernet. Keep in mind that you need IPX/SPX loaded on your other computer and bound to its' ethernet card, or your network won't work.... chances are this is what it's using anyway.
If you'd rather use the TCP/IP protocol instead then you need to set an address. If you double-click on #7 you'll see where to put the address. You can use the private addresses... like 192.168.X.X. If you choose this route then you need to set a similar address on the other machine. For example: setup TCP/IP on one NIC using 192.168.1.1 as an IP address and 255.255.255.0 as a subnet mask... then on your other computer setup TCP/IP for its' NIC to use 192.168.1.2 and 255.255.255.0 as the subnet mask. Using this plan... you don't need any IPX/SPX
2. Dial Up Adapter
3. Linksys LNE PCI II PCI Ethernet Adapter
4. IPX/SPX - Compatible Protocol -> Dial Up Adapter
5. IPX/SPX - Compatible Protocol -> Lynksys LNE PCI II PCI Ethernet Adapter
6. TCP/IP -> Dial UP Adapter
7. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
8. File and printer Sharing for Microsoft Networks.
OK. #4 is definitely out of there...
this will leave your dial-up adapter only using TCP/IP, which is all it needs.
OK. You have both IPX/SPX and TCP/IP bound to your ethernet adapter. For simplicity sake, I'd suggest removing #7, the TCP/IP bound to the ethernet. Keep in mind that you need IPX/SPX loaded on your other computer and bound to its' ethernet card, or your network won't work.... chances are this is what it's using anyway.
If you'd rather use the TCP/IP protocol instead then you need to set an address. If you double-click on #7 you'll see where to put the address. You can use the private addresses... like 192.168.X.X. If you choose this route then you need to set a similar address on the other machine. For example: setup TCP/IP on one NIC using 192.168.1.1 as an IP address and 255.255.255.0 as a subnet mask... then on your other computer setup TCP/IP for its' NIC to use 192.168.1.2 and 255.255.255.0 as the subnet mask. Using this plan... you don't need any IPX/SPX
ASKER
comment to majus:
I just follwed Pslh's suggestion.. as well as yours and removed both 4 and 5.
Then i restarted and measured my times. Absolutely no change in boot up time. exactly 2 min and 15 sec during the windows 98 screen.
Now can I remove 7 also.. since I checked that one and there is no address there... so may be it is searching for one.. Ii donno..
falcon
I just follwed Pslh's suggestion.. as well as yours and removed both 4 and 5.
Then i restarted and measured my times. Absolutely no change in boot up time. exactly 2 min and 15 sec during the windows 98 screen.
Now can I remove 7 also.. since I checked that one and there is no address there... so may be it is searching for one.. Ii donno..
falcon
ASKER
comment to BigOrange:
I checked the IRP for NIC it is 9. ALso one of the sound devices "yamaha onboard sound" has the same IRQ too..Both are functioning normally.. no yellow marks on them nor any warnings. SO I am not sure.
Falcon
I checked the IRP for NIC it is 9. ALso one of the sound devices "yamaha onboard sound" has the same IRQ too..Both are functioning normally.. no yellow marks on them nor any warnings. SO I am not sure.
Falcon
ok... in the network properties click add, then click protocol, then click Microsoft, then click IPX/SPX, then click ok. You'll probably have the remove the IPX/SPX on the dialup adapter again after this. Then delete #7.
Or you could configure #7 like in my example above... you may want to go ahead and configure the TCP/IP bound to the ethernet in your other computer also.
If you delete all protocols bound to your ethernet adapter then your ethernet adapter will also be removed. So leave at least one protocol bound to the ethernet adapter.
Or you could configure #7 like in my example above... you may want to go ahead and configure the TCP/IP bound to the ethernet in your other computer also.
If you delete all protocols bound to your ethernet adapter then your ethernet adapter will also be removed. So leave at least one protocol bound to the ethernet adapter.
falcon,
You can remove (6) and (7), restart the computer.
Start your computer to command mode, at the c:\prompt, type “scandisk ” without the quotation and press enter.
During scandisk, do scan the disk surface too.
At the c:\prompt, type “scanreg /fix ” without the quotation and press enter. Follow the instruction.
After that, restart the computer to safe mode.
Go to Start-run, type “sfc” without the quotation in the open box and OK.
Click the settings button, checked the boxes for: -
[x] Check for changed files
[x] Check for deleted files.
Click Apply and OK.
Then start to run [x] Scan for altered files. Take note on the version and date. You may need to update the detected files instead of restoring old ones.
Finished.
Restart the computer to normal mode and shutdown the computer via Shutdown-shutdown.
Checking the boot up time.
If it is shortened, try to reinstall the (6) and (7).
But no need to add any IP address for (7).
Select (7) and click [properties].
At the IP address Tab, set it to be [x] Obtain an IP address automatically.
At the WINS Configuration Tab, checked the radio button of [x] Disable WINS Resolution.
The button [ ] Use DHCP for WINS Resolution will be unselected.
Click OK.
Restart the computer and checking the boot up time again.
Pslh
You can remove (6) and (7), restart the computer.
Start your computer to command mode, at the c:\prompt, type “scandisk ” without the quotation and press enter.
During scandisk, do scan the disk surface too.
At the c:\prompt, type “scanreg /fix ” without the quotation and press enter. Follow the instruction.
After that, restart the computer to safe mode.
Go to Start-run, type “sfc” without the quotation in the open box and OK.
Click the settings button, checked the boxes for: -
[x] Check for changed files
[x] Check for deleted files.
Click Apply and OK.
Then start to run [x] Scan for altered files. Take note on the version and date. You may need to update the detected files instead of restoring old ones.
Finished.
Restart the computer to normal mode and shutdown the computer via Shutdown-shutdown.
Checking the boot up time.
If it is shortened, try to reinstall the (6) and (7).
But no need to add any IP address for (7).
Select (7) and click [properties].
At the IP address Tab, set it to be [x] Obtain an IP address automatically.
At the WINS Configuration Tab, checked the radio button of [x] Disable WINS Resolution.
The button [ ] Use DHCP for WINS Resolution will be unselected.
Click OK.
Restart the computer and checking the boot up time again.
Pslh
Pslh, how does it obtain an IP address automatically if there is nothing to assign an IP address on his network?
Pslh, how does it obtain an IP address automatically if there is nothing to assign an IP address on his network?
majus, Win98 has the ability to get IP address automatically in random order. This is the unique feature of Win98. This will facilitate general users for networking if their LAN does not linked to a specific server with specific dormain and IP address.
falcon's LAN is a simple one <<1. I have recently installed network card and connected my PC with another one at home.>>
Pslh
falcon's LAN is a simple one <<1. I have recently installed network card and connected my PC with another one at home.>>
Pslh
the antivirus is scanning ur disk when ur booting it....
try to remove the norton start up scan from the autoexec.bat by typing the [rem] command at the bigging of the line for start up scan (norton)
save it n reboot your computer.
if there something wrong with it just remove the [rem] from the line n reboot again.
i have this will solve your problem
try to remove the norton start up scan from the autoexec.bat by typing the [rem] command at the bigging of the line for start up scan (norton)
save it n reboot your computer.
if there something wrong with it just remove the [rem] from the line n reboot again.
i have this will solve your problem
This may help in regards to troubleshooting video problems and the Win98 Splash Screen....
http://support.microsoft.com/support/kb/articles/Q127/1/39.asp
http://support.microsoft.com/support/kb/articles/Q127/1/39.asp
External Scsi device? If so, this may apply, at handing up on startup logo.
http://support.microsoft.com/support/kb/articles/Q193/2/42.ASP
----
I'd try disabling the LOGO screen problems/bypassing as well. More follows.
----
This was the reference I mentioned about the other impacts of viruscan software as it regards and hangs up the Windows logon logo screen ....
http://support.microsoft.com/support/kb/ARTICLES/Q150/5/16.asp
Synopsis: When you start Windows, your computer may stop responding (hang) after the Windows logo screen is displayed.
NOTE: Windows 95 may start properly if you press the F8 key when you see the "Starting Windows 95" message, choose Step-By-Step Confirmation from the Startup menu, and then press Y at each prompt. In Windows 98, press and hold CTRL.
CAUSE
This problem may be caused by either of the following situations:
An anti-virus program warning screen may be hidden behind the Windows logo screen. This problem occurs if Windows is loading an anti- virus program from the Autoexec.bat file to automatically check for a virus. The anti-virus program detects that the Command.com file has changed as a result of the Windows installation and pauses the system to inform you and receive further instructions.
The display adapter installed in your computer is not properly handling the video mode switching that occurs when the Windows logo screen is displayed. This video mode switching does not occur when you choose Step-By-Step Confirmation from the Startup menu, because the Windows logo screen is not displayed.
This problem is known to occur with the following display adapters:
ATI Graphics Ultra Pro (Mach32)
RESOLUTION
To determine whether anti-virus software is running, press the ESC key to close the Windows logo screen. If anti-virus software is running, you may be able to access it from this screen. Choose the option that allows the program to update any affected files. This prevents the pause from occurring when you start Windows in the future.
If no anti-virus software is running, use one of the following options to determine whether disabling the logo screen will resolve the problem:
Add the following line to the [Options] section of the Msdos.sys file in the root folder of the physical boot drive:
Logo=0
This method permanently prevents the logo screen from being displayed.
For information about how to edit the Msdos.sys file, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q118579
TITLE : Contents of the Windows Msdos.sys File
http://support.microsoft.com/support/kb/articles/Q193/2/42.ASP
----
I'd try disabling the LOGO screen problems/bypassing as well. More follows.
----
This was the reference I mentioned about the other impacts of viruscan software as it regards and hangs up the Windows logon logo screen ....
http://support.microsoft.com/support/kb/ARTICLES/Q150/5/16.asp
Synopsis: When you start Windows, your computer may stop responding (hang) after the Windows logo screen is displayed.
NOTE: Windows 95 may start properly if you press the F8 key when you see the "Starting Windows 95" message, choose Step-By-Step Confirmation from the Startup menu, and then press Y at each prompt. In Windows 98, press and hold CTRL.
CAUSE
This problem may be caused by either of the following situations:
An anti-virus program warning screen may be hidden behind the Windows logo screen. This problem occurs if Windows is loading an anti- virus program from the Autoexec.bat file to automatically check for a virus. The anti-virus program detects that the Command.com file has changed as a result of the Windows installation and pauses the system to inform you and receive further instructions.
The display adapter installed in your computer is not properly handling the video mode switching that occurs when the Windows logo screen is displayed. This video mode switching does not occur when you choose Step-By-Step Confirmation from the Startup menu, because the Windows logo screen is not displayed.
This problem is known to occur with the following display adapters:
ATI Graphics Ultra Pro (Mach32)
RESOLUTION
To determine whether anti-virus software is running, press the ESC key to close the Windows logo screen. If anti-virus software is running, you may be able to access it from this screen. Choose the option that allows the program to update any affected files. This prevents the pause from occurring when you start Windows in the future.
If no anti-virus software is running, use one of the following options to determine whether disabling the logo screen will resolve the problem:
Add the following line to the [Options] section of the Msdos.sys file in the root folder of the physical boot drive:
Logo=0
This method permanently prevents the logo screen from being displayed.
For information about how to edit the Msdos.sys file, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q118579
TITLE : Contents of the Windows Msdos.sys File
Does your soundcard have an option to load a USER Instrument Bank or something like Creative Lab's AWE32 SoundFont?
Have you tried defragmenting your harddrive by using Norton SpeedDisk? Try and rearrange the files such that all files under a subdirectory resides in contiguous clusters right beside each other, followed by it's parent directory.
Have u tried to run an in-depth surface scan of your harddrive using Norton Disk Doctor? Use the multipass option.
Scan your disks integrity, both data area and free area.
Have you tried defragmenting your harddrive by using Norton SpeedDisk? Try and rearrange the files such that all files under a subdirectory resides in contiguous clusters right beside each other, followed by it's parent directory.
Have u tried to run an in-depth surface scan of your harddrive using Norton Disk Doctor? Use the multipass option.
Scan your disks integrity, both data area and free area.
Falcon?
let us know if ya workin or not
let us know if ya workin or not
ASKER
comment astaec: Thanks for the info supplied but I am almost 100% sure it has nothing to do with virus scan or norton related problems. I have removed them and faced exactly the same problems. As Pslh was mentioning, (I think he is on the right track in this regard), it is my network configuration that is really causing the boot up delay and nothing else. I am currently trying to understand an follow his suggestions.
COmment Femson7: Thanks for trying to help. But I dont think I have problems that you are referring to at all. I have tried Norton disk doctory to do scanning etc. and no problems. I also used Norton system works to find and fix problems too.. And i used my McCafee to check for viruses with th elates virus definition file.
I really think the main problem is the network configuration.
COmment Femson7: Thanks for trying to help. But I dont think I have problems that you are referring to at all. I have tried Norton disk doctory to do scanning etc. and no problems. I also used Norton system works to find and fix problems too.. And i used my McCafee to check for viruses with th elates virus definition file.
I really think the main problem is the network configuration.
I totally agree with you, Falcon, the PSLH recommendations are most important and KEY, which is why I started my piece of the participation with these comments...
"A lot of valuable input and things for you to check so don't want to add to your workload until results are known. Do, though, want to agree very much with the slow boot process as it regards the network setup AND running these background programs."
I'm sorry if I misunderstood, I just didn't want you to discount the potential impact of background programs by sharing our experience in that regard.
"A lot of valuable input and things for you to check so don't want to add to your workload until results are known. Do, though, want to agree very much with the slow boot process as it regards the network setup AND running these background programs."
I'm sorry if I misunderstood, I just didn't want you to discount the potential impact of background programs by sharing our experience in that regard.
falcon, please unlock this question by rejecting ahkit81's proposed answer. Pslh
ASKER
I am sorry this is not a correct answer. Please read the history for the reasons. The problem is related to network card as Pslh correctly identified all along.
Thanks for trying to help anyway.
Falcon
Thanks for trying to help anyway.
Falcon
ASKER
comment to pslh and majus:
I am sorry I have not had a chance to work with my PC yesterday to try some of your suggestions.
I will do it tonight and keep you posted.
Pslh: As per your suggestion, I have rejected the answer and unlocked the question.
Thanks again.
I am sorry I have not had a chance to work with my PC yesterday to try some of your suggestions.
I will do it tonight and keep you posted.
Pslh: As per your suggestion, I have rejected the answer and unlocked the question.
Thanks again.
ASKER
Comment to PSLH, MAjus and all others who tried to help me. Here is the update on my situation:
First of all, I did "ESC" to see what is happening behind the logo screen. Indeed Mc Cafee started and finished scanning with no virus found etc message and all.. Everything happened in a blurr. No delay here.. after wards there was the long period of guiet ness (2 Min. 15 sec) as I referred to in my previous comments and in the question.
I removed 6 and 7. I did not specifically do a scandisk etc. becuase this was done so many times before.
when I removed 6 and 7 i had only 2) and 3) from my list left and nothing else at all.. I restarted. and it exactly tollk like 10 to 15 secs after the blurr of mc cafee scan. then I am into windows. It solved the problem. Now my dial up did not work. so I have to install again the TCP/IP dial up in order to be able to use the modem to connect to my ISP. When I did that along with the old 7) appeared there too..
Here is the new list now.
1. Client for Microsoft Networks
2. Dial Up Adapter
3. Linksys LNE PCI II PCI Ethernet Adapter
4. TCP/IP -> Dial UP Adapter
5. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
I made appropriate changes to WINS as indicated by pslh. This I did for both 4 and 5.
Here I would like to mention that my DNS Tab had info pertaining to the my ISP provider address.. and that remained same for both 4 and 5. I am not sure about this. but Unless i specify this my dial up to my ISP does not work. I think... not sure. Anyway, after all these changes made everything became back to normal. I have my 2 min. 15 sec silence with no activity as usual. May be as someone suggestion something wrong with my network settings still.
Falcon
First of all, I did "ESC" to see what is happening behind the logo screen. Indeed Mc Cafee started and finished scanning with no virus found etc message and all.. Everything happened in a blurr. No delay here.. after wards there was the long period of guiet ness (2 Min. 15 sec) as I referred to in my previous comments and in the question.
I removed 6 and 7. I did not specifically do a scandisk etc. becuase this was done so many times before.
when I removed 6 and 7 i had only 2) and 3) from my list left and nothing else at all.. I restarted. and it exactly tollk like 10 to 15 secs after the blurr of mc cafee scan. then I am into windows. It solved the problem. Now my dial up did not work. so I have to install again the TCP/IP dial up in order to be able to use the modem to connect to my ISP. When I did that along with the old 7) appeared there too..
Here is the new list now.
1. Client for Microsoft Networks
2. Dial Up Adapter
3. Linksys LNE PCI II PCI Ethernet Adapter
4. TCP/IP -> Dial UP Adapter
5. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
I made appropriate changes to WINS as indicated by pslh. This I did for both 4 and 5.
Here I would like to mention that my DNS Tab had info pertaining to the my ISP provider address.. and that remained same for both 4 and 5. I am not sure about this. but Unless i specify this my dial up to my ISP does not work. I think... not sure. Anyway, after all these changes made everything became back to normal. I have my 2 min. 15 sec silence with no activity as usual. May be as someone suggestion something wrong with my network settings still.
Falcon
Falcon, the hint has come up very significant this time after our step-by-step diagnostic approach.
<<Here I would like to mention that my DNS Tab had info pertaining to the my ISP provider address.. and that remained same for both 4 and 5. I am not sure about this. but Unless i specify this my dial up to my ISP does not work. I think... not sure. Anyway, after all these changes made everything became back to normal. I have my 2 min. 15 sec silence with no activity as usual. May be as someone suggestion something wrong with my network settings still.
4. TCP/IP -> Dial UP Adapter
5. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
Don’t enter your ISP DNS in the TCP/IP of both (4) and (5).
Select the (4), click [properties], DNS Configuration, select the option box: -
[x] Disable DNS.
Click OK.
Remark: If you enter your ISP DNS at the protocols, your computer will search them as your server domain till the searching failed and time up for disconnecting to your said ISP DNS. Therefore, the time spent from searching to disconnect searching needs exactly 2 min. 15 sec silence in every booting.
In addition, go to select the Client for Microsoft networks, click properties.
At the General tab, unchecked the box for [ ] log on to window NT domain.
Network logon options: -
[x] Logon and restore network connection.
Click OK.
Next, we go to the My computer, Dial up networking (DUN), set up the DUN for your ISP by adding new.
After setting up a new DUN, select it and go to the “Server Types”, checked only following boxes: -
[x] Enable software compression
[x] TCP/IP
Click into the [TCP/IP Settings..] button. Select following boxes by checked the radio button.
[x] Server assigned IP address
[x] Specify name server address
Primary DNS: [ here enter your ISP provided Primary DNS]
Secondary DNS: [ here enter your ISP provided Secondary DNS]
[x] Use IP header compression
[x] Use default gateway on remote network.
Click OK.
Your DUN to your ISP has been setup.
Restart the computer and checking the times. I assume this time your computer will not search for your ISP server domain.
Let me know if it worked. Pslh
<<Here I would like to mention that my DNS Tab had info pertaining to the my ISP provider address.. and that remained same for both 4 and 5. I am not sure about this. but Unless i specify this my dial up to my ISP does not work. I think... not sure. Anyway, after all these changes made everything became back to normal. I have my 2 min. 15 sec silence with no activity as usual. May be as someone suggestion something wrong with my network settings still.
4. TCP/IP -> Dial UP Adapter
5. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
Don’t enter your ISP DNS in the TCP/IP of both (4) and (5).
Select the (4), click [properties], DNS Configuration, select the option box: -
[x] Disable DNS.
Click OK.
Remark: If you enter your ISP DNS at the protocols, your computer will search them as your server domain till the searching failed and time up for disconnecting to your said ISP DNS. Therefore, the time spent from searching to disconnect searching needs exactly 2 min. 15 sec silence in every booting.
In addition, go to select the Client for Microsoft networks, click properties.
At the General tab, unchecked the box for [ ] log on to window NT domain.
Network logon options: -
[x] Logon and restore network connection.
Click OK.
Next, we go to the My computer, Dial up networking (DUN), set up the DUN for your ISP by adding new.
After setting up a new DUN, select it and go to the “Server Types”, checked only following boxes: -
[x] Enable software compression
[x] TCP/IP
Click into the [TCP/IP Settings..] button. Select following boxes by checked the radio button.
[x] Server assigned IP address
[x] Specify name server address
Primary DNS: [ here enter your ISP provided Primary DNS]
Secondary DNS: [ here enter your ISP provided Secondary DNS]
[x] Use IP header compression
[x] Use default gateway on remote network.
Click OK.
Your DUN to your ISP has been setup.
Restart the computer and checking the times. I assume this time your computer will not search for your ISP server domain.
Let me know if it worked. Pslh
the new list now.
1. Client for Microsoft Networks
2. Dial Up Adapter
3. Linksys LNE PCI II PCI Ethernet Adapter
4. TCP/IP -> Dial UP Adapter
5. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
OK Now Falcon, Here's an optimal setup:
Quick Explanation First.
Consider #1, #3, & #5 a group.
This group connects your workstation your other workstation. We'll call this "your network".
#1 (The Client Software) gives logon access to "your network" and sends and receives data.
#3 (The Adapter Driver) Talks to your Network Interface Card (NIC), which physically connects you to "your network".
#5 (TCP/IP) is the communication protocol stack used on "your network". Transport Control Protocol/Internet Protocol is stacked together to form a complete OSI Model Solution for a common language of communication between the different devices on the network. With only TCP/IP, you can only communicate with devices that also have a minimum of TCP/IP configured. IPX/SPX is another protocol stack used for communication. With both TCP/IP and IPX/SPX, you can use either/or to communicate over your network. These rules also apply to your other workstation and any other device you may one day have on "your network".
Consider #2 & #4 a group also.
This group connects your workstation to "The Internet"
The actual components are a combination of your modem, Dial-Up Networking (DUN), the Dial-UP Adapter (#2), and TCP/IP (#4).
Ok, Now on with the setup.
Since we're gettin this deep go ahead and leave all installed network components as is, we're just gonna configure them now.
#5 is the one we're concerned with mostly. Double-Click #5 and enter 192.168.1.1 as the ip address and 255.255.255.0 as the subnet mask. You shouldn't have to change anything else.
However, you don't necessarily need the DNS enabled on this TCP/IP. Domain Name Service (DNS) is for resolving a name into an address.
It may be needed on your other TCP/IP bound to the Dial-Up Adapter for proper Internet Name Resolution.
ie: www.whatever.com = 204.122.34.63
this is a ficticios url and address
The Domain Name Server addresses are generally entered into the Dial-Up Networking connection entry under the TCP/IP settings there. But anyway nevermind that for now.
After you click ok on #5, go to your other workstation and find its' equivalent to #5 and set its' ip address to 192.168.1.2 and the subnet mask to 255.255.255.0
I know pslh said this is unnecessary, but trust me... if you set it, it will stay. if you let windows do it, who knows.
if this still gives you problems then look at the NIC you just installed and your cables. by the way... how are the 2 workstations connected... through a hub or a cross-patch cable? look at those too. if a cross-patch cable check the colors and make sure pin 1 is crossed with pin 3, and pin 2 is crossed with pin 6.
1. Client for Microsoft Networks
2. Dial Up Adapter
3. Linksys LNE PCI II PCI Ethernet Adapter
4. TCP/IP -> Dial UP Adapter
5. TCP/IP -> Linksys LNE PCI II PCI Ethernet Adapter
OK Now Falcon, Here's an optimal setup:
Quick Explanation First.
Consider #1, #3, & #5 a group.
This group connects your workstation your other workstation. We'll call this "your network".
#1 (The Client Software) gives logon access to "your network" and sends and receives data.
#3 (The Adapter Driver) Talks to your Network Interface Card (NIC), which physically connects you to "your network".
#5 (TCP/IP) is the communication protocol stack used on "your network". Transport Control Protocol/Internet Protocol is stacked together to form a complete OSI Model Solution for a common language of communication between the different devices on the network. With only TCP/IP, you can only communicate with devices that also have a minimum of TCP/IP configured. IPX/SPX is another protocol stack used for communication. With both TCP/IP and IPX/SPX, you can use either/or to communicate over your network. These rules also apply to your other workstation and any other device you may one day have on "your network".
Consider #2 & #4 a group also.
This group connects your workstation to "The Internet"
The actual components are a combination of your modem, Dial-Up Networking (DUN), the Dial-UP Adapter (#2), and TCP/IP (#4).
Ok, Now on with the setup.
Since we're gettin this deep go ahead and leave all installed network components as is, we're just gonna configure them now.
#5 is the one we're concerned with mostly. Double-Click #5 and enter 192.168.1.1 as the ip address and 255.255.255.0 as the subnet mask. You shouldn't have to change anything else.
However, you don't necessarily need the DNS enabled on this TCP/IP. Domain Name Service (DNS) is for resolving a name into an address.
It may be needed on your other TCP/IP bound to the Dial-Up Adapter for proper Internet Name Resolution.
ie: www.whatever.com = 204.122.34.63
this is a ficticios url and address
The Domain Name Server addresses are generally entered into the Dial-Up Networking connection entry under the TCP/IP settings there. But anyway nevermind that for now.
After you click ok on #5, go to your other workstation and find its' equivalent to #5 and set its' ip address to 192.168.1.2 and the subnet mask to 255.255.255.0
I know pslh said this is unnecessary, but trust me... if you set it, it will stay. if you let windows do it, who knows.
if this still gives you problems then look at the NIC you just installed and your cables. by the way... how are the 2 workstations connected... through a hub or a cross-patch cable? look at those too. if a cross-patch cable check the colors and make sure pin 1 is crossed with pin 3, and pin 2 is crossed with pin 6.
majus, <<I know pslh said this is unnecessary, but trust me... if you set it, it will stay. if you let windows do it, who knows>> I knew and every one can check it up if you know the method and it is well published by Microsoft. I thought you might need to study deeper within this topic in win98.
Moreover, I did run LAN if you know there is a term for dynamic ISP and static ISP.
Nowadays, dynamic ISP address is the trend which enables the Win98 Second Edition - Internet Connection Sharing.
You might also have a look on this how its mechanism is working if a home family has five or ten computers and they can share one modem to go to the internet with a networking system been built.
Pslh
Moreover, I did run LAN if you know there is a term for dynamic ISP and static ISP.
Nowadays, dynamic ISP address is the trend which enables the Win98 Second Edition - Internet Connection Sharing.
You might also have a look on this how its mechanism is working if a home family has five or ten computers and they can share one modem to go to the internet with a networking system been built.
Pslh
ASKER
COmment to Pslh: and Majus:
I just completed all the instructions of PSLH.. which essentially boils down to disabling DNS and WINS in 4 and 5. Actualy by disabling DNS in 4 automatically disables DNS in 5 also.. which Only now I found out but intuitively obvious!. So now it should not try to find any adress etc. wasting time during the boot up.
First 30 or secs.. for bios intialization, P&P check, Mc Cafeev irus scan. etc.. over... pretty fast indeed and not much can be done this stage. Then came the infamous long silence of 2 or so minutes.. as usual which is the root cause of my posing this long question.. after this 2 minutes of silence then I see my background windows screen (in the proper 1024x768 resolution now!) and login screen. Here i type OK. From this point on whatever the time is taken I am not too much concerned but just happen to notice that it is not trivial either. But I understand that since I do have Norton, mccafee etc TSRs and they all have to be set up. Totla boot time is more like 4 or so minutes.
The two PC's are connected thru a hup and not by crossed wire. THe hub is powered.
By the way currently (since last night :( ) my second PC is out of commision and currently Pslh is trying to make that work too. I have problems with the OS in that PC. I somehow dont think this is causing the delay. SInce even when this was working I had the same long boot time.
Anyway that is where I am. Still the mysterious two minute silence behind the logo screen.. just after Mc. Cafee virus scan. Absolute silence during that peiod. I guess if I have to live with it I have to live with it.. or remove the damn network card! I donno.
I think unless i can get my second PC working I can not try majus' suggestion.. or can I still? not sure.
Falcno
I just completed all the instructions of PSLH.. which essentially boils down to disabling DNS and WINS in 4 and 5. Actualy by disabling DNS in 4 automatically disables DNS in 5 also.. which Only now I found out but intuitively obvious!. So now it should not try to find any adress etc. wasting time during the boot up.
First 30 or secs.. for bios intialization, P&P check, Mc Cafeev irus scan. etc.. over... pretty fast indeed and not much can be done this stage. Then came the infamous long silence of 2 or so minutes.. as usual which is the root cause of my posing this long question.. after this 2 minutes of silence then I see my background windows screen (in the proper 1024x768 resolution now!) and login screen. Here i type OK. From this point on whatever the time is taken I am not too much concerned but just happen to notice that it is not trivial either. But I understand that since I do have Norton, mccafee etc TSRs and they all have to be set up. Totla boot time is more like 4 or so minutes.
The two PC's are connected thru a hup and not by crossed wire. THe hub is powered.
By the way currently (since last night :( ) my second PC is out of commision and currently Pslh is trying to make that work too. I have problems with the OS in that PC. I somehow dont think this is causing the delay. SInce even when this was working I had the same long boot time.
Anyway that is where I am. Still the mysterious two minute silence behind the logo screen.. just after Mc. Cafee virus scan. Absolute silence during that peiod. I guess if I have to live with it I have to live with it.. or remove the damn network card! I donno.
I think unless i can get my second PC working I can not try majus' suggestion.. or can I still? not sure.
Falcno
ASKER
comment to PSLH and Majus:
Eventhough My second PC is currently not working, i decide to give it a try to majus suggestion as well. I used the ip addrees and subnet mask suggested by majus. And for the first time in a long long time, i found that it some how breezed thru!.. It probably took like close to a min now.. instead of the usual 2min 15 sec. So may be this the solution. Now I am not sure by doing this whether the functionality of my network is compromised anywhich way.. I will only be able to check after I resolve my problems with the other PC. which still i have not been able to put Win 98 OS on ... keeps going into safe mode. For now, however, i consider this problem solved. I think I owe about 300 points to PSLH ( who was first to solve my resolution problem) and about 200 points to majus: please let me know if this is acceptable.. or if you would like to make any changes or whatever. And If so.. please let me know how i shall implement it. Thanks once again.
Falcon
Eventhough My second PC is currently not working, i decide to give it a try to majus suggestion as well. I used the ip addrees and subnet mask suggested by majus. And for the first time in a long long time, i found that it some how breezed thru!.. It probably took like close to a min now.. instead of the usual 2min 15 sec. So may be this the solution. Now I am not sure by doing this whether the functionality of my network is compromised anywhich way.. I will only be able to check after I resolve my problems with the other PC. which still i have not been able to put Win 98 OS on ... keeps going into safe mode. For now, however, i consider this problem solved. I think I owe about 300 points to PSLH ( who was first to solve my resolution problem) and about 200 points to majus: please let me know if this is acceptable.. or if you would like to make any changes or whatever. And If so.. please let me know how i shall implement it. Thanks once again.
Falcon
Yes, you can try it. I would go ahead and disable the DNS on the NIC's TCP/IP. Another troubleshooter could be to take the NIC from your other Workstation, since it's out of commission, and install it to see if results are different. you should remove the old one first from Network Properties, then shutdown, then physically remove the NIC, then put the other one in. Make sure you've got the drivers for the other NIC.
For that matter, does it help if no NIC is installed? Is bootup quicker?
For that matter, does it help if no NIC is installed? Is bootup quicker?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Falcon,
I could care less about any points, but I do appreciate the gesture. I'm just glad you're booting again. Do make sure you setup the address on the other computer so that both machines will be on the same TCP/IP subnet.
As for pslh,
first of all I never said you were wrong, I merely suggested that if you set a TCP/IP address and tell windows which subnet the workstation was on then windows doesn't have to do a thing to figure out anything.... you told it by setting the address.
I would like more info on your concepts, so throw me some urls.
Personally from what I read from you on this particular subject, I think you wasted much time and energy in all your typing and wasted Falcon's time and energy also. All your idiotic removing and running this and running that made no logical sense. It was obvious that there was some sort of network problem caused by connecting one workstation to the other. You went all the way around the world to do nothing. You wouldn't make it at all out in the real world of networking and troubleshooting. But that's my personal opinion which is like something else; we all got one and we all think everyone else's stinks.
I could care less about any points, but I do appreciate the gesture. I'm just glad you're booting again. Do make sure you setup the address on the other computer so that both machines will be on the same TCP/IP subnet.
As for pslh,
first of all I never said you were wrong, I merely suggested that if you set a TCP/IP address and tell windows which subnet the workstation was on then windows doesn't have to do a thing to figure out anything.... you told it by setting the address.
I would like more info on your concepts, so throw me some urls.
Personally from what I read from you on this particular subject, I think you wasted much time and energy in all your typing and wasted Falcon's time and energy also. All your idiotic removing and running this and running that made no logical sense. It was obvious that there was some sort of network problem caused by connecting one workstation to the other. You went all the way around the world to do nothing. You wouldn't make it at all out in the real world of networking and troubleshooting. But that's my personal opinion which is like something else; we all got one and we all think everyone else's stinks.
falcon, I've just read through your last comment. I would like to clarify before you have made any changes to add an ISP address as majus said.
If you have changed as I said
<<<I just completed all the instructions of PSLH.. which essentially boils down to disabling DNS and WINS in 4 and 5. Actualy by disabling DNS in 4 automatically disables DNS in 5 also.. which Only now I found out but intuitively obvious!. So now it should not try to find any adress etc. wasting time during the boot up. >>>
Have you tried to restart the computer for 3 successive trials before changes made effective?
You can unassign the ISP address, restart it 3 times. If you find the time goes back to your original long time, assign an ISP address is the key.
One of my network LAN does not need to assign an IP address and it does not need that long.
Hope you give me a serve and re-testify it. Pslh
If you have changed as I said
<<<I just completed all the instructions of PSLH.. which essentially boils down to disabling DNS and WINS in 4 and 5. Actualy by disabling DNS in 4 automatically disables DNS in 5 also.. which Only now I found out but intuitively obvious!. So now it should not try to find any adress etc. wasting time during the boot up. >>>
Have you tried to restart the computer for 3 successive trials before changes made effective?
You can unassign the ISP address, restart it 3 times. If you find the time goes back to your original long time, assign an ISP address is the key.
One of my network LAN does not need to assign an IP address and it does not need that long.
Hope you give me a serve and re-testify it. Pslh
majus,
<<Personally from what I read from you on this particular subject, I think you wasted much time and energy in all your typing and wasted Falcon's time and energy also. All your idiotic removing and running this and running that made no logical sense. It was obvious that there was some sort of network problem caused by connecting one workstation to the other. You went all the way around the world to do nothing. You wouldn't make it at all out in the real world of networking and troubleshooting. But that's my personal opinion which is like something else; we all got one and we all think everyone else's stinks.>>
If you are trying to personal attack someone (PSLH), try to save up your energy here and please don't spoil this thread and annoying Falcon and me. Don't make it a gesture of being a winner. In that way you won't win other's respect other than just points.
Pslh
<<Personally from what I read from you on this particular subject, I think you wasted much time and energy in all your typing and wasted Falcon's time and energy also. All your idiotic removing and running this and running that made no logical sense. It was obvious that there was some sort of network problem caused by connecting one workstation to the other. You went all the way around the world to do nothing. You wouldn't make it at all out in the real world of networking and troubleshooting. But that's my personal opinion which is like something else; we all got one and we all think everyone else's stinks.>>
If you are trying to personal attack someone (PSLH), try to save up your energy here and please don't spoil this thread and annoying Falcon and me. Don't make it a gesture of being a winner. In that way you won't win other's respect other than just points.
Pslh
if you do try to disprove my theory then please run winipcfg and release your ip address in your testing
ASKER
Comment to PSLH: Your last suggestion came After i sent my comment indicating that by specifying the IP address for NIC, it seemed to have helped .. and reduced the boot time. after I sent the comment I received your email regarding the suggestion that involves removing completely NIC etc. I have not tried it yet but I will definitely try it.
However, if I remove the NIC adapter etc.. and unplug the hub, still since the card is physically sitting there on a slot during the booting up windows will find it and prompt " new hardware found etc." right.. So are you suggesting to remove the card also and we know in that case the boot time is definitely will be reduced by this time. It is pretty obvious. right? Well I am confused here a bit.
However, if I remove the NIC adapter etc.. and unplug the hub, still since the card is physically sitting there on a slot during the booting up windows will find it and prompt " new hardware found etc." right.. So are you suggesting to remove the card also and we know in that case the boot time is definitely will be reduced by this time. It is pretty obvious. right? Well I am confused here a bit.
ASKER
comment to both PSLH and Majus: I think there is no need to fight over this. Together we solved something which looked almost impossible to me when it first started and It put great amount of stress in my mind. I am really thankful for both of your advices, and i have learnt a lot in the process. So let us forget and not argue anymore on this. I sure will like to give it a try to PSLH's last suggestion. But for now, my problem has been solved atleast one way and both of you have contributed and both deserve the points. So my main concern is how do I distribute points!
falcon
falcon
falcon, It seems we're now talking in real time but there is a lag in email notification and reloading the update of this thread.
Thank for your consideration in hearing some of my voices and in helping me in verify the real cause.
Meanwhile, as you recalled before assignning the IP address, you've made changes to disable DNS of your ISP's DNS in the TCP/IP protocol. You've made changes to the DUN. Let me say it is changes (A).
As I suspected before all these changes (A) made effective (It may need 3 successive restart of your computer after changes to notify win98 to amend its registry. After amendment in the registry, changes would then be effective.) However, perhaps in the mid-way you have made the assignment of ISP address to the TCP/IP protocol. Let me say it is changes (B). Later, you've found time is shortened.
Would this be the result of (A)? Would this be the result of (B)?
Therefore, I would like to seek you help in re-testify it.
Cancel the changes made by (B). If it went back to a long time, it would be surely the shortened time was caused by the changes of (B). If it really were that way, you could change back to (B) by adding back the IP address. Checking the time, it was shortened.
We may conclude something for future resolutions.
Falcon I knew you're concerning how to split points. In my opinion, I could give you some of the ideas later.
Thank in advance. Pslh
Thank for your consideration in hearing some of my voices and in helping me in verify the real cause.
Meanwhile, as you recalled before assignning the IP address, you've made changes to disable DNS of your ISP's DNS in the TCP/IP protocol. You've made changes to the DUN. Let me say it is changes (A).
As I suspected before all these changes (A) made effective (It may need 3 successive restart of your computer after changes to notify win98 to amend its registry. After amendment in the registry, changes would then be effective.) However, perhaps in the mid-way you have made the assignment of ISP address to the TCP/IP protocol. Let me say it is changes (B). Later, you've found time is shortened.
Would this be the result of (A)? Would this be the result of (B)?
Therefore, I would like to seek you help in re-testify it.
Cancel the changes made by (B). If it went back to a long time, it would be surely the shortened time was caused by the changes of (B). If it really were that way, you could change back to (B) by adding back the IP address. Checking the time, it was shortened.
We may conclude something for future resolutions.
Falcon I knew you're concerning how to split points. In my opinion, I could give you some of the ideas later.
Thank in advance. Pslh
ASKER
comment pslh:
I like your suggestion which I shall try and let you know in due course of time. I too want to get to the bottom of this and learn something for future. It is around past 12 midnight.. so i may or may not get to it yet.. but by tomorrow morning for sure i would have studied the consequences and metered the times for you. Thanks again
falcon
I like your suggestion which I shall try and let you know in due course of time. I too want to get to the bottom of this and learn something for future. It is around past 12 midnight.. so i may or may not get to it yet.. but by tomorrow morning for sure i would have studied the consequences and metered the times for you. Thanks again
falcon
give em all to pslh
The final outcome of resolution, refer to this thread: https://www.experts-exchange.com/jsp/qShow.jsp?ta=win98&qid=10250094
To test this can you phyically remove the network card and see what happens then?
Also go to Start, Run, type MSCONFIG and click OK, go to the startup tab and uncheck everything listed there (except Systray) and see if this helps. You can try this before removing the network card to see if thats improves the boot time, then try removing the network card too and test.
You have some very time intensive programs loading at boot (Norton, McAffee)