Annoyances.org
Home » Windows 95 Discussion Forum » Message 1019706825 » Entire Thread Search | Help | Home
  
Question about 'Identifying the programs that Windows runs at boot'
Showing all messages in thread #1019706825
Windows 95 Annoyances Discussion Forum


The following are all of the messages in this thread (8 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
Question about 'Identifying the programs that Windows runs at boot'
Wednesday, April 24, 2002 at 8:53 pm
Posted by Brian (11 messages posted)

I have a question about Identifying the programs that Windows runs at boot:

Can anyone tell me EXACTLY what the boot sequence is in Win95? I am having trouble tracking 2 msg's that come up during boot. It would appear they are registry related but cannot track them, even with the bootlog. They come up immediately after the c:\ prompt and the hardware beeps are heard. When I do a F8, with step by step confirmation they both come up after ack of the WIN command to start windows. But I don't know what the sequence of loading drivers, vxd's, ini files and such is and how this relates back to the information contained in the registry. Can someone help me pleaseeeeeeeeeeeee? Thank you in advance if you can!

[Reply or follow-up to this message]

re: Question about 'Identifying the programs that Windows runs at boot'
Thursday, April 25, 2002 at 4:03 am
Posted by Steve Easton (5183 messages posted)

What are the messages??
The windows boot sequence is here: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q174018





On Wednesday, April 24, 2002 at 8:53 pm, Brian wrote: >I have a question about Identifying >the programs that Windows runs at boot:

> >Can anyone tell me EXACTLY what the boot sequence is in Win95? I am having trouble >tracking >2 msg's that come up during boot. It would appear they are registry >related but cannot track them, even with the bootlog. They come up >immediately after the c:\ prompt and the hardware beeps are heard. >When I do a F8, with step by step confirmation they both come up after >ack of the WIN command to start windows. But I don't know what the >sequence of loading drivers, vxd's, ini files and such is and how this relates back >to the information contained in the registry. > >Can someone help me pleaseeeeeeeeeeeee? > >Thank you in advance if you can!

[Reply or follow-up to this message]

re: Question about 'Identifying the programs that Windows runs at boot'
Thursday, April 25, 2002 at 2:48 pm
Posted by Brian (11 messages posted)

Steve, Thanx for the link, I'll look into it and see if I can decipher what's happening. As for the messages, they are as follows: The first one says "the windows registry or System.ini file is trying to load a device that is missing.....blah, blah about reinstalling. Problem is, there is no file listed to search for. I'm almost positive is a .vxd file, but cannot find a blank reference. Any ideas how to do this effectively? The second one give me the message "invalid path, not directory, or directory not empty" This one was caused by a bad install of some Rockwell touchscreen software that crashed mid-install. I have not been able to locate the source of the message. FYI, I have used Regedit by Regsoft, versions 1.1 and 2.0.....RegVac 1.1 by Super Win Software, and Dll Orphans by microsoft to clean the junk out of the registry. Despite that the problems persist. Any suggestions on how to find the source of these messages would be extremely helpful.


On Thursday, April 25, 2002 at 4:03 am, Steve Easton wrote:

>What are the messages??
>The windows boot sequence is here: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q174018
>
>

[Reply or follow-up to this message]

re: Question about 'Identifying the programs that Windows runs at boot'
Friday, April 26, 2002 at 3:52 am
Posted by Steve Easton (5183 messages posted)

Brian, any time the system.ini or win.ini files are modified during a program install the previous ones are "normally" saved with a .syd extension. Look for system.ini and name it system.old and then change system.syd to system.ini Do the same for the win.ini and win.syd files and then restart the computer.


On Thursday, April 25, 2002 at 2:48 pm, Brian wrote:
>Steve,
> Thanx for the link, I'll look into it and see if I can decipher what's happening.
> As for the messages, they are as follows:
> The first one says "the windows registry or System.ini file is trying to load
>a device that is missing.....blah, blah about reinstalling. Problem is, there is
>no file listed to search for. I'm almost positive is a .vxd file, but cannot find
>a blank reference. Any ideas how to do this effectively?
> The second one give me the message "invalid path, not directory, or directory
>not empty" This one was caused by a bad install of some Rockwell touchscreen software
>that crashed mid-install. I have not been able to locate the source of the message.
> FYI, I have used Regedit by Regsoft, versions 1.1 and 2.0.....RegVac 1.1 by
>Super Win Software, and Dll Orphans by microsoft to clean the junk out of the registry.
> Despite that the problems persist.
> Any suggestions on how to find the source of these messages would be extremely
>helpful.
>
>

[Reply or follow-up to this message]

re: Question about 'Identifying the programs that Windows runs at boot'
Saturday, April 27, 2002 at 10:54 pm
Posted by Brian (11 messages posted)

Steve, I solved the first problem, concerning the device missing. It was from vftd.vxd missing in the registry. There was a blank "" setting I has suspected. The link in the page you sent me took me directly to the vxd files and I found it there. Thanks! Any idea what that file is for? VFTD.VXD..... Now, if i can just find the source of the other mystery fault I'll be in pretty good shape. That one doesn't stop the boot process, it's just annoying. I'll take a look at the .ini files and see if that shows me anything. I've searched them for inaccurate directories on previous occasions and haven't found any yet. It's gotta be there, I just have had zero luck tracking it down so far.


On Friday, April 26, 2002 at 3:52 am, Steve Easton wrote:
>Brian, any time the system.ini or win.ini files are modified during a program install
>the previous ones are "normally" saved with a .syd extension. Look for system.ini
>and name it system.old and then change system.syd to system.ini Do the same for
>the win.ini and win.syd files and then restart the computer.
>
>

[Reply or follow-up to this message]

re: Question about 'Identifying the programs that Windows runs at boot'
Sunday, April 28, 2002 at 7:05 am
Posted by Steve Easton (5183 messages posted)

What is the file or file reference that can't be found?


On Saturday, April 27, 2002 at 10:54 pm, Brian wrote:
>Steve,
> I solved the first problem, concerning the device missing. It was from vftd.vxd
>missing in the registry. There was a blank "" setting I has suspected. The link
>in the page you sent me took me directly to the vxd files and I found it there.
>Thanks! Any idea what that file is for? VFTD.VXD.....
> Now, if i can just find the source of the other mystery fault I'll be in pretty
>good shape. That one doesn't stop the boot process, it's just annoying.
> I'll take a look at the .ini files and see if that shows me anything. I've
>searched them for inaccurate directories on previous occasions and haven't found
>any yet. It's gotta be there, I just have had zero luck tracking it down so far.
>
>
>

[Reply or follow-up to this message]

re: Question about 'Identifying the programs that Windows runs at boot'
Sunday, April 28, 2002 at 10:03 pm
Posted by Brian (11 messages posted)

Steve, The fault that remains gives me no indication of a file referrence. It simply says "invalid path, not directory or directory no empty". It fills up approx a screen and a half in the dos window on boot up. I am at a loss on where to search further. I'm almost positive it originated from 2 consecutive install failures from Rockwell software. I cannot however locate the origin either in the registry or in system.ini, win.ini, autoexec.bat, or config.sys. Other suggestions? Another question for you. Is there a way to remove what shows up in the various "right click" pop-ups? That is to say, when you right click on a file and the various options show up. Is there a way to delete one or more of these? Brian


On Sunday, April 28, 2002 at 7:05 am, Steve Easton wrote:
>What is the file or file reference that can't be found?
>
>

[Reply or follow-up to this message]

re: Question about 'Identifying the programs that Windows runs at boot'
Monday, April 29, 2002 at 6:20 am
Posted by Steve Easton (5183 messages posted)

Brian, it sounds as if the computer is trying to finish the incomplete install.  
boot to safe mode and clear the start menu startup folder. the restart in DOS and 
type the following hitting enter after each and Y for yes when prompted.
cd:\
smartdrv
cd:\windows
deltree tempor~1
deltree history
deltree cookies
deltree temp
scandisk
and then restart the computer.





On Sunday, April 28, 2002 at 10:03 pm, Brian wrote: >Steve, > The fault that remains gives me no indication of a file referrence. It simply >says "invalid path, not directory or directory no empty". It fills up approx a screen >and a half in the dos window on boot up. I am at a loss on where to search further. > I'm almost positive it originated from 2 consecutive install failures from Rockwell >software. I cannot however locate the origin either in the registry or in system.ini, >win.ini, autoexec.bat, or config.sys. Other suggestions? > Another question for you. Is there a way to remove what shows up in the various >"right click" pop-ups? That is to say, when you right click on a file and the various >options show up. Is there a way to delete one or more of these? > >Brian > >

[Reply or follow-up to this message]

Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
Return to the Windows 95 Discussion Forum

All content at Annoyances.org is Copyright © 1995-2008 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.