Some help with a file please.

[Croc]

During boot, a screen comes up that has the following in it:

D
C\:AUTOEXEC.BAX
File not found
File not found
File not found
File not found

This only comes up when I use the OEM disk to format/reload the system. Unfortunately I have no choice but to use the OEM now after the W98 disk was damaged beyond repair.

I would appreciate some advice that will stop this screen from coming up.

TIA. :)

Croc.

[Norm]

At what point is that coming up Croc?
Is windows fully installed by then?

Explain a little more in detail.

It's an entry in autoexec.bat but why it's there or how it got there is a mystery to me. It may be OEM related.

Is windows working ok?

[blebs]

http://www.no-panic.com/backup/tech_supt/trblsht.html

Maybe? Rename AUTOEXEC.BAX to AUTOEXEC.BAT? Sounds like an OEM thing to me.

[Norm]

Blebbs, that might work, but it looks to me like that autoexec.bat is calling autoexec.bax and the errors are coming because autoexec.bax is looking for files that don't exist.

Look for autoexec.bat in the root of C:\ right click>Edit
It will open in Notepad. Take out any lines that appear odd.

Be careful not to remove lines pertaining to a sound card, or you won't have sound in any games etc that use Dos drivers.

[Croc]

It's only when I have used the OEM disk to reload the HD that this comes up.

The screen comes up during the boot process and just after AVG does it's boot scan. Windows has not kicked in at that point. The first Windows screen comes up just after the 'File not found' screen closes.

Also, doing a search for autoexec.bat was negative as well.

Thanks for the help here. :)

Croc.

[Norm]

Croc, go to start>setting>folder options then View Tab, and uncheck "Hide Known File extentions" and check "Show all files"
Apply

Then look for autoexec.bat again.

[Croc]

It was already unchecked, Norm. I had done that and tried it before I logged on.

Also... my bad.... the window comes up with:

d
File not found C:\AUTOEXEC.BAX
Bad command or file name
Bad command or file name
Bad command or file name
Bad command or file name

not what I posted in the first post. (AArrrgh this short term memory loss is driving me nuts!!!! ;))

I just rebooted after trying the rename and nothing different.

Croc.

[Norm]

Hmmm, try opening config.sys in notepad using the same method. Have a look in that file. If lots there, post a copy.

Post a copy of autoexec.bat as well.

[Croc]

config.sys is MT. Not one entry when I opened it with Notepad.

autoexec.bat does not exist.

autoexec.bax does exist but Properties say:
0 files
0 folders
0 bytes.


Croc.

[TonyT]

search all drives for the missing file, it may have been placed in incorrect location, either by mistake or by another app.

also, anti-virus app may be locking out the .bax file because it thinks it's got koodies.

[Croc]

My system is a P2 with a 4gig hd fitted. It's the only drive.
The problem never happens if I use the W98 disk... only the OEM.

I have had this happen once before and I can't remember what I did then. It was over 2 years ago. AVG didn't cause it then cause it wasn't installed.

Croc.

[Norm]

AVG didn't cause it, but it may be avg (or some other program) rewriting a file used at boot.

I would try deleting all files that start with autoexec in the root of C:

Another thing that may work is using msconfig, and editing the autoexec.bat file from there. It seems very odd to me that autoexec.bat doesn't exist.

Also, you could try.
sys c:
From a boot floppy

[Croc]

Thanks Norm. Have to go to work now so I will try it all again tonight.

Croc.

[Norm]

Croc, before you do anything can you do me a favor (or 3)? What you are experiencing is of interest to me and I'd like to know how OEM installs work.

1. Post the contents of msdos.sys (found in root of c:)
2. Post the contents of dostart.bat (found in windows dir)
3. Does the OEM install of windows appear the same as the retail version as it installs, or is it an image file (or some other strange method?

I get the feeling that your OEM version has created a hidden drive, and has placed the path to it in msdos.sys in the HostWinBootDrv= line. That would explain why you can't find autoexec.bat.

There are a few tricks that can explain why autoexec.bat is nowhere to be found, but that one is my guess.

AVG writes to autoexec.bat in order to run the bootup scan, so it's got to be somewhere, since you see it scan when you bootup.
This is the line AVG puts in autoexec.bat -
C:\PROGRA~1\GRISOFT\AVG6\bootup.exe

Note: You could also use FIND and put that line in the box for "Containing text" to find the file that it is written in.

Note: You can use tweakui to see if any drives are hidden. Under the "My Computer" tab. A hidden drive will be unchecked.

[Murman]

Originally posted by Croc
During boot, a screen comes up that has the following in it:

D
C\:AUTOEXEC.BAX
File not found
File not found
File not found
File not found

This only comes up when I use the OEM disk to format/reload the system. Unfortunately I have no choice but to use the OEM now after the W98 disk was damaged beyond repair.




look in the windows folder

[TonyT]

Norm -

I've seen similar issues on a Compaq once. During install, the oem cd created a partition (visible) and installs the set up files there. And yes, it was basically a drive image that was copied to the partition.

Croc-
I have a solution. Send me a self adressed envelope pre-paid postage and I'll burn a copy of my win98 CD and mail it back. PM me if interested and I'll send my address.

[Norm]

Yeah, some of those OEM installs irritate the hell out of me when I'm in the field, and I need to get a better understanding of what they are doing. Lots of different tricks they use. It may be a virtual drive, and hidden.

I was working on a Compaq for a couple of hours once, and got it all fixed up and tweaked. After a reboot or 2 later (once I had gone) the system was right back the way it was before I started. My best guess was it creates an image every day or so, and IF the Compac proprietary 'programming' thinks there is a problem, it puts the image back. I eventually Fdisked, formatted and loaded windows my way.

I hope Croc sees this before he does a sys c:, I really want to know what's up. As far as I know, it's the msdos.sys file the 'enforces' the path to the boot drive.

[Croc]

[Paths]
WinDir=c:\windows
WinBootDir=c:\windows
HostWinBootDrv=c

[Options]
BootMulti=1
BootGUI=1
DoubleBuffer=1
;
;The following lines are required for compatibility with other programs.
;Do not remove them (MSDOS.SYS needs to be >1024 bytes).
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxb
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxf
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxg
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxh
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxi
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxk
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxl
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxm
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxn
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxo
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxp
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxq
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxr
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxs
AutoScan=1
WinVer=4.10.1998

:D
I had started to gather all your requests Norm, but I needed some sleep.

The visual as OEM loads is very uninteresting. Basicly it's the BSOD background colour with all the .cab file paths displayed as they are opened and loaded. The screen continuously scrolls as each file is finished with and the process can take around 2 hours.

When I did the search for the line:

C:\PROGRA~1\GRISOFT\AVG6\bootup.exe

all I found were two Temp Internet Files that referred to this thread.

What if I were to place something in the .bax file or simply delete it altogether?

The other requests were not able to be completed. I will get a copy of TweakUI and see what comes of it.

TonyT... I thank you for the offer. I would be interested but I can get alternative copies here. The other alternative could be to put on W98SE which would be more beneficial to me now the son has moved out and taken his networking gear with him. Then I could use ICS. We tried that and had problems with the IDE controllers.

That's about it.

Thanks guys for this. It's only a small thing really but just shouldn't happen.

Croc.