VGAOEM

[Tom]

I keep getting the following message:
--------------
Windows could not start. The following file is missing or
corrupted \windows\system\vgaoem.fon.

You can attempt to repair this file by starting Windows
setup using the original setup CD-ROM. Select 'r' at the
first screen to start repair.
---------------
Have repeatedly followed the instructions in:

http://support.microsoft.com/?kbid=315338

which seems to work for a while, until a couple of weeks
later. Then the message appears again. If anyone knows of a
permanent solution I would love to hear it.

Ta,

Tom

 

[Will Denny]

Hi Tom

Try here:

http://groups.google.com/groups?q=c...\vgaoem.fon&ie=UTF-8&hl=en&btnG=Google+Search

 

[Tom]

Hi Tom,my H/P did that to me after SP2 update,was running
funny for 2 days after it,then got that after reboot.H/P
claims it's from SP2.If windows came preloaded,pump the
F10 key at start-up,till you get the recovery screen,then
select the NON-DESTRUCTIVE recovery,you can hit the
destructive recovery thru advance button,but that will
set everything back like the day you bought it new.Non-D
will replace the missing files erase SP2,and change all
settings back,but will leave all your files and folders
in tact!

 

[Tom again]

Oh ya (follow up to previous post)if you didn't have it
preloaded,then you need to put in the start-up disc push
r then administrator password:leave blank push enter.At
the prompt type in
expand d:\i386\vgaoem.fo_ c:\windows\system
just a little problem I had,after the uderscore in .fo_
make sure you leave a space after it,between the
(_)and(cand a space between(expand)and(d
it will comeup with vgaoem.fo_ 1 file(s)
expanded. then type in exit,and push enter.Take out the
disc,and it will boot into windows.If you have Home any
Home disc will work for this,if it's Pro,any Pro will
work.I did my H/P with F10,and a friend at work we did it
with another friends XP disc,both were XP Home,both were
H/P's,both went south after SP2 updates one in 2 days,the
other right after SP2 reboot.H/P claims their working on
the fix for it with microsoft,it's the OEM factory
XP,They told me only a small percent of H/P's are
affected,told me 10% to 15%.Geuss everythings not
perfect,Both are working fine now.Everything comes at a
price,If not for the hackers out there,we wouldn't have
to worry,but the worlds not a kind place.

 

[Tom again]

Tom,here is the address from microsoft that has the fix
like I listed from Tom again,two Toms should be able to
fix it.Copy and paste it to you address bar and Go to
it,you may want to copy it to have when you go to fix the
other box.Like I posted B-4 make sure to leave a space
between expand d: and .fo_ c: and you don't
put the n in .fo_ that space drove me nuts I was putting
it in without it and it kept coming up access denied.Good
Luck Tom,,,,,,Tom

 

[andy]

Oh ya (follow up to previous post)if you didn't have it
preloaded,then you need to put in the start-up disc push
r then administrator password:leave blank push enter.At
the prompt type in
expand d:\i386\vgaoem.fo_ c:\windows\system
just a little problem I had,after the uderscore in .fo_
make sure you leave a space after it,between the
(_)and(cand a space between(expand)and(d
it will comeup with vgaoem.fo_ 1 file(s)
expanded. then type in exit,and push enter.Take out the
disc,and it will boot into windows.If you have Home any
Home disc will work for this,if it's Pro,any Pro will
work.I did my H/P with F10,and a friend at work we did it
with another friends XP disc,both were XP Home,both were
H/P's,both went south after SP2 updates one in 2 days,the
other right after SP2 reboot.H/P claims their working on
the fix for it with microsoft,it's the OEM factory
XP,They told me only a small percent of H/P's are
affected,told me 10% to 15%.Geuss everythings not
perfect,Both are working fine now.Everything comes at a
price,If not for the hackers out there,we wouldn't have
to worry,but the worlds not a kind place.

Wow, not seen this errors in years! Was a regular one when I worked at Tiny
(please don't hate me!) years ago with windows 3.1, or windows 95, I forget,
was ages ago!

Andy

 

[John Boy]

Do you have your anti virus set to delete infected files?
If you do this could be your problem,check in the
options,and select clean instead of delete.If that
doesn't do it you may want to think about deleteing SP2
from add and remove,till they find a patch for this
fix.Could you post back with,1:computer
manufacterer,2:antivirus you use,3:do you use Ad-
Aware,4:do you use Zone Alarm firewall w/XP's firewall?

 

[Paul]

-----Original Message-----



Wow, not seen this errors in years! Was a regular one when I worked at Tiny
(please don't hate me!) years ago with windows 3.1, or windows 95, I forget,
was ages ago!

Andy


.
Wow Andy,your as old as me.It came back when people

upgraded to XP from windows 98,and now again with SP2 it
seems,have seen several other posts in the past couple of
weeks. Paul

 

[andy]

..
upgraded to XP from windows 98,and now again with SP2 it
seems,have seen several other posts in the past couple of
weeks. Paul

Hi Paul, ah, memories!

Yep, must be a sp2 thing. Only installed it at work on one pc as yet, one
with hardly any software on apart from yer bog-standard ms office apps and
not going to install it at home for ages yet, waiting to get a large hard
drive to ghost my computers to before I do!

Andy

 

[Tom]

Hi,

Thanks for all your help. I've been laid up with a cold
recently, so haven't been online since I posted.

Am replying to John Boy as he seems to have targeted my
problem best:
1. Concorde computers
2. Norton
3. Spybot (not Ad-Aware)
4. No

Am trying to see whether I can get Norton to ignore that
file - and see whether that helps. It does make sense that
the intermittent nature of the problem is related somehow
to the intermittent nature of my complete system scan.

Will let you know if any progress is made.

Tom