AV software and PC in safe mode

My *guess* is that you *might* have a hardware/driver issue as you machine
boots into Normal Mode.

Boot into Safe Mode and look in Device Manager for any/all yellow
exclamation marks or duplicate (or multiple) instances of devices (sound
card, video card, monitor, etc.) and 'Remove' ALL of them from DevMan.

Re-boot and see if things improve.

.... I saw loadfails in bootlog.txt regarding True
Type Fonts. What do you think?

This is not unusual when the boot process fails during a driver/hardware
issue. There is a 'fix' for a marlett font issue, but I don't think this is
your problem at the moment.

FYI, but don't act on it just yet - "Description of and Troubleshooting the
Marlett TrueType Font"
http://support.microsoft.com/default.aspx?scid=kb;[LN];134861

Mart


wrote in message
...
The ol****.exe file is oltrga.exe....not olgtra. Had it
written down incorrectly in my notes and didn't realize it
until now. Sorry for confusion. Anyway, this routine and
error is out of commission. I haven't deleted it yet, but
will if/when I can get all things working in normal boot.
Taking it out of system.ini took care of this error. I
may break into song when I finally delete it. g

When I boot up normally, I get an Explorer error "An error
has occurred in your program. Click Ignore.. or Click
Close.." Clicking ignore does nothing. Clicking Close
takes me to 2nd error "Explorer has caused an error in
GDI.EXE. Explorer will now close." I click on "Close",
get gray screen that stays. I press ctrl+alt+del and
Close Program window comes up showing one thing
running..Osd. I click on Shut Down and system seems to
shut down okay. If I could get past the explorer error in
normal, I might actually be able to fix this thing!

Did some research on GDI.exe. Think it may have to do
with fonts. I saw loadfails in bootlog.txt regarding True
Type Fonts. What do you think?
ex: LoadStart=C:\Windows\fonts\Marlett.ttf
LoadFail=C:\Windows\fonts\Marlett.ttf
Failure code is 0016
Haven't had chance to check out this failure code number.

FYI, I ran Stinger again in safe mode. This time I did
not click on repair, only report and there were two files
found containing the w32/Klez.h@MM virus.
C:_Restore\Archive\FS1360.CAB\A0168847.CPY
C:_Restore\Archive\FS1360.CAB\A0168848.CPY
I understand that finding the virus in the restore
archives should not affect this PC unless I use the
infected restore points. It was not found anywhere else.


-----Original Message-----
Cannot boot to desktop in normal mode. I get an
explorer error that stops me.

What error? (exact wording AND symptoms please)

Mmmm..... But you then go on to say:-

Don't get olgtra error in normal
anymore, either.

Confused? - Well I am! see next paragraph.

Can you confirm the name of the da*ned oltrxx.file,??
You've put at least a
couple of names:- olgtra.exe and oltrga.exe. Not that I
can find any
reference to either, but it would be nice to know g

The rest of your reply sounds good though. But like I
said originally - one
thing at a time.

Mart


wrote in message
...
Great suggestion! Looked at startup tab in msconfig.
Didn't find anything there. I then went through every
tab.
Happened to find reference to olgtra.exe under
system.ini
tab in boot folder. (Sneaky devil!) Shell=Explorer.exe
olgtra.exe I removed olgtra.exe part. Still have not
deleted the actual exe file. Wanted to see what would
happen on next boot.
Reboot to safe mode working pretty well. Error re
olgtra does not come up. Not getting any other errors
in
safe mode. Happy! Don't get olgtra error in normal
anymore, either. Can work nicely in safe mode with its
limitations. Thank you!
Cannot boot to desktop in normal mode. I get an
explorer error that stops me.

-----Original Message-----
Well if the 'Software House' that wrote the oltrga.exe
application can't be
bothered to build their details into it (but is an old
date) then I would
suspect that it is even more rogue than I first
thought.

Try Start | Run and type "msconfig" (no quotes) in the
space provided and
then click OK. Look for the Startup Tab and see if
there
is any reference to
oltrga and if so, uncheck the appropriate box.

Re-boot and see if it rids you of the Oltrga error -
you
will probably get a
'warning' that you have something set in msconfig, each
time you boot, but
ignore it for the time being. Just see if the Oltrga
error goes.

Mart


"Jane" wrote in
message
...
Sorry, Mart. I could have explained better. All I
saw
under properties for the oltrga.exe is described
below.
There was only a general tab, no version tab. It
provided
very little info.

snipped


.



.