98 errors -VPICD, V86MMGR, 386enhanced

philo · Mar 2, 2008

"keith" <uncle@tanoose.nut> wrote in message
news:uP8XaUFfIHA.1900@TK2MSFTNGP02.phx.gbl...
> Have seen a few errors at different times lately when booting / rebooting
> after system lock-ups.
>
> 'While initializing device VPICD: Windows protection error.'
> 'While initializing (installing??) V86MMGR: error cannot
> install 386 enhanced MXSD'
> Not sure if it said installing or initializing.
> Not sure I got the MXSD part correctly - MVXD? or
some
> variation.
> And one about dangerously low resources.
>
> Tried a couple of SCANRE /RESTORE dates from prior to errors but still
got
> the VPICD error on this last boot.
>
> W98 with 2 drives - First is just Windows and other programs - only 2 out
of
> 6 gigs used
> Second is just files, fotos, vids - about
80
> out of 95 gigs used.
> Second has been as high as 90
out
> of 95 without problems.
> Its usually in the 70-75 out of
> 90 range
>
> Have start up sequence set to display Normal, Safe Mode, Command
Promp
> Only , etc menu with 30 second wait period.
> Ocasiionaly Normal doesn't load and it goes back to the menu with
Safe
> Mode hilighted but can usually choose Normal again and complete the
> start-up.
> Nothing out of the ordinary with SpyBot, Ad-Aware, SpyWare Blaster or
> AVG scans.
> Nothing new in Add/Remove Programs list or ALT/CTRL/DEL list
>
> Thaught I'd post this first while this rig seems to be working OK and will
> start searching for solutions / references.
> Any ideas what to do next?
> Thanks.
>
>

Try a RAM test for starters

http://oca.microsoft.com/en/windiag.asp

keith · Mar 2, 2008

Have seen a few errors at different times lately when booting / rebooting
after system lock-ups.

'While initializing device VPICD: Windows protection error.'
'While initializing (installing??) V86MMGR: error cannot
install 386 enhanced MXSD'
Not sure if it said installing or initializing.
Not sure I got the MXSD part correctly - MVXD? or some
variation.
And one about dangerously low resources.

Tried a couple of SCANRE /RESTORE dates from prior to errors but still got
the VPICD error on this last boot.

W98 with 2 drives - First is just Windows and other programs - only 2 out of
6 gigs used
Second is just files, fotos, vids - about 80
out of 95 gigs used.
Second has been as high as 90 out
of 95 without problems.
Its usually in the 70-75 out of
90 range

Have start up sequence set to display Normal, Safe Mode, Command Promp
Only , etc menu with 30 second wait period.
Ocasiionaly Normal doesn't load and it goes back to the menu with Safe
Mode hilighted but can usually choose Normal again and complete the
start-up.
Nothing out of the ordinary with SpyBot, Ad-Aware, SpyWare Blaster or
AVG scans.
Nothing new in Add/Remove Programs list or ALT/CTRL/DEL list

Thaught I'd post this first while this rig seems to be working OK and will
start searching for solutions / references.
Any ideas what to do next?
Thanks.

philo · Mar 2, 2008

"keith" <uncle@tanoose.nut> wrote in message
news:%23CDzG0IfIHA.5160@TK2MSFTNGP05.phx.gbl...
> Thanks. That was quick.
> Swimming in unfamiliar waters -
> Printed the Diagnostic pages for reference.
> Download/save the Diagnostic to a blank CD-R in the in the CD drive and
use
> that to re-boot?
>

I always just run it from a floppy
if you use that option, just put a blank drive in...and the utility will
load to the bootable floppy

if you save the cd image to your harddrive. when you
burn it. you will need to use the "burn image" option of your cd buring
software.
you cannot simply write the iso file to the cd

> "philo" <philo@privacy.net> wrote in message
> news:evypshGfIHA.4140@TK2MSFTNGP04.phx.gbl...
> >
> > "keith" <uncle@tanoose.nut> wrote in message
> > news:uP8XaUFfIHA.1900@TK2MSFTNGP02.phx.gbl...
> > > Have seen a few errors at different times lately when booting /
> rebooting
> > > after system lock-ups.
> > >
> > > 'While initializing device VPICD: Windows protection
> error.'
> > > 'While initializing (installing??) V86MMGR: error
cannot
> > > install 386 enhanced MXSD'
> > > Not sure if it said installing or initializing.
> > > Not sure I got the MXSD part correctly - MVXD? or
> > some
> > > variation.
> > > And one about dangerously low resources.
> > >
> > > Tried a couple of SCANRE /RESTORE dates from prior to errors but
still
> > got
> > > the VPICD error on this last boot.
> > >
> > > W98 with 2 drives - First is just Windows and other programs - only 2
> out
> > of
> > > 6 gigs used
> > > Second is just files, fotos, vids -
about
> > 80
> > > out of 95 gigs used.
> > > Second has been as high as
90
> > out
> > > of 95 without problems.
> > > Its usually in the 70-75
out
> of
> > > 90 range
> > >
> > > Have start up sequence set to display Normal, Safe Mode, Command
> > Promp
> > > Only , etc menu with 30 second wait period.
> > > Ocasiionaly Normal doesn't load and it goes back to the menu with
> > Safe
> > > Mode hilighted but can usually choose Normal again and complete the
> > > start-up.
> > > Nothing out of the ordinary with SpyBot, Ad-Aware, SpyWare
Blaster
> or
> > > AVG scans.
> > > Nothing new in Add/Remove Programs list or ALT/CTRL/DEL list
> > >
> > > Thaught I'd post this first while this rig seems to be working OK and
> will
> > > start searching for solutions / references.
> > > Any ideas what to do next?
> > > Thanks.
> > >
> > >
> >
> > Try a RAM test for starters
> >
> > http://oca.microsoft.com/en/windiag.asp
> >
> >
>
>

keith · Mar 2, 2008

Thanks. That was quick.
Swimming in unfamiliar waters -
Printed the Diagnostic pages for reference.
Download/save the Diagnostic to a blank CD-R in the in the CD drive and use
that to re-boot?

"philo" <philo@privacy.net> wrote in message
news:evypshGfIHA.4140@TK2MSFTNGP04.phx.gbl...
>
> "keith" <uncle@tanoose.nut> wrote in message
> news:uP8XaUFfIHA.1900@TK2MSFTNGP02.phx.gbl...
> > Have seen a few errors at different times lately when booting /
rebooting
> > after system lock-ups.
> >
> > 'While initializing device VPICD: Windows protection
error.'
> > 'While initializing (installing??) V86MMGR: error cannot
> > install 386 enhanced MXSD'
> > Not sure if it said installing or initializing.
> > Not sure I got the MXSD part correctly - MVXD? or
> some
> > variation.
> > And one about dangerously low resources.
> >
> > Tried a couple of SCANRE /RESTORE dates from prior to errors but still
> got
> > the VPICD error on this last boot.
> >
> > W98 with 2 drives - First is just Windows and other programs - only 2
out
> of
> > 6 gigs used
> > Second is just files, fotos, vids - about
> 80
> > out of 95 gigs used.
> > Second has been as high as 90
> out
> > of 95 without problems.
> > Its usually in the 70-75 out
of
> > 90 range
> >
> > Have start up sequence set to display Normal, Safe Mode, Command
> Promp
> > Only , etc menu with 30 second wait period.
> > Ocasiionaly Normal doesn't load and it goes back to the menu with
> Safe
> > Mode hilighted but can usually choose Normal again and complete the
> > start-up.
> > Nothing out of the ordinary with SpyBot, Ad-Aware, SpyWare Blaster
or
> > AVG scans.
> > Nothing new in Add/Remove Programs list or ALT/CTRL/DEL list
> >
> > Thaught I'd post this first while this rig seems to be working OK and
will
> > start searching for solutions / references.
> > Any ideas what to do next?
> > Thanks.
> >
> >
>
> Try a RAM test for starters
>
> http://oca.microsoft.com/en/windiag.asp
>
>

PCR · Mar 3, 2008

keith wrote:
| Have seen a few errors at different times lately when booting /
| rebooting after system lock-ups.
|
| 'While initializing device VPICD: Windows protection
| error.' 'While initializing (installing??) V86MMGR:
| error cannot
| install 386 enhanced MXSD'
| Not sure if it said installing or initializing.
| Not sure I got the MXSD part correctly - MVXD?
| or some variation.
| And one about dangerously low resources.
|
| Tried a couple of SCANRE /RESTORE dates from prior to errors but
| still got the VPICD error on this last boot.
|
| W98 with 2 drives - First is just Windows and other programs - only 2
| out of 6 gigs used
| Second is just files, fotos, vids -
| about 80 out of 95 gigs used.
| Second has been as high as
| 90 out of 95 without problems.
| Its usually in the 70-75
| out of 90 range
|
| Have start up sequence set to display Normal, Safe Mode, Command
| Promp Only , etc menu with 30 second wait period.
| Ocasiionaly Normal doesn't load and it goes back to the menu
| with Safe Mode hilighted but can usually choose Normal again and
| complete the start-up.

When an installation boots poorly only occasionally, the bootstrap is
probably fine. That includes BIOS, MBR (Master Boot Record), PBR
(Partition Boot Record), & all the files needed to boot, even the
Registry.

| Nothing out of the ordinary with SpyBot, Ad-Aware, SpyWare
| Blaster or AVG scans.
| Nothing new in Add/Remove Programs list or ALT/CTRL/DEL list
|
| Thaught I'd post this first while this rig seems to be working OK and
| will start searching for solutions / references.

(1) Run the RAM test as philo posted.
(2) Make a backup of your boot partition.
(It may be on its way out!)
(3) Run the hard drive diagnostic for your brand.
This repairs the structure of the hard drive, if necessary.
(4) Run a ScanDisk & Defrag.
This repairs the Windows file system, but could also
wreak havoc, if a big repair is necessary...
http://cquirke.mvps.org/9x/scandisk.htm

........Quote.......
You should run the diagnostics for the brand of hard drive that is in
the computer.

If you don't know what brand the drive is, you can download the
limited-use free edition of OnTrack Data Advisor from this location:
http://www.ontrack.com/freesoftware/#dataadvisor

When you click the download link on that page for Data Advisor 5.0 Free
edition, you will be taken to a page to register with the OnTrack site,
then you will be able to download the diskette creator file.

The downloads are diskette creators. They are to be run once from a
working Windows system and will guide you through the process of
extracting the Data Advisor onto a 3.5" floppy disk.

Download and Use Instructions:
http://www.ontrack.com/dataadvisor/downloadinfo.asp

Hard Drive Diagnostic Programs by Vendor:

The older version of SeaTools, for creating a bootable CD, is here:
http://www.majorgeeks.com/download2858.html

Hard Drive Diagnostic Programs by Vendor:

OnTrack Data Advisor:
http://www.ontrack.com/freesoftware/#dataadvisor
IBM/Hitachi Drive Fitness Test:
http://www.hgst.com/hdd/support/download.htm
Western Digital Data Lifeguard Tools:
http://support.wdc.com/download/
Quantum/Maxtor PowerMax:
http://www.seagate.com/ww/v/index.j...toid=a37d8b9c4a8ff010VgnVCM100000dd04090aRCRD
or
http://www.majorgeeks.com/Maxtor_Powermax_d1386.html
Seagate SeaTools for DOS:
http://www.seagate.com/www/en-us/support/downloads/seatools

--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm
......End.of... URLs of Glee...

| Any ideas what to do next?
| Thanks.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

keith · Mar 6, 2008

Sorry, gents, for the delayed response time. Neighbors have been keeping
me busy of late.
Downloaded the Diagnostic to hard drive and burned it to CD.Will check
Nero for 'burn image' option.
Created start up disk on a used, erased floppy. Got the "Success" dialog
box.

Tried different settings in F2 start-up - check diskette first, CD
first, hard drive first etc at re-boot.
No luck running WinDiag / mtinst.exe yet.
Pretty sure the HD is a Seagate but will open the bax and take a look
and try manufacturer's diagnostic..
Probably time to clear out the dust and cobwebs anyway. And re-read the
WinDiag instructions, too.

Thanks again.
Keith

"PCR" <pcrrcp@netzero.net> wrote in message
news:%23jgMP0YfIHA.1168@TK2MSFTNGP02.phx.gbl...
> keith wrote:
> | Have seen a few errors at different times lately when booting /
> | rebooting after system lock-ups.
> |
> | 'While initializing device VPICD: Windows protection
> | error.' 'While initializing (installing??) V86MMGR:
> | error cannot
> | install 386 enhanced MXSD'
> | Not sure if it said installing or initializing.
> | Not sure I got the MXSD part correctly - MVXD?
> | or some variation.
> | And one about dangerously low resources.
> |
> | Tried a couple of SCANRE /RESTORE dates from prior to errors but
> | still got the VPICD error on this last boot.
> |
> | W98 with 2 drives - First is just Windows and other programs - only 2
> | out of 6 gigs used
> | Second is just files, fotos, vids -
> | about 80 out of 95 gigs used.
> | Second has been as high as
> | 90 out of 95 without problems.
> | Its usually in the 70-75
> | out of 90 range
> |
> | Have start up sequence set to display Normal, Safe Mode, Command
> | Promp Only , etc menu with 30 second wait period.
> | Ocasiionaly Normal doesn't load and it goes back to the menu
> | with Safe Mode hilighted but can usually choose Normal again and
> | complete the start-up.
>
> When an installation boots poorly only occasionally, the bootstrap is
> probably fine. That includes BIOS, MBR (Master Boot Record), PBR
> (Partition Boot Record), & all the files needed to boot, even the
> Registry.
>
> | Nothing out of the ordinary with SpyBot, Ad-Aware, SpyWare
> | Blaster or AVG scans.
> | Nothing new in Add/Remove Programs list or ALT/CTRL/DEL list
> |
> | Thaught I'd post this first while this rig seems to be working OK and
> | will start searching for solutions / references.
>
> (1) Run the RAM test as philo posted.
> (2) Make a backup of your boot partition.
> (It may be on its way out!)
> (3) Run the hard drive diagnostic for your brand.
> This repairs the structure of the hard drive, if necessary.
> (4) Run a ScanDisk & Defrag.
> This repairs the Windows file system, but could also
> wreak havoc, if a big repair is necessary...
> http://cquirke.mvps.org/9x/scandisk.htm
>
> .......Quote.......
> You should run the diagnostics for the brand of hard drive that is in
> the computer.
>
> If you don't know what brand the drive is, you can download the
> limited-use free edition of OnTrack Data Advisor from this location:
> http://www.ontrack.com/freesoftware/#dataadvisor
>
> When you click the download link on that page for Data Advisor 5.0 Free
> edition, you will be taken to a page to register with the OnTrack site,
> then you will be able to download the diskette creator file.
>
> The downloads are diskette creators. They are to be run once from a
> working Windows system and will guide you through the process of
> extracting the Data Advisor onto a 3.5" floppy disk.
>
> Download and Use Instructions:
> http://www.ontrack.com/dataadvisor/downloadinfo.asp
>
> Hard Drive Diagnostic Programs by Vendor:
>
> The older version of SeaTools, for creating a bootable CD, is here:
> http://www.majorgeeks.com/download2858.html
>
> Hard Drive Diagnostic Programs by Vendor:
>
> OnTrack Data Advisor:
> http://www.ontrack.com/freesoftware/#dataadvisor
> IBM/Hitachi Drive Fitness Test:
> http://www.hgst.com/hdd/support/download.htm
> Western Digital Data Lifeguard Tools:
> http://support.wdc.com/download/
> Quantum/Maxtor PowerMax:
>
http://www.seagate.com/ww/v/index.j...toid=a37d8b9c4a8ff010VgnVCM100000dd04090aRCRD
> or
> http://www.majorgeeks.com/Maxtor_Powermax_d1386.html
> Seagate SeaTools for DOS:
> http://www.seagate.com/www/en-us/support/downloads/seatools
>
> --
> Glen Ventura, MS MVP W95/98 Systems
> http://dts-l.org/goodpost.htm
> .....End.of... URLs of Glee...
>
> | Any ideas what to do next?
> | Thanks.
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> Should things get worse after this,
> PCR
> pcrrcp@netzero.net
>
>

PCR · Mar 6, 2008

keith · Mar 8, 2008

PCR · Mar 10, 2008

keith wrote:
| Baught some NEW, UNUSED floppies.
| Downloaded the Windows Memory Diagnostic (mtinst.exe) again and ran
| the test(s).
| Ran the standard suite for 3 passes and the extended suite for 2
| passes. All 'Successful' and no errors found.

Very good. The RAM is fine.

| The 'WinDiag / mtinst.exe' confusion was all mine. Wasn't sure what
| to call it so typed the test name AND the file name.

I see. OK.

| There's probably an easy way to copy/paste or print the BIOS settings
| but I just wrote them all down
| and put them in the attached Word document.
|
| The large extra HD (for file storage) is the Seagate. The small main
| HD is a Quantum.
| Will try the Quantum/Maxtor links again and maybe the other RAM tests.

Keep us informed. I think something could be wrong either with the hard
drive itself or with the Windows file system. Another possibility is
that there is too much in the Startup Group, going by your words--
"dangerously low resources". Therefore...

"START button, Run, MSInfo32, Software Environment, Startup Programs".
Use the Edit menu to copy & post it.

| Thanks again.

You are welcome. That BIOS report isn't so huge. It looks fine to me,
(although I don't know what Chassis Intrusion or DAC Snoop is). Auto is
a good setting for the hard drives. I'll post it here, for others to
easily see...

Pentium II 400 Mhz System memory 15 MB SDRAM
Level 2 Cache 512 KB Integrated Video Memory 8 MB SGRAM

**********

Diskette A 1.44 MB
Diskette B Not Installed

Drives Type CYLS HDS PRE SEC SIZE
Primary
Drive 0 Auto 913 255 -1 63 7509
Drive 1 Auto EIDE Drive 65432
Secondary
Drive 0 Auto CD ROM Drive
Drive 1 Auto CD ROM Drive
**********

Reserved Memory 15 - 16 M
CPU Speed 400 Mhz
Num Lock On
Chassis Intrusion Disabled
DAC Snoop On
ACPI On

**********

Keyboard Errors Report
System Password Not Enabled
Password Status Unlocked
Boot Sequence Diskette First
Setup Password Not Enabled
Auto Power On Disabled 00:00
Power Management Regular
Wake-up on LAN Off

**********

| "PCR" <pcrrcp@netzero.net> wrote in message
| news:uQX2aw%23fIHA.2448@TK2MSFTNGP03.phx.gbl...

....snip
|> |> keith wrote:
|> |> | Have seen a few errors at different times lately when booting /
|> |> | rebooting after system lock-ups.
|> |> |
|> |> | 'While initializing device VPICD: Windows
|> |> | protection error.' 'While initializing
|> |> | (installing??) V86MMGR:
|> |> | error cannot
|> |> | install 386 enhanced MXSD'
|> |> | Not sure if it said installing or
|> |> | initializing. Not sure I got the MXSD part
|> |> | correctly - MVXD?
|> |> | or some variation.
|> |> | And one about dangerously low resources.
|> |> |
|> |> | Tried a couple of SCANRE /RESTORE dates from prior to errors
|> |> | but still got the VPICD error on this last boot.
|> |> |
|> |> | W98 with 2 drives - First is just Windows and other programs -
|> |> | only 2 out of 6 gigs used
|> |> | Second is just files, fotos,
|> |> | vids - about 80 out of 95 gigs used.
|> |> | Second has been as
|> |> | high as 90 out of 95 without problems.
|> |> | Its usually in the
|> |> | 70-75 out of 90 range
|> |> |
|> |> | Have start up sequence set to display Normal, Safe Mode,
|> |> | Command Promp Only , etc menu with 30 second wait period.
|> |> | Ocasiionaly Normal doesn't load and it goes back to the
|> |> | menu with Safe Mode hilighted but can usually choose Normal
|> |> | again and complete the start-up.
|> |>
|> |> When an installation boots poorly only occasionally, the
|> |> bootstrap is probably fine. That includes BIOS, MBR (Master Boot
|> |> Record), PBR (Partition Boot Record), & all the files needed to
|> |> boot, even the Registry.
|> |>
|> |> | Nothing out of the ordinary with SpyBot, Ad-Aware, SpyWare
|> |> | Blaster or AVG scans.
|> |> | Nothing new in Add/Remove Programs list or ALT/CTRL/DEL
|> |> | list
|> |> |
|> |> | Thaught I'd post this first while this rig seems to be working
|> |> | OK and will start searching for solutions / references.
|> |>
|> |> (1) Run the RAM test as philo posted.
|> |> (2) Make a backup of your boot partition.
|> |> (It may be on its way out!)
|> |> (3) Run the hard drive diagnostic for your brand.
|> |> This repairs the structure of the hard drive, if necessary.
|> |> (4) Run a ScanDisk & Defrag.
|> |> This repairs the Windows file system, but could also
|> |> wreak havoc, if a big repair is necessary...
|> |> http://cquirke.mvps.org/9x/scandisk.htm
|> |>

....snip
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

keith · Mar 10, 2008

Where did Philo's reply go? No longer in this string.

Data Advisor 5.00
Memory test - passed
Smart Status test - passed
90 second test - passed
File structure test - "unknown" - Not sure what that means. File structure
unknown? Test result unknown?

MAXTOR Power Max 4.23 manufacturer's test (for Quantum drive) - all passed.

Start>run>MSInfo32>Software environment>Startup Programs

SystemTray Registry (Machine Run) SysTray.Exe
ScanRegistry Registry (Machine Run)
C:\WINDOWS\scanregw.exe /autorun
LoadPowerProfile Registry (Machine Run) Rundll32.exe
powrprof.dll,LoadCurrentPwrScheme
PCPitStopEraser Registry (Machine Run) C:\Program
Files\PCPitstop\Erase\PCPitStopErase.exe /remindme
AVG7_CC Registry (Machine Run)
C:\PROGRA~1\GRISOFT\AVG7\AVGCC.EXE /STARTUP
AVG7_EMC Registry (Machine Run)
C:\PROGRA~1\GRISOFT\AVG7\AVGEMC.EXE
AVG7_AMSVR Registry (Machine Run)
C:\PROGRA~1\GRISOFT\AVG7\AVGAMSVR.EXE
LoadPowerProfile Registry (Machine Service) Rundll32.exe
powrprof.dll,LoadCurrentPwrScheme
KB891711 Registry (Machine Service)
C:\WINDOWS\SYSTEM\KB891711\KB891711.EXE
KB918547 Registry (Machine Service)
C:\WINDOWS\SYSTEM\KB918547\KB918547.EXE

Ran some test from PCPitStop long ago and still have their site in IE
favorites list.

Maybe the problem has been staring me in the face at every startup for
months on end.
Sometime last year a neighbor gave me and plugged in a couple extra 128
memory chips to go with the one original 128.
At every startup I get the following message
'Memory write/read failure at 100002020, read 00000000, expecting
00EF00EF. Decreasing available memory.'
A short pause and the continues with start up.
Always assumed it meant one of the extra chips was bad and ignored it all
this time and was just to lazy to pull it/them back out.
If there is only one in there the system says 128. With any two or all
three in there, the system says only 256. Ergo the bad chip assumption.

Still getting these newer ones though: (only one at a time but with
different devices)
'While initializing device VDD , windows protection error. Need to
restart computer.'
Usually VDD or VDK. Ocassionally VPICD. Once or twice with
V86MMGR or that 386enhanced thing.

Might take a couple of restarts to get to the Normal or Safe Mode option and
then a couple of Normal attempts there.
Needless to say, I don't turm it off very often.
But lots of re-starts lately with the diskette tests and checking the HD
manufacturer and those memory chips.
And I have gotten a couple of regular, straight thru startups, too.
No Win 98 discs on hand here if that is.where the problem lurks.

"PCR" <pcrrcp@netzero.net> wrote in message
news:eKLVBtngIHA.4140@TK2MSFTNGP04.phx.gbl...
> keith wrote:
> | Baught some NEW, UNUSED floppies.
> | Downloaded the Windows Memory Diagnostic (mtinst.exe) again and ran
> | the test(s).
> | Ran the standard suite for 3 passes and the extended suite for 2
> | passes. All 'Successful' and no errors found.
>
> Very good. The RAM is fine.
>
> | The 'WinDiag / mtinst.exe' confusion was all mine. Wasn't sure what
> | to call it so typed the test name AND the file name.
>
> I see. OK.
>
> | There's probably an easy way to copy/paste or print the BIOS settings
> | but I just wrote them all down
> | and put them in the attached Word document.
> |
> | The large extra HD (for file storage) is the Seagate. The small main
> | HD is a Quantum.
> | Will try the Quantum/Maxtor links again and maybe the other RAM tests.
>
> Keep us informed. I think something could be wrong either with the hard
> drive itself or with the Windows file system. Another possibility is
> that there is too much in the Startup Group, going by your words--
> "dangerously low resources". Therefore...
>
> "START button, Run, MSInfo32, Software Environment, Startup Programs".
> Use the Edit menu to copy & post it.
>
> | Thanks again.
>
> You are welcome. That BIOS report isn't so huge. It looks fine to me,
> (although I don't know what Chassis Intrusion or DAC Snoop is). Auto is
> a good setting for the hard drives. I'll post it here, for others to
> easily see...
>
> Pentium II 400 Mhz System memory 15 MB SDRAM
> Level 2 Cache 512 KB Integrated Video Memory 8 MB SGRAM
>
> **********
>
> Diskette A 1.44 MB
> Diskette B Not Installed
>
> Drives Type CYLS HDS PRE SEC SIZE
> Primary
> Drive 0 Auto 913 255 -1 63 7509
> Drive 1 Auto EIDE Drive 65432
> Secondary
> Drive 0 Auto CD ROM Drive
> Drive 1 Auto CD ROM Drive
> **********
>
> Reserved Memory 15 - 16 M
> CPU Speed 400 Mhz
> Num Lock On
> Chassis Intrusion Disabled
> DAC Snoop On
> ACPI On
>
> **********
>
> Keyboard Errors Report
> System Password Not Enabled
> Password Status Unlocked
> Boot Sequence Diskette First
> Setup Password Not Enabled
> Auto Power On Disabled 00:00
> Power Management Regular
> Wake-up on LAN Off
>
> **********
>
>
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:uQX2aw%23fIHA.2448@TK2MSFTNGP03.phx.gbl...
>
> ...snip
> |> |> keith wrote:
> |> |> | Have seen a few errors at different times lately when booting /
> |> |> | rebooting after system lock-ups.
> |> |> |
> |> |> | 'While initializing device VPICD: Windows
> |> |> | protection error.' 'While initializing
> |> |> | (installing??) V86MMGR:
> |> |> | error cannot
> |> |> | install 386 enhanced MXSD'
> |> |> | Not sure if it said installing or
> |> |> | initializing. Not sure I got the MXSD part
> |> |> | correctly - MVXD?
> |> |> | or some variation.
> |> |> | And one about dangerously low resources.
> |> |> |
> |> |> | Tried a couple of SCANRE /RESTORE dates from prior to errors
> |> |> | but still got the VPICD error on this last boot.
> |> |> |
> |> |> | W98 with 2 drives - First is just Windows and other programs -
> |> |> | only 2 out of 6 gigs used
> |> |> | Second is just files, fotos,
> |> |> | vids - about 80 out of 95 gigs used.
> |> |> | Second has been as
> |> |> | high as 90 out of 95 without problems.
> |> |> | Its usually in the
> |> |> | 70-75 out of 90 range
> |> |> |
> |> |> | Have start up sequence set to display Normal, Safe Mode,
> |> |> | Command Promp Only , etc menu with 30 second wait period.
> |> |> | Ocasiionaly Normal doesn't load and it goes back to the
> |> |> | menu with Safe Mode hilighted but can usually choose Normal
> |> |> | again and complete the start-up.
> |> |>
> |> |> When an installation boots poorly only occasionally, the
> |> |> bootstrap is probably fine. That includes BIOS, MBR (Master Boot
> |> |> Record), PBR (Partition Boot Record), & all the files needed to
> |> |> boot, even the Registry.
> |> |>
> |> |> | Nothing out of the ordinary with SpyBot, Ad-Aware, SpyWare
> |> |> | Blaster or AVG scans.
> |> |> | Nothing new in Add/Remove Programs list or ALT/CTRL/DEL
> |> |> | list
> |> |> |
> |> |> | Thaught I'd post this first while this rig seems to be working
> |> |> | OK and will start searching for solutions / references.
> |> |>
> |> |> (1) Run the RAM test as philo posted.
> |> |> (2) Make a backup of your boot partition.
> |> |> (It may be on its way out!)
> |> |> (3) Run the hard drive diagnostic for your brand.
> |> |> This repairs the structure of the hard drive, if necessary.
> |> |> (4) Run a ScanDisk & Defrag.
> |> |> This repairs the Windows file system, but could also
> |> |> wreak havoc, if a big repair is necessary...
> |> |> http://cquirke.mvps.org/9x/scandisk.htm
> |> |>
>
> ...snip
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> Should things get worse after this,
> PCR
> pcrrcp@netzero.net
>
>

PCR · Mar 11, 2008

keith wrote:
| Where did Philo's reply go? No longer in this string.

I see two responses by philo, & I can't remember if there were any more.
You answered his 1st (3/2/08 9:21 AM), but not his 2nd (3/2/08 7:04 PM).
WELL, you may have included the answer to his 2nd in your answer to my
1st. Anyhow, it was about how to run WinDiag-- which I think you've
done.

| Data Advisor 5.00
| Memory test - passed
| Smart Status test - passed
| 90 second test - passed

That is good. But does it say how much memory it is testing? Does it go
through all 3 chips or only two? I don't like what you say below about
your memory chips! It could be Windows is having a problem, despite
these chips seem to pass memory tests. Maybe the first thing to do is
really to pull that extra chip to get rid of the error message! Although
during boot you get the message "decreasing available memory"-- I can
think Windows might try to use it anyhow during those failed boots!

| File structure test - "unknown" - Not sure what that means. File
| structure unknown? Test result unknown?

http://www.ontrackdatarecovery.com/hard-drive-software/dataadvisor.aspx
Ontrack Data Recovery
........Quote...........
File Structure Test

Reads and verifies the integrity of the File Allocation Tables (FAT) on
DOS, Windows 3.x, Windows 95, 98, Me, NT*, 2000* and XP*. Checks
critical boot sectors, reads the Master Boot Record and cross-checks
partition tables and CMOS.

* Support for FAT formatted partitions only
........EOQ..............

That sounds like serious tests. Do you know which partition it is
referring to? Can it be an NTFS partition or other non-FAT partition
that DataAdvisor will not recognize? Try the FAQS link at that site, but
I could not find what "unknown" meant after a 20 minute intensive
search.

Windows's ScanDisk is meant to correct FAT errors. Defrag may also help.
But you should make a backup of your boot partition first, just in case
serious errors are found. You could try...

(a) Boot to DOS. (Hold CTRL as you boot for the Startup Menu, & select
"Command Prompt Only".)

(b) Scandisk /Checkonly /Surface

This will not fix, but only inform what it intends to fix.
It will display on screen & get written to "C:\Scandisk.log".
It may take quite a while to complete.

(c) Scandisk
Let it fix, if it didn't sound horrible. Otherwise, post what it
said.

In Dos, you may see "C:\Scandisk.log" this way...

EDIT C:\Scandisk.log
Alt-F-X (pressed separately) to exit EDIT. (TAB to traverse buttons.)

http://support.microsoft.com/kb/199557
Command-Line Parameters for the Scandisk Tool

| MAXTOR Power Max 4.23 manufacturer's test (for Quantum drive) - all
| passed.

The hard drive is good, then. It is the Windows file system that may
have a problem, (unless this is really a RAM issue after all).

| Start>run>MSInfo32>Software environment>Startup Programs
|
| SystemTray Registry (Machine Run) SysTray.Exe
| ScanRegistry Registry (Machine Run)
| C:\WINDOWS\scanregw.exe /autorun
| LoadPowerProfile Registry (Machine Run) Rundll32.exe
| powrprof.dll,LoadCurrentPwrScheme

Those are fine.

| PCPitStopEraser Registry (Machine Run) C:\Program
| Files\PCPitstop\Erase\PCPitStopErase.exe /remindme
| AVG7_CC Registry (Machine Run)
| C:\PROGRA~1\GRISOFT\AVG7\AVGCC.EXE /STARTUP
| AVG7_EMC Registry (Machine Run)
| C:\PROGRA~1\GRISOFT\AVG7\AVGEMC.EXE
| AVG7_AMSVR Registry (Machine Run)
| C:\PROGRA~1\GRISOFT\AVG7\AVGAMSVR.EXE

Maybe uncheck the above at...
"START, Run, MSConfig, Startup tab"
....to see whether something has gone wrong with them. But I would at
first be more inclined to with a ScanDisk/Defrag. If done in Windows
(instead of DOS), don't let them constantly restart-- post back for a
cure instead.

| LoadPowerProfile Registry (Machine Service) Rundll32.exe
| powrprof.dll,LoadCurrentPwrScheme
| KB891711 Registry (Machine Service)
| C:\WINDOWS\SYSTEM\KB891711\KB891711.EXE
| KB918547 Registry (Machine Service)
| C:\WINDOWS\SYSTEM\KB918547\KB918547.EXE

Those are fine, including the 2nd LoadPowerProfile, presuming you have
the repaired version of KB891711. But I'm sure you do.

| Ran some test from PCPitStop long ago and still have their site in IE
| favorites list.
|
| Maybe the problem has been staring me in the face at every
| startup for months on end.
| Sometime last year a neighbor gave me and plugged in a couple
| extra 128 memory chips to go with the one original 128.
| At every startup I get the following message
| 'Memory write/read failure at 100002020, read 00000000,
| expecting 00EF00EF. Decreasing available memory.'
| A short pause and the continues with start up.
| Always assumed it meant one of the extra chips was bad and ignored
| it all this time and was just to lazy to pull it/them back out.
| If there is only one in there the system says 128. With any two or
| all three in there, the system says only 256. Ergo the bad chip
| assumption.

Take one out permanently! I don't like that message!

| Still getting these newer ones though: (only one at a time but with
| different devices)
| 'While initializing device VDD , windows protection error. Need to
| restart computer.'
| Usually VDD or VDK. Ocassionally VPICD. Once or
| twice with V86MMGR or that 386enhanced thing.

Sounds like a complaint about the video (VDD) & the keyboard (VDK). We
can investigate these things if the other measures do not suffice.

| Might take a couple of restarts to get to the Normal or Safe Mode
| option and then a couple of Normal attempts there.
| Needless to say, I don't turm it off very often.
| But lots of re-starts lately with the diskette tests and checking the
| HD manufacturer and those memory chips.
| And I have gotten a couple of regular, straight thru startups, too.
| No Win 98 discs on hand here if that is.where the problem lurks.

Well, let's hope it doesn't come to that. But you won't need an
installation CD, if the .cab's are on the hard drive...

"START button, Find, F/F, Win98*.cab" (That's asterisk-dot-cab.)

If 55 of them show up, the folder that contains them is a copy of the
Installation CD. Normally, they are in "C:\Windows\Options\Cabs".

|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:eKLVBtngIHA.4140@TK2MSFTNGP04.phx.gbl...
|> keith wrote:
|> | Baught some NEW, UNUSED floppies.
|> | Downloaded the Windows Memory Diagnostic (mtinst.exe) again and ran
|> | the test(s).
|> | Ran the standard suite for 3 passes and the extended suite for 2
|> | passes. All 'Successful' and no errors found.
|>
|> Very good. The RAM is fine.
|>
|> | The 'WinDiag / mtinst.exe' confusion was all mine. Wasn't sure what
|> | to call it so typed the test name AND the file name.
|>
|> I see. OK.
|>
|> | There's probably an easy way to copy/paste or print the BIOS
|> | settings but I just wrote them all down
|> | and put them in the attached Word document.
|> |
|> | The large extra HD (for file storage) is the Seagate. The small
|> | main HD is a Quantum.
|> | Will try the Quantum/Maxtor links again and maybe the other RAM
|> | tests.
|>
|> Keep us informed. I think something could be wrong either with the
|> hard drive itself or with the Windows file system. Another
|> possibility is that there is too much in the Startup Group, going by
|> your words-- "dangerously low resources". Therefore...
|>
|> "START button, Run, MSInfo32, Software Environment, Startup
|> Programs". Use the Edit menu to copy & post it.
|>
|> | Thanks again.
|>
|> You are welcome. That BIOS report isn't so huge. It looks fine to me,
|> (although I don't know what Chassis Intrusion or DAC Snoop is). Auto
|> is a good setting for the hard drives. I'll post it here, for others
|> to easily see...
|>
|> Pentium II 400 Mhz System memory 15 MB SDRAM
|> Level 2 Cache 512 KB Integrated Video Memory 8 MB SGRAM
|>
|> **********
|>
|> Diskette A 1.44 MB
|> Diskette B Not Installed
|>
|> Drives Type CYLS HDS PRE SEC SIZE
|> Primary
|> Drive 0 Auto 913 255 -1 63 7509
|> Drive 1 Auto EIDE Drive 65432
|> Secondary
|> Drive 0 Auto CD ROM Drive
|> Drive 1 Auto CD ROM Drive
|> **********
|>
|> Reserved Memory 15 - 16 M
|> CPU Speed 400 Mhz
|> Num Lock On
|> Chassis Intrusion Disabled
|> DAC Snoop On
|> ACPI On
|>
|> **********
|>
|> Keyboard Errors Report
|> System Password Not Enabled
|> Password Status Unlocked
|> Boot Sequence Diskette First
|> Setup Password Not Enabled
|> Auto Power On Disabled 00:00
|> Power Management Regular
|> Wake-up on LAN Off
|>
|> **********
|>
|>
|> | "PCR" <pcrrcp@netzero.net> wrote in message
|> | news:uQX2aw%23fIHA.2448@TK2MSFTNGP03.phx.gbl...
|>
|> ...snip
|> |> |> keith wrote:
|> |> |> | Have seen a few errors at different times lately when
|> |> |> | booting / rebooting after system lock-ups.
|> |> |> |
|> |> |> | 'While initializing device VPICD: Windows
|> |> |> | protection error.' 'While initializing
|> |> |> | (installing??) V86MMGR:
|> |> |> | error cannot
|> |> |> | install 386 enhanced MXSD'
|> |> |> | Not sure if it said installing or
|> |> |> | initializing. Not sure I got the MXSD
|> |> |> | part correctly - MVXD?
|> |> |> | or some variation.
|> |> |> | And one about dangerously low resources.
|> |> |> |
|> |> |> | Tried a couple of SCANRE /RESTORE dates from prior to errors
|> |> |> | but still got the VPICD error on this last boot.
|> |> |> |
|> |> |> | W98 with 2 drives - First is just Windows and other programs
|> |> |> | - only 2 out of 6 gigs used
|> |> |> | Second is just files, fotos,
|> |> |> | vids - about 80 out of 95 gigs used.
|> |> |> | Second has been as
|> |> |> | high as 90 out of 95 without problems.
|> |> |> | Its usually in the
|> |> |> | 70-75 out of 90 range
|> |> |> |
|> |> |> | Have start up sequence set to display Normal, Safe Mode,
|> |> |> | Command Promp Only , etc menu with 30 second wait period.
|> |> |> | Ocasiionaly Normal doesn't load and it goes back to the
|> |> |> | menu with Safe Mode hilighted but can usually choose Normal
|> |> |> | again and complete the start-up.
|> |> |>
|> |> |> When an installation boots poorly only occasionally, the
|> |> |> bootstrap is probably fine. That includes BIOS, MBR (Master
|> |> |> Boot Record), PBR (Partition Boot Record), & all the files
|> |> |> needed to boot, even the Registry.
|> |> |>
|> |> |> | Nothing out of the ordinary with SpyBot, Ad-Aware,
|> |> |> | SpyWare Blaster or AVG scans.
|> |> |> | Nothing new in Add/Remove Programs list or ALT/CTRL/DEL
|> |> |> | list
|> |> |> |
|> |> |> | Thaught I'd post this first while this rig seems to be
|> |> |> | working OK and will start searching for solutions /
|> |> |> | references.
|> |> |>
|> |> |> (1) Run the RAM test as philo posted.
|> |> |> (2) Make a backup of your boot partition.
|> |> |> (It may be on its way out!)
|> |> |> (3) Run the hard drive diagnostic for your brand.
|> |> |> This repairs the structure of the hard drive, if
|> |> |> necessary. (4) Run a ScanDisk & Defrag.
|> |> |> This repairs the Windows file system, but could also
|> |> |> wreak havoc, if a big repair is necessary...
|> |> |> http://cquirke.mvps.org/9x/scandisk.htm
|> |> |>
|>
|> ...snip
|> --
|> Thanks or Good Luck,
|> There may be humor in this post, and,
|> Naturally, you will not sue,
|> Should things get worse after this,
|> PCR
|> pcrrcp@netzero.net

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

keith · Mar 14, 2008

Didn't see Philo's replies in the thread last time I posted.
Now I don't see the original post and full thread. Just this shortened
Re.thread.
Maybe it will all come back later. OE does get twitchy sometimes.

Quitr right. My answer to his 2nd was in my answer to your 1st.
Sorry, Philo. I'd posted that reply at the tail end of the thread. No snub
intended.
Will revisit posting tips and etiquette.

Seems it was those pesky extra memory cards after all.
Shuffled them around 1 at a time, 2 at a time, 3 three at a time and in
different positions in the 3 available slots.
Lots of reboots and those error messages in the process of elimination but
finally got it straightened out.
Have re-booted and re-started from OFF a number of times with no problem.
Not sure if the lame RAM card is the original or not. Lost track of who's on
first and what's on second.

While nosing around I found 'Motherboard resources Properties' (in MSConfig
I think) that showed Memory Range as
00EFE000 - 00EFFFFF. Yikes! There's those wierd characters again like in the
memory error message, Yikes! The motherboard?
Fear and trembling ensued. But for just a short while. Found lots of similar
character strings in numerous memory summeries in a 12 page 'System Resource
Report' I'd printed a few years back for this old Dell Optiplex Gx1p.
Guess it is just standard terminology for memory usage or locations or some
such thing.

Anyhow -
The Ram tests and manufacturer's HD test have all passed.
Boots and re-boots are good.
No problems found with ScanDisk (standard) om small main HD and large
storage HD.
A 'Thorough' ScanDisk on both does the 10 restarts in Normal and Safe Mode.
Have DeFragged the small main HD but the large one takes nearly half a day
to get half way done.
Hope its safe to have paused and quit before its done.
Will put AVG back into the Start-Up routine.

Thanks again to BOTH of yous guys for your time and patience.

"PCR" <pcrrcp@netzero.net> wrote in message
news:uSZnYt0gIHA.4376@TK2MSFTNGP05.phx.gbl...
> keith wrote:
> | Where did Philo's reply go? No longer in this string.
>
> I see two responses by philo, & I can't remember if there were any more.
> You answered his 1st (3/2/08 9:21 AM), but not his 2nd (3/2/08 7:04 PM).
> WELL, you may have included the answer to his 2nd in your answer to my
> 1st. Anyhow, it was about how to run WinDiag-- which I think you've
> done.
>
> | Data Advisor 5.00
> | Memory test - passed
> | Smart Status test - passed
> | 90 second test - passed
>
> That is good. But does it say how much memory it is testing? Does it go
> through all 3 chips or only two? I don't like what you say below about
> your memory chips! It could be Windows is having a problem, despite
> these chips seem to pass memory tests. Maybe the first thing to do is
> really to pull that extra chip to get rid of the error message! Although
> during boot you get the message "decreasing available memory"-- I can
> think Windows might try to use it anyhow during those failed boots!
>
> | File structure test - "unknown" - Not sure what that means. File
> | structure unknown? Test result unknown?
>
> http://www.ontrackdatarecovery.com/hard-drive-software/dataadvisor.aspx
> Ontrack Data Recovery
> .......Quote...........
> File Structure Test
>
> Reads and verifies the integrity of the File Allocation Tables (FAT) on
> DOS, Windows 3.x, Windows 95, 98, Me, NT*, 2000* and XP*. Checks
> critical boot sectors, reads the Master Boot Record and cross-checks
> partition tables and CMOS.
>
> * Support for FAT formatted partitions only
> .......EOQ..............
>
> That sounds like serious tests. Do you know which partition it is
> referring to? Can it be an NTFS partition or other non-FAT partition
> that DataAdvisor will not recognize? Try the FAQS link at that site, but
> I could not find what "unknown" meant after a 20 minute intensive
> search.
>
> Windows's ScanDisk is meant to correct FAT errors. Defrag may also help.
> But you should make a backup of your boot partition first, just in case
> serious errors are found. You could try...
>
> (a) Boot to DOS. (Hold CTRL as you boot for the Startup Menu, & select
> "Command Prompt Only".)
>
> (b) Scandisk /Checkonly /Surface
>
> This will not fix, but only inform what it intends to fix.
> It will display on screen & get written to "C:\Scandisk.log".
> It may take quite a while to complete.
>
> (c) Scandisk
> Let it fix, if it didn't sound horrible. Otherwise, post what it
> said.
>
> In Dos, you may see "C:\Scandisk.log" this way...
>
> EDIT C:\Scandisk.log
> Alt-F-X (pressed separately) to exit EDIT. (TAB to traverse buttons.)
>
> http://support.microsoft.com/kb/199557
> Command-Line Parameters for the Scandisk Tool
>
> | MAXTOR Power Max 4.23 manufacturer's test (for Quantum drive) - all
> | passed.
>
> The hard drive is good, then. It is the Windows file system that may
> have a problem, (unless this is really a RAM issue after all).
>
> | Start>run>MSInfo32>Software environment>Startup Programs
> |
> | SystemTray Registry (Machine Run) SysTray.Exe
> | ScanRegistry Registry (Machine Run)
> | C:\WINDOWS\scanregw.exe /autorun
> | LoadPowerProfile Registry (Machine Run) Rundll32.exe
> | powrprof.dll,LoadCurrentPwrScheme
>
> Those are fine.
>
> | PCPitStopEraser Registry (Machine Run) C:\Program
> | Files\PCPitstop\Erase\PCPitStopErase.exe /remindme
> | AVG7_CC Registry (Machine Run)
> | C:\PROGRA~1\GRISOFT\AVG7\AVGCC.EXE /STARTUP
> | AVG7_EMC Registry (Machine Run)
> | C:\PROGRA~1\GRISOFT\AVG7\AVGEMC.EXE
> | AVG7_AMSVR Registry (Machine Run)
> | C:\PROGRA~1\GRISOFT\AVG7\AVGAMSVR.EXE
>
> Maybe uncheck the above at...
> "START, Run, MSConfig, Startup tab"
> ...to see whether something has gone wrong with them. But I would at
> first be more inclined to with a ScanDisk/Defrag. If done in Windows
> (instead of DOS), don't let them constantly restart-- post back for a
> cure instead.
>
> | LoadPowerProfile Registry (Machine Service) Rundll32.exe
> | powrprof.dll,LoadCurrentPwrScheme
> | KB891711 Registry (Machine Service)
> | C:\WINDOWS\SYSTEM\KB891711\KB891711.EXE
> | KB918547 Registry (Machine Service)
> | C:\WINDOWS\SYSTEM\KB918547\KB918547.EXE
>
> Those are fine, including the 2nd LoadPowerProfile, presuming you have
> the repaired version of KB891711. But I'm sure you do.
>
> | Ran some test from PCPitStop long ago and still have their site in IE
> | favorites list.
> |
> | Maybe the problem has been staring me in the face at every
> | startup for months on end.
> | Sometime last year a neighbor gave me and plugged in a couple
> | extra 128 memory chips to go with the one original 128.
> | At every startup I get the following message
> | 'Memory write/read failure at 100002020, read 00000000,
> | expecting 00EF00EF. Decreasing available memory.'
> | A short pause and the continues with start up.
> | Always assumed it meant one of the extra chips was bad and ignored
> | it all this time and was just to lazy to pull it/them back out.
> | If there is only one in there the system says 128. With any two or
> | all three in there, the system says only 256. Ergo the bad chip
> | assumption.
>
> Take one out permanently! I don't like that message!
>
> | Still getting these newer ones though: (only one at a time but with
> | different devices)
> | 'While initializing device VDD , windows protection error. Need to
> | restart computer.'
> | Usually VDD or VDK. Ocassionally VPICD. Once or
> | twice with V86MMGR or that 386enhanced thing.
>
> Sounds like a complaint about the video (VDD) & the keyboard (VDK). We
> can investigate these things if the other measures do not suffice.
>
> | Might take a couple of restarts to get to the Normal or Safe Mode
> | option and then a couple of Normal attempts there.
> | Needless to say, I don't turm it off very often.
> | But lots of re-starts lately with the diskette tests and checking the
> | HD manufacturer and those memory chips.
> | And I have gotten a couple of regular, straight thru startups, too.
> | No Win 98 discs on hand here if that is.where the problem lurks.
>
> Well, let's hope it doesn't come to that. But you won't need an
> installation CD, if the .cab's are on the hard drive...
>
> "START button, Find, F/F, Win98*.cab" (That's asterisk-dot-cab.)
>
> If 55 of them show up, the folder that contains them is a copy of the
> Installation CD. Normally, they are in "C:\Windows\Options\Cabs".
>
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:eKLVBtngIHA.4140@TK2MSFTNGP04.phx.gbl...
> |> keith wrote:
> |> | Baught some NEW, UNUSED floppies.
> |> | Downloaded the Windows Memory Diagnostic (mtinst.exe) again and ran
> |> | the test(s).
> |> | Ran the standard suite for 3 passes and the extended suite for 2
> |> | passes. All 'Successful' and no errors found.
> |>
> |> Very good. The RAM is fine.
> |>
> |> | The 'WinDiag / mtinst.exe' confusion was all mine. Wasn't sure what
> |> | to call it so typed the test name AND the file name.
> |>
> |> I see. OK.
> |>
> |> | There's probably an easy way to copy/paste or print the BIOS
> |> | settings but I just wrote them all down
> |> | and put them in the attached Word document.
> |> |
> |> | The large extra HD (for file storage) is the Seagate. The small
> |> | main HD is a Quantum.
> |> | Will try the Quantum/Maxtor links again and maybe the other RAM
> |> | tests.
> |>
> |> Keep us informed. I think something could be wrong either with the
> |> hard drive itself or with the Windows file system. Another
> |> possibility is that there is too much in the Startup Group, going by
> |> your words-- "dangerously low resources". Therefore...
> |>
> |> "START button, Run, MSInfo32, Software Environment, Startup
> |> Programs". Use the Edit menu to copy & post it.
> |>
> |> | Thanks again.
> |>
> |> You are welcome. That BIOS report isn't so huge. It looks fine to me,
> |> (although I don't know what Chassis Intrusion or DAC Snoop is). Auto
> |> is a good setting for the hard drives. I'll post it here, for others
> |> to easily see...
> |>
> |> Pentium II 400 Mhz System memory 15 MB SDRAM
> |> Level 2 Cache 512 KB Integrated Video Memory 8 MB SGRAM
> |>
> |> **********
> |>
> |> Diskette A 1.44 MB
> |> Diskette B Not Installed
> |>
> |> Drives Type CYLS HDS PRE SEC SIZE
> |> Primary
> |> Drive 0 Auto 913 255 -1 63 7509
> |> Drive 1 Auto EIDE Drive 65432
> |> Secondary
> |> Drive 0 Auto CD ROM Drive
> |> Drive 1 Auto CD ROM Drive
> |> **********
> |>
> |> Reserved Memory 15 - 16 M
> |> CPU Speed 400 Mhz
> |> Num Lock On
> |> Chassis Intrusion Disabled
> |> DAC Snoop On
> |> ACPI On
> |>
> |> **********
> |>
> |> Keyboard Errors Report
> |> System Password Not Enabled
> |> Password Status Unlocked
> |> Boot Sequence Diskette First
> |> Setup Password Not Enabled
> |> Auto Power On Disabled 00:00
> |> Power Management Regular
> |> Wake-up on LAN Off
> |>
> |> **********
> |>
> |>
> |> | "PCR" <pcrrcp@netzero.net> wrote in message
> |> | news:uQX2aw%23fIHA.2448@TK2MSFTNGP03.phx.gbl...
> |>
> |> ...snip
> |> |> |> keith wrote:
> |> |> |> | Have seen a few errors at different times lately when
> |> |> |> | booting / rebooting after system lock-ups.
> |> |> |> |
> |> |> |> | 'While initializing device VPICD: Windows
> |> |> |> | protection error.' 'While initializing
> |> |> |> | (installing??) V86MMGR:
> |> |> |> | error cannot
> |> |> |> | install 386 enhanced MXSD'
> |> |> |> | Not sure if it said installing or
> |> |> |> | initializing. Not sure I got the MXSD
> |> |> |> | part correctly - MVXD?
> |> |> |> | or some variation.
> |> |> |> | And one about dangerously low resources.
> |> |> |> |
> |> |> |> | Tried a couple of SCANRE /RESTORE dates from prior to errors
> |> |> |> | but still got the VPICD error on this last boot.
> |> |> |> |
> |> |> |> | W98 with 2 drives - First is just Windows and other programs
> |> |> |> | - only 2 out of 6 gigs used
> |> |> |> | Second is just files, fotos,
> |> |> |> | vids - about 80 out of 95 gigs used.
> |> |> |> | Second has been as
> |> |> |> | high as 90 out of 95 without problems.
> |> |> |> | Its usually in the
> |> |> |> | 70-75 out of 90 range
> |> |> |> |
> |> |> |> | Have start up sequence set to display Normal, Safe Mode,
> |> |> |> | Command Promp Only , etc menu with 30 second wait period.
> |> |> |> | Ocasiionaly Normal doesn't load and it goes back to the
> |> |> |> | menu with Safe Mode hilighted but can usually choose Normal
> |> |> |> | again and complete the start-up.
> |> |> |>
> |> |> |> When an installation boots poorly only occasionally, the
> |> |> |> bootstrap is probably fine. That includes BIOS, MBR (Master
> |> |> |> Boot Record), PBR (Partition Boot Record), & all the files
> |> |> |> needed to boot, even the Registry.
> |> |> |>
> |> |> |> | Nothing out of the ordinary with SpyBot, Ad-Aware,
> |> |> |> | SpyWare Blaster or AVG scans.
> |> |> |> | Nothing new in Add/Remove Programs list or ALT/CTRL/DEL
> |> |> |> | list
> |> |> |> |
> |> |> |> | Thaught I'd post this first while this rig seems to be
> |> |> |> | working OK and will start searching for solutions /
> |> |> |> | references.
> |> |> |>
> |> |> |> (1) Run the RAM test as philo posted.
> |> |> |> (2) Make a backup of your boot partition.
> |> |> |> (It may be on its way out!)
> |> |> |> (3) Run the hard drive diagnostic for your brand.
> |> |> |> This repairs the structure of the hard drive, if
> |> |> |> necessary. (4) Run a ScanDisk & Defrag.
> |> |> |> This repairs the Windows file system, but could also
> |> |> |> wreak havoc, if a big repair is necessary...
> |> |> |> http://cquirke.mvps.org/9x/scandisk.htm
> |> |> |>
> |>
> |> ...snip
> |> --
> |> Thanks or Good Luck,
> |> There may be humor in this post, and,
> |> Naturally, you will not sue,
> |> Should things get worse after this,
> |> PCR
> |> pcrrcp@netzero.net
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> Should things get worse after this,
> PCR
> pcrrcp@netzero.net
>
>

PCR · Mar 14, 2008

keith wrote:
| Didn't see Philo's replies in the thread last time I posted.
| Now I don't see the original post and full thread. Just this shortened
| Re.thread.
| Maybe it will all come back later. OE does get twitchy sometimes.

I still see the whole thread.

(a) Can you have accidentally deleted the 4 posts above my own?
(Pressing the delete key while sitting on one will do that.)

(b) Can it be at...
"OE, View menu, Current View"
that "Show all messages" is not selected?

To recover lost posts...

(a) "R-Clk the NG in OE's left pane, Properties, Synchronize tab"
Ensure "All Messages" is selected. If it wasn't, do so,
& try at first to skip to step (c).

(b) At the "Local File" tab, reset the NG.
This will wipe the NG, & prepare it for new download.

(c) "OE, Tools menu, Synchronize Newsgroup".
This will download 3 months worth, if you have not
skipped step (b). May take a while on Dial-Up.

| Quitr right. My answer to his 2nd was in my answer to your 1st.
| Sorry, Philo. I'd posted that reply at the tail end of the thread. No
| snub intended.
| Will revisit posting tips and etiquette.

I guess your etiquette is fine.

| Seems it was those pesky extra memory cards after all.
| Shuffled them around 1 at a time, 2 at a time, 3 three at a time and
| in different positions in the 3 available slots.
| Lots of reboots and those error messages in the process of
| elimination but finally got it straightened out.
| Have re-booted and re-started from OFF a number of times with no
| problem. Not sure if the lame RAM card is the original or not. Lost
| track of who's on first and what's on second.

Alright, as long as it is working now. If any two of them will work, but
not three-- then it is possible there is a jumper on the MB that must be
moved when the 3rd is added. But I know little about it. Try the
manufacturers WEB site.

| While nosing around I found 'Motherboard resources Properties' (in
| MSConfig I think) that showed Memory Range as
| 00EFE000 - 00EFFFFF. Yikes! There's those wierd characters again like
| in the memory error message, Yikes! The motherboard?
| Fear and trembling ensued. But for just a short while. Found lots of
| similar character strings in numerous memory summeries in a 12 page
| 'System Resource Report' I'd printed a few years back for this old
| Dell Optiplex Gx1p.
| Guess it is just standard terminology for memory usage or locations
| or some such thing.

Those are hexadecimal numbers. Mine look just like that.

| Anyhow -
| The Ram tests and manufacturer's HD test have all passed.
| Boots and re-boots are good.

That says the RAM & the hard drive itself are fine.

| No problems found with ScanDisk (standard) om small main HD and large
| storage HD.
| A 'Thorough' ScanDisk on both does the 10 restarts in Normal and
| Safe Mode.

That is sad-- especially that it happens in Safe Mode! I don't like the
sound of that! Does it seem to run well in DOS?

Most items that could cause the restarts are automatically turned off in
Safe Mode. Check whether any of these are still on...

1. Turn off screen saver (R-Clk Desktop, Properties, Screen Saver--
None).
2. Turn off power management (Control Panel, Power Management--
Always On, Never, Never, Never).
3. Suspend Task Scheduler.
4. Disable any permanent internet cable connection, perhaps.
5. "START button, Run, MSConfig, Startup tab". Note what is
unchecked. Then, go to the General tab & disable the entire
Startup Group, by clicking "Selective.." & unchecking
"Load Startup...". Reboot. Don't forget to re-enable before
the next boot.

To speed up the scan somewhat...

(a) "Control Panel, Internet Options, Delete Files button,
bolt Delete all offline content, OK, OK"
Those are the Temporary Internat Files, which can be huge.

(b) "START button, Run, %TEMP%", & delete all files that will go.
This will likely be "C:\Windows\Temp". This is best done after a
fresh boot, if you have just done an install.

| Have DeFragged the small main HD but the large one takes
| nearly half a day to get half way done.

DON'T DO IT-- if you cannot get it to stop the constant restarts! I
remember 6-hour ScanDisks & Defrags being a precursor to my '01 hard
drive crash!

| Hope its safe to have paused and quit before its done.
| Will put AVG back into the Start-Up routine.
|
| Thanks again to BOTH of yous guys for your time and patience.

You are welcome.

|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:uSZnYt0gIHA.4376@TK2MSFTNGP05.phx.gbl...
|> keith wrote:
|> | Where did Philo's reply go? No longer in this string.
|>
|> I see two responses by philo, & I can't remember if there were any
|> more. You answered his 1st (3/2/08 9:21 AM), but not his 2nd (3/2/08
|> 7:04 PM). WELL, you may have included the answer to his 2nd in your
|> answer to my 1st. Anyhow, it was about how to run WinDiag-- which I
|> think you've done.
|>
|> | Data Advisor 5.00
|> | Memory test - passed
|> | Smart Status test - passed
|> | 90 second test - passed
|>
|> That is good. But does it say how much memory it is testing? Does it
|> go through all 3 chips or only two? I don't like what you say below
|> about your memory chips! It could be Windows is having a problem,
|> despite these chips seem to pass memory tests. Maybe the first thing
|> to do is really to pull that extra chip to get rid of the error
|> message! Although during boot you get the message "decreasing
|> available memory"-- I can think Windows might try to use it anyhow
|> during those failed boots!
|>
|> | File structure test - "unknown" - Not sure what that means. File
|> | structure unknown? Test result unknown?
|>
|>
http://www.ontrackdatarecovery.com/hard-drive-software/dataadvisor.aspx
|> Ontrack Data Recovery
|> .......Quote...........
|> File Structure Test
|>
|> Reads and verifies the integrity of the File Allocation Tables (FAT)
|> on DOS, Windows 3.x, Windows 95, 98, Me, NT*, 2000* and XP*. Checks
|> critical boot sectors, reads the Master Boot Record and cross-checks
|> partition tables and CMOS.
|>
|> * Support for FAT formatted partitions only
|> .......EOQ..............
|>
|> That sounds like serious tests. Do you know which partition it is
|> referring to? Can it be an NTFS partition or other non-FAT partition
|> that DataAdvisor will not recognize? Try the FAQS link at that site,
|> but I could not find what "unknown" meant after a 20 minute intensive
|> search.
|>
|> Windows's ScanDisk is meant to correct FAT errors. Defrag may also
|> help. But you should make a backup of your boot partition first,
|> just in case serious errors are found. You could try...
|>
|> (a) Boot to DOS. (Hold CTRL as you boot for the Startup Menu, &
|> select "Command Prompt Only".)
|>
|> (b) Scandisk /Checkonly /Surface
|>
|> This will not fix, but only inform what it intends to fix.
|> It will display on screen & get written to "C:\Scandisk.log".
|> It may take quite a while to complete.
|>
|> (c) Scandisk
|> Let it fix, if it didn't sound horrible. Otherwise, post what
|> it said.
|>
|> In Dos, you may see "C:\Scandisk.log" this way...
|>
|> EDIT C:\Scandisk.log
|> Alt-F-X (pressed separately) to exit EDIT. (TAB to traverse buttons.)
|>
|> http://support.microsoft.com/kb/199557
|> Command-Line Parameters for the Scandisk Tool
|>
|> | MAXTOR Power Max 4.23 manufacturer's test (for Quantum drive) - all
|> | passed.
|>
|> The hard drive is good, then. It is the Windows file system that may
|> have a problem, (unless this is really a RAM issue after all).
|>
|> | Start>run>MSInfo32>Software environment>Startup Programs
|> |
|> | SystemTray Registry (Machine Run)
|> | SysTray.Exe ScanRegistry Registry (Machine Run)
|> | C:\WINDOWS\scanregw.exe /autorun
|> | LoadPowerProfile Registry (Machine Run) Rundll32.exe
|> | powrprof.dll,LoadCurrentPwrScheme
|>
|> Those are fine.
|>
|> | PCPitStopEraser Registry (Machine Run) C:\Program
|> | Files\PCPitstop\Erase\PCPitStopErase.exe /remindme
|> | AVG7_CC Registry (Machine Run)
|> | C:\PROGRA~1\GRISOFT\AVG7\AVGCC.EXE /STARTUP
|> | AVG7_EMC Registry (Machine Run)
|> | C:\PROGRA~1\GRISOFT\AVG7\AVGEMC.EXE
|> | AVG7_AMSVR Registry (Machine Run)
|> | C:\PROGRA~1\GRISOFT\AVG7\AVGAMSVR.EXE
|>
|> Maybe uncheck the above at...
|> "START, Run, MSConfig, Startup tab"
|> ...to see whether something has gone wrong with them. But I would at
|> first be more inclined to with a ScanDisk/Defrag. If done in Windows
|> (instead of DOS), don't let them constantly restart-- post back for a
|> cure instead.
|>
|> | LoadPowerProfile Registry (Machine Service) Rundll32.exe
|> | powrprof.dll,LoadCurrentPwrScheme
|> | KB891711 Registry (Machine Service)
|> | C:\WINDOWS\SYSTEM\KB891711\KB891711.EXE
|> | KB918547 Registry (Machine Service)
|> | C:\WINDOWS\SYSTEM\KB918547\KB918547.EXE
|>
|> Those are fine, including the 2nd LoadPowerProfile, presuming you
|> have the repaired version of KB891711. But I'm sure you do.
|>
|> | Ran some test from PCPitStop long ago and still have their site in
|> | IE favorites list.
|> |
|> | Maybe the problem has been staring me in the face at every
|> | startup for months on end.
|> | Sometime last year a neighbor gave me and plugged in a couple
|> | extra 128 memory chips to go with the one original 128.
|> | At every startup I get the following message
|> | 'Memory write/read failure at 100002020, read 00000000,
|> | expecting 00EF00EF. Decreasing available memory.'
|> | A short pause and the continues with start up.
|> | Always assumed it meant one of the extra chips was bad and
|> | ignored it all this time and was just to lazy to pull it/them back
|> | out. If there is only one in there the system says 128. With
|> | any two or all three in there, the system says only 256. Ergo the
|> | bad chip assumption.
|>
|> Take one out permanently! I don't like that message!
|>
|> | Still getting these newer ones though: (only one at a time but with
|> | different devices)
|> | 'While initializing device VDD , windows protection error.
|> | Need to restart computer.'
|> | Usually VDD or VDK. Ocassionally VPICD. Once or
|> | twice with V86MMGR or that 386enhanced thing.
|>
|> Sounds like a complaint about the video (VDD) & the keyboard (VDK).
|> We can investigate these things if the other measures do not suffice.
|>
|> | Might take a couple of restarts to get to the Normal or Safe Mode
|> | option and then a couple of Normal attempts there.
|> | Needless to say, I don't turm it off very often.
|> | But lots of re-starts lately with the diskette tests and checking
|> | the HD manufacturer and those memory chips.
|> | And I have gotten a couple of regular, straight thru startups, too.
|> | No Win 98 discs on hand here if that is.where the problem lurks.
|>
|> Well, let's hope it doesn't come to that. But you won't need an
|> installation CD, if the .cab's are on the hard drive...
|>
|> "START button, Find, F/F, Win98*.cab" (That's asterisk-dot-cab.)
|>
|> If 55 of them show up, the folder that contains them is a copy of the
|> Installation CD. Normally, they are in "C:\Windows\Options\Cabs".
|>
|> |
|> | "PCR" <pcrrcp@netzero.net> wrote in message
|> | news:eKLVBtngIHA.4140@TK2MSFTNGP04.phx.gbl...
|> |> keith wrote:
|> |> | Baught some NEW, UNUSED floppies.
|> |> | Downloaded the Windows Memory Diagnostic (mtinst.exe) again and
|> |> | ran the test(s).
|> |> | Ran the standard suite for 3 passes and the extended suite for 2
|> |> | passes. All 'Successful' and no errors found.
|> |>
|> |> Very good. The RAM is fine.
|> |>
|> |> | The 'WinDiag / mtinst.exe' confusion was all mine. Wasn't sure
|> |> | what to call it so typed the test name AND the file name.
|> |>
|> |> I see. OK.
|> |>
|> |> | There's probably an easy way to copy/paste or print the BIOS
|> |> | settings but I just wrote them all down
|> |> | and put them in the attached Word document.
|> |> |
|> |> | The large extra HD (for file storage) is the Seagate. The small
|> |> | main HD is a Quantum.
|> |> | Will try the Quantum/Maxtor links again and maybe the other RAM
|> |> | tests.
|> |>
|> |> Keep us informed. I think something could be wrong either with the
|> |> hard drive itself or with the Windows file system. Another
|> |> possibility is that there is too much in the Startup Group, going
|> |> by your words-- "dangerously low resources". Therefore...
|> |>
|> |> "START button, Run, MSInfo32, Software Environment, Startup
|> |> Programs". Use the Edit menu to copy & post it.
|> |>
|> |> | Thanks again.
|> |>
|> |> You are welcome. That BIOS report isn't so huge. It looks fine to
|> |> me, (although I don't know what Chassis Intrusion or DAC Snoop
|> |> is). Auto is a good setting for the hard drives. I'll post it
|> |> here, for others to easily see...
|> |>
|> |> Pentium II 400 Mhz System memory 15 MB SDRAM
|> |> Level 2 Cache 512 KB Integrated Video Memory 8 MB SGRAM
|> |>
|> |> **********
|> |>
|> |> Diskette A 1.44 MB
|> |> Diskette B Not Installed
|> |>
|> |> Drives Type CYLS HDS PRE SEC SIZE
|> |> Primary
|> |> Drive 0 Auto 913 255 -1 63 7509
|> |> Drive 1 Auto EIDE Drive 65432
|> |> Secondary
|> |> Drive 0 Auto CD ROM Drive
|> |> Drive 1 Auto CD ROM Drive
|> |> **********
|> |>
|> |> Reserved Memory 15 - 16 M
|> |> CPU Speed 400 Mhz
|> |> Num Lock On
|> |> Chassis Intrusion Disabled
|> |> DAC Snoop On
|> |> ACPI On
|> |>
|> |> **********
|> |>
|> |> Keyboard Errors Report
|> |> System Password Not Enabled
|> |> Password Status Unlocked
|> |> Boot Sequence Diskette First
|> |> Setup Password Not Enabled
|> |> Auto Power On Disabled 00:00
|> |> Power Management Regular
|> |> Wake-up on LAN Off
|> |>
|> |> **********
|> |>
|> |>
|> |> | "PCR" <pcrrcp@netzero.net> wrote in message
|> |> | news:uQX2aw%23fIHA.2448@TK2MSFTNGP03.phx.gbl...
|> |>
|> |> ...snip
|> |> |> |> keith wrote:
|> |> |> |> | Have seen a few errors at different times lately when
|> |> |> |> | booting / rebooting after system lock-ups.
|> |> |> |> |
|> |> |> |> | 'While initializing device VPICD: Windows
|> |> |> |> | protection error.' 'While initializing
|> |> |> |> | (installing??) V86MMGR:
|> |> |> |> | error cannot
|> |> |> |> | install 386 enhanced MXSD'
|> |> |> |> | Not sure if it said installing or
|> |> |> |> | initializing. Not sure I got the MXSD
|> |> |> |> | part correctly - MVXD?
|> |> |> |> | or some variation.
|> |> |> |> | And one about dangerously low resources.
|> |> |> |> |
|> |> |> |> | Tried a couple of SCANRE /RESTORE dates from prior to
|> |> |> |> | errors but still got the VPICD error on this last boot.
|> |> |> |> |
|> |> |> |> | W98 with 2 drives - First is just Windows and other
|> |> |> |> | programs - only 2 out of 6 gigs used
|> |> |> |> | Second is just files,
|> |> |> |> | fotos, vids - about 80 out of 95 gigs used.
|> |> |> |> | Second has been
|> |> |> |> | as high as 90 out of 95 without problems.
|> |> |> |> | Its usually in
|> |> |> |> | the 70-75 out of 90 range
|> |> |> |> |
|> |> |> |> | Have start up sequence set to display Normal, Safe
|> |> |> |> | Mode, Command Promp Only , etc menu with 30 second wait
|> |> |> |> | period. Ocasiionaly Normal doesn't load and it goes
|> |> |> |> | back to the
|> |> |> |> | menu with Safe Mode hilighted but can usually choose
|> |> |> |> | Normal again and complete the start-up.
|> |> |> |>
|> |> |> |> When an installation boots poorly only occasionally, the
|> |> |> |> bootstrap is probably fine. That includes BIOS, MBR (Master
|> |> |> |> Boot Record), PBR (Partition Boot Record), & all the files
|> |> |> |> needed to boot, even the Registry.
|> |> |> |>
|> |> |> |> | Nothing out of the ordinary with SpyBot, Ad-Aware,
|> |> |> |> | SpyWare Blaster or AVG scans.
|> |> |> |> | Nothing new in Add/Remove Programs list or
|> |> |> |> | ALT/CTRL/DEL list
|> |> |> |> |
|> |> |> |> | Thaught I'd post this first while this rig seems to be
|> |> |> |> | working OK and will start searching for solutions /
|> |> |> |> | references.
|> |> |> |>
|> |> |> |> (1) Run the RAM test as philo posted.
|> |> |> |> (2) Make a backup of your boot partition.
|> |> |> |> (It may be on its way out!)
|> |> |> |> (3) Run the hard drive diagnostic for your brand.
|> |> |> |> This repairs the structure of the hard drive, if
|> |> |> |> necessary. (4) Run a ScanDisk & Defrag.
|> |> |> |> This repairs the Windows file system, but could also
|> |> |> |> wreak havoc, if a big repair is necessary...
|> |> |> |> http://cquirke.mvps.org/9x/scandisk.htm
|> |> |> |>
|> |>
|> |> ...snip
|> |> --
|> |> Thanks or Good Luck,
|> |> There may be humor in this post, and,
|> |> Naturally, you will not sue,
|> |> Should things get worse after this,
|> |> PCR
|> |> pcrrcp@netzero.net
|>
|> --
|> Thanks or Good Luck,
|> There may be humor in this post, and,
|> Naturally, you will not sue,
|> Should things get worse after this,
|> PCR
|> pcrrcp@netzero.net

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

Franc Zabkar · Mar 17, 2008

On Mon, 10 Mar 2008 12:05:47 -0400, "keith" <uncle@tanoose.nut> put
finger to keyboard and composed:

> At every startup I get the following message
> 'Memory write/read failure at 100002020, read 00000000, expecting
>00EF00EF. Decreasing available memory.'

Address 0x100000000 is equivalent to 256M decimal, so your memory
error occurs very early in the address space of your third 128MB
memory module. The difference between the read and expected data
suggests that the problem is not with the individual RAM chips
(because more than one chip appears to be involved), instead I'm
guessing that there is some kind if addressing fault. I'd check for
damaged pins in the DIMM socket. At the very least you should swap the
"faulty" module with one of the others to confirm whether it is indeed
faulty.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

keith · Apr 1, 2008

Philo is back after the 'To recover lost posts' suggestions. Thanks.
Got the three months worth re-downloaded.
Will OE keep adding to the three months or add new posts and cut older posts
to maintain just three months worth?

And I'm back, too, after some lengthy service provider issues.
Won't name names as that would CAST asspersions on the provider COMpany's
name.

Last 'Scan' and 'Defrag' in Safe Mode was quick enough on the small HD with
the programs, OS, etc.
The larger 100 gig HD still scans and defrags in slow motion in Safe Mode.
No repeats, just slow.
If I run defrag again at a later time it seems like it runs pretty quick up
to where it left off the last time and then slows down again.
May try one more over-nighter to see if it'll finish.
I never use a screen saver - I just turn off the monitor.
Power manageent was set to 'Always on' and Never, Never.
Changed it to 'Home/desktop' and Never, Never.
History, cookies, and temp files (including off-line content) are
cleared every day and sometimes twice a day.

Started this thread with the start-up errors and that has been solved.
Wondering if I should continue here with this scan and defrag issue or make
this issue a new post.

Thanks again.

"PCR" <pcrrcp@netzero.net> wrote in message
news:%23aUYkRjhIHA.2268@TK2MSFTNGP02.phx.gbl...
> keith wrote:
> | Didn't see Philo's replies in the thread last time I posted.
> | Now I don't see the original post and full thread. Just this shortened
> | Re.thread.
> | Maybe it will all come back later. OE does get twitchy sometimes.
>
> I still see the whole thread.
>
> (a) Can you have accidentally deleted the 4 posts above my own?
> (Pressing the delete key while sitting on one will do that.)
>
> (b) Can it be at...
> "OE, View menu, Current View"
> that "Show all messages" is not selected?
>
> To recover lost posts...
>
> (a) "R-Clk the NG in OE's left pane, Properties, Synchronize tab"
> Ensure "All Messages" is selected. If it wasn't, do so,
> & try at first to skip to step (c).
>
> (b) At the "Local File" tab, reset the NG.
> This will wipe the NG, & prepare it for new download.
>
> (c) "OE, Tools menu, Synchronize Newsgroup".
> This will download 3 months worth, if you have not
> skipped step (b). May take a while on Dial-Up.
>
> | Quitr right. My answer to his 2nd was in my answer to your 1st.
> | Sorry, Philo. I'd posted that reply at the tail end of the thread. No
> | snub intended.
> | Will revisit posting tips and etiquette.
>
> I guess your etiquette is fine.
>
> | Seems it was those pesky extra memory cards after all.
> | Shuffled them around 1 at a time, 2 at a time, 3 three at a time and
> | in different positions in the 3 available slots.
> | Lots of reboots and those error messages in the process of
> | elimination but finally got it straightened out.
> | Have re-booted and re-started from OFF a number of times with no
> | problem. Not sure if the lame RAM card is the original or not. Lost
> | track of who's on first and what's on second.
>
> Alright, as long as it is working now. If any two of them will work, but
> not three-- then it is possible there is a jumper on the MB that must be
> moved when the 3rd is added. But I know little about it. Try the
> manufacturers WEB site.
>
> | While nosing around I found 'Motherboard resources Properties' (in
> | MSConfig I think) that showed Memory Range as
> | 00EFE000 - 00EFFFFF. Yikes! There's those wierd characters again like
> | in the memory error message, Yikes! The motherboard?
> | Fear and trembling ensued. But for just a short while. Found lots of
> | similar character strings in numerous memory summeries in a 12 page
> | 'System Resource Report' I'd printed a few years back for this old
> | Dell Optiplex Gx1p.
> | Guess it is just standard terminology for memory usage or locations
> | or some such thing.
>
> Those are hexadecimal numbers. Mine look just like that.
>
> | Anyhow -
> | The Ram tests and manufacturer's HD test have all passed.
> | Boots and re-boots are good.
>
> That says the RAM & the hard drive itself are fine.
>
> | No problems found with ScanDisk (standard) om small main HD and large
> | storage HD.
> | A 'Thorough' ScanDisk on both does the 10 restarts in Normal and
> | Safe Mode.
>
> That is sad-- especially that it happens in Safe Mode! I don't like the
> sound of that! Does it seem to run well in DOS?
>
> Most items that could cause the restarts are automatically turned off in
> Safe Mode. Check whether any of these are still on...
>
> 1. Turn off screen saver (R-Clk Desktop, Properties, Screen Saver--
> None).
> 2. Turn off power management (Control Panel, Power Management--
> Always On, Never, Never, Never).
> 3. Suspend Task Scheduler.
> 4. Disable any permanent internet cable connection, perhaps.
> 5. "START button, Run, MSConfig, Startup tab". Note what is
> unchecked. Then, go to the General tab & disable the entire
> Startup Group, by clicking "Selective.." & unchecking
> "Load Startup...". Reboot. Don't forget to re-enable before
> the next boot.
>
> To speed up the scan somewhat...
>
> (a) "Control Panel, Internet Options, Delete Files button,
> bolt Delete all offline content, OK, OK"
> Those are the Temporary Internat Files, which can be huge.
>
> (b) "START button, Run, %TEMP%", & delete all files that will go.
> This will likely be "C:\Windows\Temp". This is best done after a
> fresh boot, if you have just done an install.
>
> | Have DeFragged the small main HD but the large one takes
> | nearly half a day to get half way done.
>
> DON'T DO IT-- if you cannot get it to stop the constant restarts! I
> remember 6-hour ScanDisks & Defrags being a precursor to my '01 hard
> drive crash!
>
> | Hope its safe to have paused and quit before its done.
> | Will put AVG back into the Start-Up routine.
> |
> | Thanks again to BOTH of yous guys for your time and patience.
>
> You are welcome.
>
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:uSZnYt0gIHA.4376@TK2MSFTNGP05.phx.gbl...
> |> keith wrote:
> |> | Where did Philo's reply go? No longer in this string.
> |>
> |> I see two responses by philo, & I can't remember if there were any
> |> more. You answered his 1st (3/2/08 9:21 AM), but not his 2nd (3/2/08
> |> 7:04 PM). WELL, you may have included the answer to his 2nd in your
> |> answer to my 1st. Anyhow, it was about how to run WinDiag-- which I
> |> think you've done.
> |>
> |> | Data Advisor 5.00
> |> | Memory test - passed
> |> | Smart Status test - passed
> |> | 90 second test - passed
> |>
> |> That is good. But does it say how much memory it is testing? Does it
> |> go through all 3 chips or only two? I don't like what you say below
> |> about your memory chips! It could be Windows is having a problem,
> |> despite these chips seem to pass memory tests. Maybe the first thing
> |> to do is really to pull that extra chip to get rid of the error
> |> message! Although during boot you get the message "decreasing
> |> available memory"-- I can think Windows might try to use it anyhow
> |> during those failed boots!
> |>
> |> | File structure test - "unknown" - Not sure what that means. File
> |> | structure unknown? Test result unknown?
> |>
> |>
> http://www.ontrackdatarecovery.com/hard-drive-software/dataadvisor.aspx
> |> Ontrack Data Recovery
> |> .......Quote...........
> |> File Structure Test
> |>
> |> Reads and verifies the integrity of the File Allocation Tables (FAT)
> |> on DOS, Windows 3.x, Windows 95, 98, Me, NT*, 2000* and XP*. Checks
> |> critical boot sectors, reads the Master Boot Record and cross-checks
> |> partition tables and CMOS.
> |>
> |> * Support for FAT formatted partitions only
> |> .......EOQ..............
> |>
> |> That sounds like serious tests. Do you know which partition it is
> |> referring to? Can it be an NTFS partition or other non-FAT partition
> |> that DataAdvisor will not recognize? Try the FAQS link at that site,
> |> but I could not find what "unknown" meant after a 20 minute intensive
> |> search.
> |>
> |> Windows's ScanDisk is meant to correct FAT errors. Defrag may also
> |> help. But you should make a backup of your boot partition first,
> |> just in case serious errors are found. You could try...
> |>
> |> (a) Boot to DOS. (Hold CTRL as you boot for the Startup Menu, &
> |> select "Command Prompt Only".)
> |>
> |> (b) Scandisk /Checkonly /Surface
> |>
> |> This will not fix, but only inform what it intends to fix.
> |> It will display on screen & get written to "C:\Scandisk.log".
> |> It may take quite a while to complete.
> |>
> |> (c) Scandisk
> |> Let it fix, if it didn't sound horrible. Otherwise, post what
> |> it said.
> |>
> |> In Dos, you may see "C:\Scandisk.log" this way...
> |>
> |> EDIT C:\Scandisk.log
> |> Alt-F-X (pressed separately) to exit EDIT. (TAB to traverse buttons.)
> |>
> |> http://support.microsoft.com/kb/199557
> |> Command-Line Parameters for the Scandisk Tool
> |>
> |> | MAXTOR Power Max 4.23 manufacturer's test (for Quantum drive) - all
> |> | passed.
> |>
> |> The hard drive is good, then. It is the Windows file system that may
> |> have a problem, (unless this is really a RAM issue after all).
> |>
> |> | Start>run>MSInfo32>Software environment>Startup Programs
> |> |
> |> | SystemTray Registry (Machine Run)
> |> | SysTray.Exe ScanRegistry Registry (Machine Run)
> |> | C:\WINDOWS\scanregw.exe /autorun
> |> | LoadPowerProfile Registry (Machine Run) Rundll32.exe
> |> | powrprof.dll,LoadCurrentPwrScheme
> |>
> |> Those are fine.
> |>
> |> | PCPitStopEraser Registry (Machine Run) C:\Program
> |> | Files\PCPitstop\Erase\PCPitStopErase.exe /remindme
> |> | AVG7_CC Registry (Machine Run)
> |> | C:\PROGRA~1\GRISOFT\AVG7\AVGCC.EXE /STARTUP
> |> | AVG7_EMC Registry (Machine Run)
> |> | C:\PROGRA~1\GRISOFT\AVG7\AVGEMC.EXE
> |> | AVG7_AMSVR Registry (Machine Run)
> |> | C:\PROGRA~1\GRISOFT\AVG7\AVGAMSVR.EXE
> |>
> |> Maybe uncheck the above at...
> |> "START, Run, MSConfig, Startup tab"
> |> ...to see whether something has gone wrong with them. But I would at
> |> first be more inclined to with a ScanDisk/Defrag. If done in Windows
> |> (instead of DOS), don't let them constantly restart-- post back for a
> |> cure instead.
> |>
> |> | LoadPowerProfile Registry (Machine Service) Rundll32.exe
> |> | powrprof.dll,LoadCurrentPwrScheme
> |> | KB891711 Registry (Machine Service)
> |> | C:\WINDOWS\SYSTEM\KB891711\KB891711.EXE
> |> | KB918547 Registry (Machine Service)
> |> | C:\WINDOWS\SYSTEM\KB918547\KB918547.EXE
> |>
> |> Those are fine, including the 2nd LoadPowerProfile, presuming you
> |> have the repaired version of KB891711. But I'm sure you do.
> |>
> |> | Ran some test from PCPitStop long ago and still have their site in
> |> | IE favorites list.
> |> |
> |> | Maybe the problem has been staring me in the face at every
> |> | startup for months on end.
> |> | Sometime last year a neighbor gave me and plugged in a couple
> |> | extra 128 memory chips to go with the one original 128.
> |> | At every startup I get the following message
> |> | 'Memory write/read failure at 100002020, read 00000000,
> |> | expecting 00EF00EF. Decreasing available memory.'
> |> | A short pause and the continues with start up.
> |> | Always assumed it meant one of the extra chips was bad and
> |> | ignored it all this time and was just to lazy to pull it/them back
> |> | out. If there is only one in there the system says 128. With
> |> | any two or all three in there, the system says only 256. Ergo the
> |> | bad chip assumption.
> |>
> |> Take one out permanently! I don't like that message!
> |>
> |> | Still getting these newer ones though: (only one at a time but with
> |> | different devices)
> |> | 'While initializing device VDD , windows protection error.
> |> | Need to restart computer.'
> |> | Usually VDD or VDK. Ocassionally VPICD. Once or
> |> | twice with V86MMGR or that 386enhanced thing.
> |>
> |> Sounds like a complaint about the video (VDD) & the keyboard (VDK).
> |> We can investigate these things if the other measures do not suffice.
> |>
> |> | Might take a couple of restarts to get to the Normal or Safe Mode
> |> | option and then a couple of Normal attempts there.
> |> | Needless to say, I don't turm it off very often.
> |> | But lots of re-starts lately with the diskette tests and checking
> |> | the HD manufacturer and those memory chips.
> |> | And I have gotten a couple of regular, straight thru startups, too.
> |> | No Win 98 discs on hand here if that is.where the problem lurks.
> |>
> |> Well, let's hope it doesn't come to that. But you won't need an
> |> installation CD, if the .cab's are on the hard drive...
> |>
> |> "START button, Find, F/F, Win98*.cab" (That's asterisk-dot-cab.)
> |>
> |> If 55 of them show up, the folder that contains them is a copy of the
> |> Installation CD. Normally, they are in "C:\Windows\Options\Cabs".
> |>
> |> |
> |> | "PCR" <pcrrcp@netzero.net> wrote in message
> |> | news:eKLVBtngIHA.4140@TK2MSFTNGP04.phx.gbl...
> |> |> keith wrote:
> |> |> | Baught some NEW, UNUSED floppies.
> |> |> | Downloaded the Windows Memory Diagnostic (mtinst.exe) again and
> |> |> | ran the test(s).
> |> |> | Ran the standard suite for 3 passes and the extended suite for 2
> |> |> | passes. All 'Successful' and no errors found.
> |> |>
> |> |> Very good. The RAM is fine.
> |> |>
> |> |> | The 'WinDiag / mtinst.exe' confusion was all mine. Wasn't sure
> |> |> | what to call it so typed the test name AND the file name.
> |> |>
> |> |> I see. OK.
> |> |>
> |> |> | There's probably an easy way to copy/paste or print the BIOS
> |> |> | settings but I just wrote them all down
> |> |> | and put them in the attached Word document.
> |> |> |
> |> |> | The large extra HD (for file storage) is the Seagate. The small
> |> |> | main HD is a Quantum.
> |> |> | Will try the Quantum/Maxtor links again and maybe the other RAM
> |> |> | tests.
> |> |>
> |> |> Keep us informed. I think something could be wrong either with the
> |> |> hard drive itself or with the Windows file system. Another
> |> |> possibility is that there is too much in the Startup Group, going
> |> |> by your words-- "dangerously low resources". Therefore...
> |> |>
> |> |> "START button, Run, MSInfo32, Software Environment, Startup
> |> |> Programs". Use the Edit menu to copy & post it.
> |> |>
> |> |> | Thanks again.
> |> |>
> |> |> You are welcome. That BIOS report isn't so huge. It looks fine to
> |> |> me, (although I don't know what Chassis Intrusion or DAC Snoop
> |> |> is). Auto is a good setting for the hard drives. I'll post it
> |> |> here, for others to easily see...
> |> |>
> |> |> Pentium II 400 Mhz System memory 15 MB SDRAM
> |> |> Level 2 Cache 512 KB Integrated Video Memory 8 MB SGRAM
> |> |>
> |> |> **********
> |> |>
> |> |> Diskette A 1.44 MB
> |> |> Diskette B Not Installed
> |> |>
> |> |> Drives Type CYLS HDS PRE SEC SIZE
> |> |> Primary
> |> |> Drive 0 Auto 913 255 -1 63 7509
> |> |> Drive 1 Auto EIDE Drive 65432
> |> |> Secondary
> |> |> Drive 0 Auto CD ROM Drive
> |> |> Drive 1 Auto CD ROM Drive
> |> |> **********
> |> |>
> |> |> Reserved Memory 15 - 16 M
> |> |> CPU Speed 400 Mhz
> |> |> Num Lock On
> |> |> Chassis Intrusion Disabled
> |> |> DAC Snoop On
> |> |> ACPI On
> |> |>
> |> |> **********
> |> |>
> |> |> Keyboard Errors Report
> |> |> System Password Not Enabled
> |> |> Password Status Unlocked
> |> |> Boot Sequence Diskette First
> |> |> Setup Password Not Enabled
> |> |> Auto Power On Disabled 00:00
> |> |> Power Management Regular
> |> |> Wake-up on LAN Off
> |> |>
> |> |> **********
> |> |>
> |> |>
> |> |> | "PCR" <pcrrcp@netzero.net> wrote in message
> |> |> | news:uQX2aw%23fIHA.2448@TK2MSFTNGP03.phx.gbl...
> |> |>
> |> |> ...snip
> |> |> |> |> keith wrote:
> |> |> |> |> | Have seen a few errors at different times lately when
> |> |> |> |> | booting / rebooting after system lock-ups.
> |> |> |> |> |
> |> |> |> |> | 'While initializing device VPICD: Windows
> |> |> |> |> | protection error.' 'While initializing
> |> |> |> |> | (installing??) V86MMGR:
> |> |> |> |> | error cannot
> |> |> |> |> | install 386 enhanced MXSD'
> |> |> |> |> | Not sure if it said installing or
> |> |> |> |> | initializing. Not sure I got the MXSD
> |> |> |> |> | part correctly - MVXD?
> |> |> |> |> | or some variation.
> |> |> |> |> | And one about dangerously low resources.
> |> |> |> |> |
> |> |> |> |> | Tried a couple of SCANRE /RESTORE dates from prior to
> |> |> |> |> | errors but still got the VPICD error on this last boot.
> |> |> |> |> |
> |> |> |> |> | W98 with 2 drives - First is just Windows and other
> |> |> |> |> | programs - only 2 out of 6 gigs used
> |> |> |> |> | Second is just files,
> |> |> |> |> | fotos, vids - about 80 out of 95 gigs used.
> |> |> |> |> | Second has been
> |> |> |> |> | as high as 90 out of 95 without problems.
> |> |> |> |> | Its usually in
> |> |> |> |> | the 70-75 out of 90 range
> |> |> |> |> |
> |> |> |> |> | Have start up sequence set to display Normal, Safe
> |> |> |> |> | Mode, Command Promp Only , etc menu with 30 second wait
> |> |> |> |> | period. Ocasiionaly Normal doesn't load and it goes
> |> |> |> |> | back to the
> |> |> |> |> | menu with Safe Mode hilighted but can usually choose
> |> |> |> |> | Normal again and complete the start-up.
> |> |> |> |>
> |> |> |> |> When an installation boots poorly only occasionally, the
> |> |> |> |> bootstrap is probably fine. That includes BIOS, MBR (Master
> |> |> |> |> Boot Record), PBR (Partition Boot Record), & all the files
> |> |> |> |> needed to boot, even the Registry.
> |> |> |> |>
> |> |> |> |> | Nothing out of the ordinary with SpyBot, Ad-Aware,
> |> |> |> |> | SpyWare Blaster or AVG scans.
> |> |> |> |> | Nothing new in Add/Remove Programs list or
> |> |> |> |> | ALT/CTRL/DEL list
> |> |> |> |> |
> |> |> |> |> | Thaught I'd post this first while this rig seems to be
> |> |> |> |> | working OK and will start searching for solutions /
> |> |> |> |> | references.
> |> |> |> |>
> |> |> |> |> (1) Run the RAM test as philo posted.
> |> |> |> |> (2) Make a backup of your boot partition.
> |> |> |> |> (It may be on its way out!)
> |> |> |> |> (3) Run the hard drive diagnostic for your brand.
> |> |> |> |> This repairs the structure of the hard drive, if
> |> |> |> |> necessary. (4) Run a ScanDisk & Defrag.
> |> |> |> |> This repairs the Windows file system, but could also
> |> |> |> |> wreak havoc, if a big repair is necessary...
> |> |> |> |> http://cquirke.mvps.org/9x/scandisk.htm
> |> |> |> |>
> |> |>
> |> |> ...snip
> |> |> --
> |> |> Thanks or Good Luck,
> |> |> There may be humor in this post, and,
> |> |> Naturally, you will not sue,
> |> |> Should things get worse after this,
> |> |> PCR
> |> |> pcrrcp@netzero.net
> |>
> |> --
> |> Thanks or Good Luck,
> |> There may be humor in this post, and,
> |> Naturally, you will not sue,
> |> Should things get worse after this,
> |> PCR
> |> pcrrcp@netzero.net
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> Should things get worse after this,
> PCR
> pcrrcp@netzero.net
>
>

keith · Apr 1, 2008

Thanks.
Wasn't really paying attention to which socket(s) the moduals were in, just
which combination of moduals were in.
Will try moving them around agan.
"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
news:v6vrt3lqc9det76o06nppa1mrgesp07bet@4ax.com...
> On Mon, 10 Mar 2008 12:05:47 -0400, "keith" <uncle@tanoose.nut> put
> finger to keyboard and composed:
>
> > At every startup I get the following message
> > 'Memory write/read failure at 100002020, read 00000000, expecting
> >00EF00EF. Decreasing available memory.'
>
> Address 0x100000000 is equivalent to 256M decimal, so your memory
> error occurs very early in the address space of your third 128MB
> memory module. The difference between the read and expected data
> suggests that the problem is not with the individual RAM chips
> (because more than one chip appears to be involved), instead I'm
> guessing that there is some kind if addressing fault. I'd check for
> damaged pins in the DIMM socket. At the very least you should swap the
> "faulty" module with one of the others to confirm whether it is indeed
> faulty.
>
> - Franc Zabkar
> --
> Please remove one 'i' from my address when replying by email.

PCR · Apr 1, 2008

keith wrote:
| Philo is back after the 'To recover lost posts' suggestions. Thanks.
| Got the three months worth re-downloaded.

Very good. Now/then things can get discoordinated between a .dbx & the
server, I guess. And that may be so whether or not one connects directly
to the MS server that produces this newsgroup. In a recent thread I've
seen someone replying to someone who's post I couldn't see, myself. But
that can also happen through multipost shenanigans so, I won't go &
reset this NG just yet.

| Will OE keep adding to the three months or add new posts and cut
| older posts to maintain just three months worth?

I believe 3 months is the figure that MS will maintain at the server--
well, if that's what you got after the reset-- then, yea, that is it at
the server. As far as OE, it will keep whatever you read into your OE
Store until you delete them. That store is shown at...
"R-Clk NG in OE left-pane, Properties, General tab"
.... Mine shows...
G:\Outlook Express Store\microsoft.public.win98.gen_discussion.dbx
.... But its location can be changed at...
"OE, Tools menu, Options, Maintenence tab, Store Folder button".

I have set up a message rule to delete anything older than 90 days from
my store. The rule must be manually run. But sometimes I regret seeing
them go! Messages can also be deleted individually by highlighting a
group of them & pressing delete. And you know they can be deleted in
that Properties requestor.

| And I'm back, too, after some lengthy service provider issues.
| Won't name names as that would CAST asspersions on the provider
| COMpany's name.

Alright. I have a friend who recently switched to Verizon DSL. He was
having big problems maintaining a connection but claims it is fixed now
after at least a month. Yesterday, they replaced phone wires coming into
the building! Time will tell. It certainly is real speedy when
functioning & makes me a tad envious, but my phone & Netzero bills add
up to about half of his single one.

| Last 'Scan' and 'Defrag' in Safe Mode was quick enough on the small
| HD with the programs, OS, etc.
| The larger 100 gig HD still scans and defrags in slow motion in Safe
| Mode. No repeats, just slow.

That's fine, then-- so long as you don't get the interminable restarts!
Sure, 100 GB would be slow.

| If I run defrag again at a later time it seems like it runs pretty
| quick up to where it left off the last time and then slows down again.

Right. Defrag will be quick if the interval between running is not huge.

| May try one more over-nighter to see if it'll finish.

Yea. Get it done.

| I never use a screen saver - I just turn off the monitor.

OK, that is fine.

| Power manageent was set to 'Always on' and Never, Never.
| Changed it to 'Home/desktop' and Never, Never.

Don't you have a 3rd Never? I've got one for System Standby, Turn Off
Monitor, & Turn Off Hard Disks.

If Power Management does not interfere with your Scandisk/Defrag, I
guess it is pecfectly OK to use it as you do. I shut mine off in the
process of investigating my own constant restarts & never turned it back
on because the Standby button on my keyboard continued to work. But
Power Management wasn't my problem. I think that was either/all of
McAfee suddenly doing it or it was the MS Update Notifier or Wavetop...

http://www.pcmag.com/ 's CrackUp (Gregory A. Wolking & Bob Flanders),
DiskAction (Rick Knoblaugh), & BHOCop (Patrick Philippot) were helpful
to me.

"DiskAction" reports the last 12 processes that access any partition. It
discovered the Microsoft Windows Critical Update Notification tool was
accessing my HDD every five minutes! It can be uninstalled in "Control
Panel, Add/Remove Programs". Then, occasionally, "START, Windows Update"
on your own well-- it may be late for that now.

"BHOCop" found a Browser Helper Object called Wavehelper Class, created
by "Wavetop", that was building a monstrosity of an error log called
"Logit.txt" in here. "START, Find, F/F, Logit.txt"-- see one? Mine is
gone now!

| History, cookies, and temp files (including off-line content) are
| cleared every day and sometimes twice a day.

That should give Scandisk/Defrag a lot less work!

| Started this thread with the start-up errors and that has been solved.
| Wondering if I should continue here with this scan and defrag issue
| or make this issue a new post.

Start here. If it dries up, do a new one.

| Thanks again.

You are welcome.

| "PCR" <pcrrcp@netzero.net> wrote in message
| news:%23aUYkRjhIHA.2268@TK2MSFTNGP02.phx.gbl...
|> keith wrote:
|> | Didn't see Philo's replies in the thread last time I posted.
|> | Now I don't see the original post and full thread. Just this
|> | shortened Re.thread.
|> | Maybe it will all come back later. OE does get twitchy sometimes.
|>
|> I still see the whole thread.
|>
|> (a) Can you have accidentally deleted the 4 posts above my own?
|> (Pressing the delete key while sitting on one will do that.)
|>
|> (b) Can it be at...
|> "OE, View menu, Current View"
|> that "Show all messages" is not selected?
|>
|> To recover lost posts...
|>
|> (a) "R-Clk the NG in OE's left pane, Properties, Synchronize tab"
|> Ensure "All Messages" is selected. If it wasn't, do so,
|> & try at first to skip to step (c).
|>
|> (b) At the "Local File" tab, reset the NG.
|> This will wipe the NG, & prepare it for new download.
|>
|> (c) "OE, Tools menu, Synchronize Newsgroup".
|> This will download 3 months worth, if you have not
|> skipped step (b). May take a while on Dial-Up.
|>
|> | Quitr right. My answer to his 2nd was in my answer to your 1st.
|> | Sorry, Philo. I'd posted that reply at the tail end of the thread.
|> | No snub intended.
|> | Will revisit posting tips and etiquette.
|>
|> I guess your etiquette is fine.
|>
|> | Seems it was those pesky extra memory cards after all.
|> | Shuffled them around 1 at a time, 2 at a time, 3 three at a time
|> | and in different positions in the 3 available slots.
|> | Lots of reboots and those error messages in the process of
|> | elimination but finally got it straightened out.
|> | Have re-booted and re-started from OFF a number of times with no
|> | problem. Not sure if the lame RAM card is the original or not. Lost
|> | track of who's on first and what's on second.
|>
|> Alright, as long as it is working now. If any two of them will work,
|> but not three-- then it is possible there is a jumper on the MB that
|> must be moved when the 3rd is added. But I know little about it. Try
|> the manufacturers WEB site.
|>
|> | While nosing around I found 'Motherboard resources Properties' (in
|> | MSConfig I think) that showed Memory Range as
|> | 00EFE000 - 00EFFFFF. Yikes! There's those wierd characters again
|> | like in the memory error message, Yikes! The motherboard?
|> | Fear and trembling ensued. But for just a short while. Found lots
|> | of similar character strings in numerous memory summeries in a 12
|> | page 'System Resource Report' I'd printed a few years back for
|> | this old Dell Optiplex Gx1p.
|> | Guess it is just standard terminology for memory usage or locations
|> | or some such thing.
|>
|> Those are hexadecimal numbers. Mine look just like that.
|>
|> | Anyhow -
|> | The Ram tests and manufacturer's HD test have all passed.
|> | Boots and re-boots are good.
|>
|> That says the RAM & the hard drive itself are fine.
|>
|> | No problems found with ScanDisk (standard) om small main HD and
|> | large storage HD.
|> | A 'Thorough' ScanDisk on both does the 10 restarts in Normal and
|> | Safe Mode.
|>
|> That is sad-- especially that it happens in Safe Mode! I don't like
|> the sound of that! Does it seem to run well in DOS?
|>
|> Most items that could cause the restarts are automatically turned
|> off in Safe Mode. Check whether any of these are still on...
|>
|> 1. Turn off screen saver (R-Clk Desktop, Properties, Screen Saver--
|> None).
|> 2. Turn off power management (Control Panel, Power Management--
|> Always On, Never, Never, Never).
|> 3. Suspend Task Scheduler.
|> 4. Disable any permanent internet cable connection, perhaps.
|> 5. "START button, Run, MSConfig, Startup tab". Note what is
|> unchecked. Then, go to the General tab & disable the entire
|> Startup Group, by clicking "Selective.." & unchecking
|> "Load Startup...". Reboot. Don't forget to re-enable before
|> the next boot.
|>
|> To speed up the scan somewhat...
|>
|> (a) "Control Panel, Internet Options, Delete Files button,
|> bolt Delete all offline content, OK, OK"
|> Those are the Temporary Internat Files, which can be huge.
|>
|> (b) "START button, Run, %TEMP%", & delete all files that will go.
|> This will likely be "C:\Windows\Temp". This is best done
|> after a fresh boot, if you have just done an install.
|>
|> | Have DeFragged the small main HD but the large one takes
|> | nearly half a day to get half way done.
|>
|> DON'T DO IT-- if you cannot get it to stop the constant restarts! I
|> remember 6-hour ScanDisks & Defrags being a precursor to my '01 hard
|> drive crash!
|>
|> | Hope its safe to have paused and quit before its done.
|> | Will put AVG back into the Start-Up routine.
|> |
|> | Thanks again to BOTH of yous guys for your time and patience.
|>
|> You are welcome.
|>
|> |
|> | "PCR" <pcrrcp@netzero.net> wrote in message
|> | news:uSZnYt0gIHA.4376@TK2MSFTNGP05.phx.gbl...
|> |> keith wrote:
|> |> | Where did Philo's reply go? No longer in this string.
|> |>
|> |> I see two responses by philo, & I can't remember if there were any
|> |> more. You answered his 1st (3/2/08 9:21 AM), but not his 2nd
|> |> (3/2/08 7:04 PM). WELL, you may have included the answer to his
|> |> 2nd in your answer to my 1st. Anyhow, it was about how to run
|> |> WinDiag-- which I think you've done.
|> |>
|> |> | Data Advisor 5.00
|> |> | Memory test - passed
|> |> | Smart Status test - passed
|> |> | 90 second test - passed
|> |>
|> |> That is good. But does it say how much memory it is testing? Does
|> |> it go through all 3 chips or only two? I don't like what you say
|> |> below about your memory chips! It could be Windows is having a
|> |> problem, despite these chips seem to pass memory tests. Maybe the
|> |> first thing to do is really to pull that extra chip to get rid of
|> |> the error message! Although during boot you get the message
|> |> "decreasing available memory"-- I can think Windows might try to
|> |> use it anyhow during those failed boots!
|> |>
|> |> | File structure test - "unknown" - Not sure what that means.
|> |> | File structure unknown? Test result unknown?
|> |>
|> |>
|>
http://www.ontrackdatarecovery.com/hard-drive-software/dataadvisor.aspx
|> |> Ontrack Data Recovery
|> |> .......Quote...........
|> |> File Structure Test
|> |>
|> |> Reads and verifies the integrity of the File Allocation Tables
|> |> (FAT) on DOS, Windows 3.x, Windows 95, 98, Me, NT*, 2000* and
|> |> XP*. Checks critical boot sectors, reads the Master Boot Record
|> |> and cross-checks partition tables and CMOS.
|> |>
|> |> * Support for FAT formatted partitions only
|> |> .......EOQ..............
|> |>
|> |> That sounds like serious tests. Do you know which partition it is
|> |> referring to? Can it be an NTFS partition or other non-FAT
|> |> partition that DataAdvisor will not recognize? Try the FAQS link
|> |> at that site, but I could not find what "unknown" meant after a
|> |> 20 minute intensive search.
|> |>
|> |> Windows's ScanDisk is meant to correct FAT errors. Defrag may also
|> |> help. But you should make a backup of your boot partition first,
|> |> just in case serious errors are found. You could try...
|> |>
|> |> (a) Boot to DOS. (Hold CTRL as you boot for the Startup Menu, &
|> |> select "Command Prompt Only".)
|> |>
|> |> (b) Scandisk /Checkonly /Surface
|> |>
|> |> This will not fix, but only inform what it intends to fix.
|> |> It will display on screen & get written to
|> |> "C:\Scandisk.log". It may take quite a while to complete.
|> |>
|> |> (c) Scandisk
|> |> Let it fix, if it didn't sound horrible. Otherwise, post
|> |> what it said.
|> |>
|> |> In Dos, you may see "C:\Scandisk.log" this way...
|> |>
|> |> EDIT C:\Scandisk.log
|> |> Alt-F-X (pressed separately) to exit EDIT. (TAB to traverse
|> |> buttons.)
|> |>
|> |> http://support.microsoft.com/kb/199557
|> |> Command-Line Parameters for the Scandisk Tool
|> |>
|> |> | MAXTOR Power Max 4.23 manufacturer's test (for Quantum drive) -
|> |> | all passed.
|> |>
|> |> The hard drive is good, then. It is the Windows file system that
|> |> may have a problem, (unless this is really a RAM issue after all).
|> |>
|> |> | Start>run>MSInfo32>Software environment>Startup Programs
|> |> |
|> |> | SystemTray Registry (Machine Run)
|> |> | SysTray.Exe ScanRegistry Registry (Machine Run)
|> |> | C:\WINDOWS\scanregw.exe /autorun
|> |> | LoadPowerProfile Registry (Machine Run)
|> |> | Rundll32.exe powrprof.dll,LoadCurrentPwrScheme
|> |>
|> |> Those are fine.
|> |>
|> |> | PCPitStopEraser Registry (Machine Run) C:\Program
|> |> | Files\PCPitstop\Erase\PCPitStopErase.exe /remindme
|> |> | AVG7_CC Registry (Machine Run)
|> |> | C:\PROGRA~1\GRISOFT\AVG7\AVGCC.EXE /STARTUP
|> |> | AVG7_EMC Registry (Machine Run)
|> |> | C:\PROGRA~1\GRISOFT\AVG7\AVGEMC.EXE
|> |> | AVG7_AMSVR Registry (Machine Run)
|> |> | C:\PROGRA~1\GRISOFT\AVG7\AVGAMSVR.EXE
|> |>
|> |> Maybe uncheck the above at...
|> |> "START, Run, MSConfig, Startup tab"
|> |> ...to see whether something has gone wrong with them. But I would
|> |> at first be more inclined to with a ScanDisk/Defrag. If done in
|> |> Windows (instead of DOS), don't let them constantly restart--
|> |> post back for a cure instead.
|> |>
|> |> | LoadPowerProfile Registry (Machine Service) Rundll32.exe
|> |> | powrprof.dll,LoadCurrentPwrScheme
|> |> | KB891711 Registry (Machine Service)
|> |> | C:\WINDOWS\SYSTEM\KB891711\KB891711.EXE
|> |> | KB918547 Registry (Machine Service)
|> |> | C:\WINDOWS\SYSTEM\KB918547\KB918547.EXE
|> |>
|> |> Those are fine, including the 2nd LoadPowerProfile, presuming you
|> |> have the repaired version of KB891711. But I'm sure you do.
|> |>
|> |> | Ran some test from PCPitStop long ago and still have their site
|> |> | in IE favorites list.
|> |> |
|> |> | Maybe the problem has been staring me in the face at every
|> |> | startup for months on end.
|> |> | Sometime last year a neighbor gave me and plugged in a
|> |> | couple extra 128 memory chips to go with the one original 128.
|> |> | At every startup I get the following message
|> |> | 'Memory write/read failure at 100002020, read 00000000,
|> |> | expecting 00EF00EF. Decreasing available memory.'
|> |> | A short pause and the continues with start up.
|> |> | Always assumed it meant one of the extra chips was bad and
|> |> | ignored it all this time and was just to lazy to pull it/them
|> |> | back out. If there is only one in there the system says 128.
|> |> | With
|> |> | any two or all three in there, the system says only 256. Ergo
|> |> | the bad chip assumption.
|> |>
|> |> Take one out permanently! I don't like that message!
|> |>
|> |> | Still getting these newer ones though: (only one at a time but
|> |> | with different devices)
|> |> | 'While initializing device VDD , windows protection error.
|> |> | Need to restart computer.'
|> |> | Usually VDD or VDK. Ocassionally VPICD. Once or
|> |> | twice with V86MMGR or that 386enhanced thing.
|> |>
|> |> Sounds like a complaint about the video (VDD) & the keyboard
|> |> (VDK). We can investigate these things if the other measures do
|> |> not suffice.
|> |>
|> |> | Might take a couple of restarts to get to the Normal or Safe
|> |> | Mode option and then a couple of Normal attempts there.
|> |> | Needless to say, I don't turm it off very often.
|> |> | But lots of re-starts lately with the diskette tests and
|> |> | checking the HD manufacturer and those memory chips.
|> |> | And I have gotten a couple of regular, straight thru startups,
|> |> | too. No Win 98 discs on hand here if that is.where the problem
|> |> | lurks.
|> |>
|> |> Well, let's hope it doesn't come to that. But you won't need an
|> |> installation CD, if the .cab's are on the hard drive...
|> |>
|> |> "START button, Find, F/F, Win98*.cab" (That's asterisk-dot-cab.)
|> |>
|> |> If 55 of them show up, the folder that contains them is a copy of
|> |> the Installation CD. Normally, they are in
|> |> "C:\Windows\Options\Cabs".
|> |>
|> |> |
|> |> | "PCR" <pcrrcp@netzero.net> wrote in message
|> |> | news:eKLVBtngIHA.4140@TK2MSFTNGP04.phx.gbl...
|> |> |> keith wrote:
|> |> |> | Baught some NEW, UNUSED floppies.
|> |> |> | Downloaded the Windows Memory Diagnostic (mtinst.exe) again
|> |> |> | and ran the test(s).
|> |> |> | Ran the standard suite for 3 passes and the extended suite
|> |> |> | for 2 passes. All 'Successful' and no errors found.
|> |> |>
|> |> |> Very good. The RAM is fine.
|> |> |>
|> |> |> | The 'WinDiag / mtinst.exe' confusion was all mine. Wasn't
|> |> |> | sure what to call it so typed the test name AND the file
|> |> |> | name.
|> |> |>
|> |> |> I see. OK.
|> |> |>
|> |> |> | There's probably an easy way to copy/paste or print the BIOS
|> |> |> | settings but I just wrote them all down
|> |> |> | and put them in the attached Word document.
|> |> |> |
|> |> |> | The large extra HD (for file storage) is the Seagate. The
|> |> |> | small main HD is a Quantum.
|> |> |> | Will try the Quantum/Maxtor links again and maybe the other
|> |> |> | RAM tests.
|> |> |>
|> |> |> Keep us informed. I think something could be wrong either with
|> |> |> the hard drive itself or with the Windows file system. Another
|> |> |> possibility is that there is too much in the Startup Group,
|> |> |> going by your words-- "dangerously low resources". Therefore...
|> |> |>
|> |> |> "START button, Run, MSInfo32, Software Environment, Startup
|> |> |> Programs". Use the Edit menu to copy & post it.
|> |> |>
|> |> |> | Thanks again.
|> |> |>
|> |> |> You are welcome. That BIOS report isn't so huge. It looks fine
|> |> |> to me, (although I don't know what Chassis Intrusion or DAC
|> |> |> Snoop is). Auto is a good setting for the hard drives. I'll
|> |> |> post it here, for others to easily see...
|> |> |>
|> |> |> Pentium II 400 Mhz System memory 15 MB SDRAM
|> |> |> Level 2 Cache 512 KB Integrated Video Memory 8 MB SGRAM
|> |> |>
|> |> |> **********
|> |> |>
|> |> |> Diskette A 1.44 MB
|> |> |> Diskette B Not Installed
|> |> |>
|> |> |> Drives Type CYLS HDS PRE SEC SIZE
|> |> |> Primary
|> |> |> Drive 0 Auto 913 255 -1 63 7509
|> |> |> Drive 1 Auto EIDE Drive 65432
|> |> |> Secondary
|> |> |> Drive 0 Auto CD ROM Drive
|> |> |> Drive 1 Auto CD ROM Drive
|> |> |> **********
|> |> |>
|> |> |> Reserved Memory 15 - 16 M
|> |> |> CPU Speed 400 Mhz
|> |> |> Num Lock On
|> |> |> Chassis Intrusion Disabled
|> |> |> DAC Snoop On
|> |> |> ACPI On
|> |> |>
|> |> |> **********
|> |> |>
|> |> |> Keyboard Errors Report
|> |> |> System Password Not Enabled
|> |> |> Password Status Unlocked
|> |> |> Boot Sequence Diskette First
|> |> |> Setup Password Not Enabled
|> |> |> Auto Power On Disabled 00:00
|> |> |> Power Management Regular
|> |> |> Wake-up on LAN Off
|> |> |>
|> |> |> **********
|> |> |>
|> |> |>
|> |> |> | "PCR" <pcrrcp@netzero.net> wrote in message
|> |> |> | news:uQX2aw%23fIHA.2448@TK2MSFTNGP03.phx.gbl...
|> |> |>
|> |> |> ...snip
|> |> |> |> |> keith wrote:
|> |> |> |> |> | Have seen a few errors at different times lately when
|> |> |> |> |> | booting / rebooting after system lock-ups.
|> |> |> |> |> |
|> |> |> |> |> | 'While initializing device VPICD: Windows
|> |> |> |> |> | protection error.' 'While initializing
|> |> |> |> |> | (installing??) V86MMGR:
|> |> |> |> |> | error cannot
|> |> |> |> |> | install 386 enhanced MXSD'
|> |> |> |> |> | Not sure if it said installing or
|> |> |> |> |> | initializing. Not sure I got the
|> |> |> |> |> | MXSD part correctly - MVXD?
|> |> |> |> |> | or some variation.
|> |> |> |> |> | And one about dangerously low resources.
|> |> |> |> |> |
|> |> |> |> |> | Tried a couple of SCANRE /RESTORE dates from prior to
|> |> |> |> |> | errors but still got the VPICD error on this last boot.
|> |> |> |> |> |
|> |> |> |> |> | W98 with 2 drives - First is just Windows and other
|> |> |> |> |> | programs - only 2 out of 6 gigs used
|> |> |> |> |> | Second is just files,
|> |> |> |> |> | fotos, vids - about 80 out of 95 gigs used.
|> |> |> |> |> | Second has
|> |> |> |> |> | been as high as 90 out of 95 without problems.
|> |> |> |> |> | Its usually
|> |> |> |> |> | in the 70-75 out of 90 range
|> |> |> |> |> |
|> |> |> |> |> | Have start up sequence set to display Normal, Safe
|> |> |> |> |> | Mode, Command Promp Only , etc menu with 30 second wait
|> |> |> |> |> | period. Ocasiionaly Normal doesn't load and it
|> |> |> |> |> | goes back to the
|> |> |> |> |> | menu with Safe Mode hilighted but can usually choose
|> |> |> |> |> | Normal again and complete the start-up.
|> |> |> |> |>
|> |> |> |> |> When an installation boots poorly only occasionally, the
|> |> |> |> |> bootstrap is probably fine. That includes BIOS, MBR
|> |> |> |> |> (Master Boot Record), PBR (Partition Boot Record), & all
|> |> |> |> |> the files needed to boot, even the Registry.
|> |> |> |> |>
|> |> |> |> |> | Nothing out of the ordinary with SpyBot, Ad-Aware,
|> |> |> |> |> | SpyWare Blaster or AVG scans.
|> |> |> |> |> | Nothing new in Add/Remove Programs list or
|> |> |> |> |> | ALT/CTRL/DEL list
|> |> |> |> |> |
|> |> |> |> |> | Thaught I'd post this first while this rig seems to be
|> |> |> |> |> | working OK and will start searching for solutions /
|> |> |> |> |> | references.
|> |> |> |> |>
|> |> |> |> |> (1) Run the RAM test as philo posted.
|> |> |> |> |> (2) Make a backup of your boot partition.
|> |> |> |> |> (It may be on its way out!)
|> |> |> |> |> (3) Run the hard drive diagnostic for your brand.
|> |> |> |> |> This repairs the structure of the hard drive, if
|> |> |> |> |> necessary. (4) Run a ScanDisk & Defrag.
|> |> |> |> |> This repairs the Windows file system, but could also
|> |> |> |> |> wreak havoc, if a big repair is necessary...
|> |> |> |> |> http://cquirke.mvps.org/9x/scandisk.htm
|> |> |> |> |>
|> |> |>
|> |> |> ...snip
|> |> |> --
|> |> |> Thanks or Good Luck,
|> |> |> There may be humor in this post, and,
|> |> |> Naturally, you will not sue,
|> |> |> Should things get worse after this,
|> |> |> PCR
|> |> |> pcrrcp@netzero.net
|> |>
|> |> --
|> |> Thanks or Good Luck,
|> |> There may be humor in this post, and,
|> |> Naturally, you will not sue,
|> |> Should things get worse after this,
|> |> PCR
|> |> pcrrcp@netzero.net
|>
|> --
|> Thanks or Good Luck,
|> There may be humor in this post, and,
|> Naturally, you will not sue,
|> Should things get worse after this,
|> PCR
|> pcrrcp@netzero.net

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

MEB · Apr 3, 2008

Re: 98 errors - continuing with scandisk and defrag

Not sure what you're about to post, but if issues are occurring during
normal mode, try creating a *.reg file:

------copy below to a text only editor
REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce]
"Scandisk"="Scandskw /a /n"
"Defrag"="Defrag /All /Detailed /Noprompt"

------paste the above with the blank lines into the editor.
Name it scanfrag.reg and merge this [or manually add ONLY if you have done
this
before] to the registry.

This runs scandisk first, then defrag, before the full GUI/system starts.
As it is a *RunOnce* it must be merged each time you wish to run them using
this method.

--
MEB http://peoplescounsel.orgfree.com
--
_________

"keith" <uncle@tanoose.nut> wrote in message
news:OfOKEuFlIHA.2268@TK2MSFTNGP02.phx.gbl...
| Philo is back after the 'To recover lost posts' suggestions. Thanks.
| Got the three months worth re-downloaded.
| Will OE keep adding to the three months or add new posts and cut older
posts
| to maintain just three months worth?
|
| And I'm back, too, after some lengthy service provider issues.
| Won't name names as that would CAST asspersions on the provider COMpany's
| name.
|
| Last 'Scan' and 'Defrag' in Safe Mode was quick enough on the small HD
with
| the programs, OS, etc.
| The larger 100 gig HD still scans and defrags in slow motion in Safe
Mode.
| No repeats, just slow.
| If I run defrag again at a later time it seems like it runs pretty quick
up
| to where it left off the last time and then slows down again.
| May try one more over-nighter to see if it'll finish.
| I never use a screen saver - I just turn off the monitor.
| Power manageent was set to 'Always on' and Never, Never.
| Changed it to 'Home/desktop' and Never, Never.
| History, cookies, and temp files (including off-line content) are
| cleared every day and sometimes twice a day.
|
| Started this thread with the start-up errors and that has been solved.
| Wondering if I should continue here with this scan and defrag issue or
make
| this issue a new post.
|
| Thanks again.
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:%23aUYkRjhIHA.2268@TK2MSFTNGP02.phx.gbl...
| > keith wrote:
| > | Didn't see Philo's replies in the thread last time I posted.
| > | Now I don't see the original post and full thread. Just this shortened
| > | Re.thread.
| > | Maybe it will all come back later. OE does get twitchy sometimes.
| >
| > I still see the whole thread.
| >
| > (a) Can you have accidentally deleted the 4 posts above my own?
| > (Pressing the delete key while sitting on one will do that.)
| >
| > (b) Can it be at...
| > "OE, View menu, Current View"
| > that "Show all messages" is not selected?
| >
| > To recover lost posts...
| >
| > (a) "R-Clk the NG in OE's left pane, Properties, Synchronize tab"
| > Ensure "All Messages" is selected. If it wasn't, do so,
| > & try at first to skip to step (c).
| >
| > (b) At the "Local File" tab, reset the NG.
| > This will wipe the NG, & prepare it for new download.
| >
| > (c) "OE, Tools menu, Synchronize Newsgroup".
| > This will download 3 months worth, if you have not
| > skipped step (b). May take a while on Dial-Up.
| >
| > | Quitr right. My answer to his 2nd was in my answer to your 1st.
| > | Sorry, Philo. I'd posted that reply at the tail end of the thread. No
| > | snub intended.
| > | Will revisit posting tips and etiquette.
| >
| > I guess your etiquette is fine.
| >
| > | Seems it was those pesky extra memory cards after all.
| > | Shuffled them around 1 at a time, 2 at a time, 3 three at a time and
| > | in different positions in the 3 available slots.
| > | Lots of reboots and those error messages in the process of
| > | elimination but finally got it straightened out.
| > | Have re-booted and re-started from OFF a number of times with no
| > | problem. Not sure if the lame RAM card is the original or not. Lost
| > | track of who's on first and what's on second.
| >
| > Alright, as long as it is working now. If any two of them will work, but
| > not three-- then it is possible there is a jumper on the MB that must be
| > moved when the 3rd is added. But I know little about it. Try the
| > manufacturers WEB site.
| >
| > | While nosing around I found 'Motherboard resources Properties' (in
| > | MSConfig I think) that showed Memory Range as
| > | 00EFE000 - 00EFFFFF. Yikes! There's those wierd characters again like
| > | in the memory error message, Yikes! The motherboard?
| > | Fear and trembling ensued. But for just a short while. Found lots of
| > | similar character strings in numerous memory summeries in a 12 page
| > | 'System Resource Report' I'd printed a few years back for this old
| > | Dell Optiplex Gx1p.
| > | Guess it is just standard terminology for memory usage or locations
| > | or some such thing.
| >
| > Those are hexadecimal numbers. Mine look just like that.
| >
| > | Anyhow -
| > | The Ram tests and manufacturer's HD test have all passed.
| > | Boots and re-boots are good.
| >
| > That says the RAM & the hard drive itself are fine.
| >
| > | No problems found with ScanDisk (standard) om small main HD and large
| > | storage HD.
| > | A 'Thorough' ScanDisk on both does the 10 restarts in Normal and
| > | Safe Mode.
| >
| > That is sad-- especially that it happens in Safe Mode! I don't like the
| > sound of that! Does it seem to run well in DOS?
| >
| > Most items that could cause the restarts are automatically turned off in
| > Safe Mode. Check whether any of these are still on...
| >
| > 1. Turn off screen saver (R-Clk Desktop, Properties, Screen Saver--
| > None).
| > 2. Turn off power management (Control Panel, Power Management--
| > Always On, Never, Never, Never).
| > 3. Suspend Task Scheduler.
| > 4. Disable any permanent internet cable connection, perhaps.
| > 5. "START button, Run, MSConfig, Startup tab". Note what is
| > unchecked. Then, go to the General tab & disable the entire
| > Startup Group, by clicking "Selective.." & unchecking
| > "Load Startup...". Reboot. Don't forget to re-enable before
| > the next boot.
| >
| > To speed up the scan somewhat...
| >
| > (a) "Control Panel, Internet Options, Delete Files button,
| > bolt Delete all offline content, OK, OK"
| > Those are the Temporary Internat Files, which can be huge.
| >
| > (b) "START button, Run, %TEMP%", & delete all files that will go.
| > This will likely be "C:\Windows\Temp". This is best done after a
| > fresh boot, if you have just done an install.
| >
| > | Have DeFragged the small main HD but the large one takes
| > | nearly half a day to get half way done.
| >
| > DON'T DO IT-- if you cannot get it to stop the constant restarts! I
| > remember 6-hour ScanDisks & Defrags being a precursor to my '01 hard
| > drive crash!
| >
| > | Hope its safe to have paused and quit before its done.
| > | Will put AVG back into the Start-Up routine.
| > |
| > | Thanks again to BOTH of yous guys for your time and patience.
| >
| > You are welcome.
| >
| > |
| > | "PCR" <pcrrcp@netzero.net> wrote in message
| > | news:uSZnYt0gIHA.4376@TK2MSFTNGP05.phx.gbl...
| > |> keith wrote:
| > |> | Where did Philo's reply go? No longer in this string.
| > |>
| > |> I see two responses by philo, & I can't remember if there were any
| > |> more. You answered his 1st (3/2/08 9:21 AM), but not his 2nd (3/2/08
| > |> 7:04 PM). WELL, you may have included the answer to his 2nd in your
| > |> answer to my 1st. Anyhow, it was about how to run WinDiag-- which I
| > |> think you've done.
| > |>
| > |> | Data Advisor 5.00
| > |> | Memory test - passed
| > |> | Smart Status test - passed
| > |> | 90 second test - passed
| > |>
| > |> That is good. But does it say how much memory it is testing? Does it
| > |> go through all 3 chips or only two? I don't like what you say below
| > |> about your memory chips! It could be Windows is having a problem,
| > |> despite these chips seem to pass memory tests. Maybe the first thing
| > |> to do is really to pull that extra chip to get rid of the error
| > |> message! Although during boot you get the message "decreasing
| > |> available memory"-- I can think Windows might try to use it anyhow
| > |> during those failed boots!
| > |>
| > |> | File structure test - "unknown" - Not sure what that means. File
| > |> | structure unknown? Test result unknown?
| > |>
| > |>
| > http://www.ontrackdatarecovery.com/hard-drive-software/dataadvisor.aspx
| > |> Ontrack Data Recovery
| > |> .......Quote...........
| > |> File Structure Test
| > |>
| > |> Reads and verifies the integrity of the File Allocation Tables (FAT)
| > |> on DOS, Windows 3.x, Windows 95, 98, Me, NT*, 2000* and XP*. Checks
| > |> critical boot sectors, reads the Master Boot Record and cross-checks
| > |> partition tables and CMOS.
| > |>
| > |> * Support for FAT formatted partitions only
| > |> .......EOQ..............
| > |>
| > |> That sounds like serious tests. Do you know which partition it is
| > |> referring to? Can it be an NTFS partition or other non-FAT partition
| > |> that DataAdvisor will not recognize? Try the FAQS link at that site,
| > |> but I could not find what "unknown" meant after a 20 minute intensive
| > |> search.
| > |>
| > |> Windows's ScanDisk is meant to correct FAT errors. Defrag may also
| > |> help. But you should make a backup of your boot partition first,
| > |> just in case serious errors are found. You could try...
| > |>
| > |> (a) Boot to DOS. (Hold CTRL as you boot for the Startup Menu, &
| > |> select "Command Prompt Only".)
| > |>
| > |> (b) Scandisk /Checkonly /Surface
| > |>
| > |> This will not fix, but only inform what it intends to fix.
| > |> It will display on screen & get written to "C:\Scandisk.log".
| > |> It may take quite a while to complete.
| > |>
| > |> (c) Scandisk
| > |> Let it fix, if it didn't sound horrible. Otherwise, post what
| > |> it said.
| > |>
| > |> In Dos, you may see "C:\Scandisk.log" this way...
| > |>
| > |> EDIT C:\Scandisk.log
| > |> Alt-F-X (pressed separately) to exit EDIT. (TAB to traverse buttons.)
| > |>
| > |> http://support.microsoft.com/kb/199557
| > |> Command-Line Parameters for the Scandisk Tool
| > |>
| > |> | MAXTOR Power Max 4.23 manufacturer's test (for Quantum drive) - all
| > |> | passed.
| > |>
| > |> The hard drive is good, then. It is the Windows file system that may
| > |> have a problem, (unless this is really a RAM issue after all).
| > |>
| > |> | Start>run>MSInfo32>Software environment>Startup Programs
| > |> |
| > |> | SystemTray Registry (Machine Run)
| > |> | SysTray.Exe ScanRegistry Registry (Machine Run)
| > |> | C:\WINDOWS\scanregw.exe /autorun
| > |> | LoadPowerProfile Registry (Machine Run) Rundll32.exe
| > |> | powrprof.dll,LoadCurrentPwrScheme
| > |>
| > |> Those are fine.
| > |>
| > |> | PCPitStopEraser Registry (Machine Run) C:\Program
| > |> | Files\PCPitstop\Erase\PCPitStopErase.exe /remindme
| > |> | AVG7_CC Registry (Machine Run)
| > |> | C:\PROGRA~1\GRISOFT\AVG7\AVGCC.EXE /STARTUP
| > |> | AVG7_EMC Registry (Machine Run)
| > |> | C:\PROGRA~1\GRISOFT\AVG7\AVGEMC.EXE
| > |> | AVG7_AMSVR Registry (Machine Run)
| > |> | C:\PROGRA~1\GRISOFT\AVG7\AVGAMSVR.EXE
| > |>
| > |> Maybe uncheck the above at...
| > |> "START, Run, MSConfig, Startup tab"
| > |> ...to see whether something has gone wrong with them. But I would at
| > |> first be more inclined to with a ScanDisk/Defrag. If done in Windows
| > |> (instead of DOS), don't let them constantly restart-- post back for a
| > |> cure instead.
| > |>
| > |> | LoadPowerProfile Registry (Machine Service) Rundll32.exe
| > |> | powrprof.dll,LoadCurrentPwrScheme
| > |> | KB891711 Registry (Machine Service)
| > |> | C:\WINDOWS\SYSTEM\KB891711\KB891711.EXE
| > |> | KB918547 Registry (Machine Service)
| > |> | C:\WINDOWS\SYSTEM\KB918547\KB918547.EXE
| > |>
| > |> Those are fine, including the 2nd LoadPowerProfile, presuming you
| > |> have the repaired version of KB891711. But I'm sure you do.
| > |>
| > |> | Ran some test from PCPitStop long ago and still have their site in
| > |> | IE favorites list.
| > |> |
| > |> | Maybe the problem has been staring me in the face at every
| > |> | startup for months on end.
| > |> | Sometime last year a neighbor gave me and plugged in a couple
| > |> | extra 128 memory chips to go with the one original 128.
| > |> | At every startup I get the following message
| > |> | 'Memory write/read failure at 100002020, read 00000000,
| > |> | expecting 00EF00EF. Decreasing available memory.'
| > |> | A short pause and the continues with start up.
| > |> | Always assumed it meant one of the extra chips was bad and
| > |> | ignored it all this time and was just to lazy to pull it/them back
| > |> | out. If there is only one in there the system says 128. With
| > |> | any two or all three in there, the system says only 256. Ergo the
| > |> | bad chip assumption.
| > |>
| > |> Take one out permanently! I don't like that message!
| > |>
| > |> | Still getting these newer ones though: (only one at a time but with
| > |> | different devices)
| > |> | 'While initializing device VDD , windows protection error.
| > |> | Need to restart computer.'
| > |> | Usually VDD or VDK. Ocassionally VPICD. Once or
| > |> | twice with V86MMGR or that 386enhanced thing.
| > |>
| > |> Sounds like a complaint about the video (VDD) & the keyboard (VDK).
| > |> We can investigate these things if the other measures do not suffice.
| > |>
| > |> | Might take a couple of restarts to get to the Normal or Safe Mode
| > |> | option and then a couple of Normal attempts there.
| > |> | Needless to say, I don't turm it off very often.
| > |> | But lots of re-starts lately with the diskette tests and checking
| > |> | the HD manufacturer and those memory chips.
| > |> | And I have gotten a couple of regular, straight thru startups, too.
| > |> | No Win 98 discs on hand here if that is.where the problem lurks.
| > |>
| > |> Well, let's hope it doesn't come to that. But you won't need an
| > |> installation CD, if the .cab's are on the hard drive...
| > |>
| > |> "START button, Find, F/F, Win98*.cab" (That's asterisk-dot-cab.)
| > |>
| > |> If 55 of them show up, the folder that contains them is a copy of the
| > |> Installation CD. Normally, they are in "C:\Windows\Options\Cabs".
| > |>
| > |> |
| > |> | "PCR" <pcrrcp@netzero.net> wrote in message
| > |> | news:eKLVBtngIHA.4140@TK2MSFTNGP04.phx.gbl...
| > |> |> keith wrote:
| > |> |> | Baught some NEW, UNUSED floppies.
| > |> |> | Downloaded the Windows Memory Diagnostic (mtinst.exe) again and
| > |> |> | ran the test(s).
| > |> |> | Ran the standard suite for 3 passes and the extended suite for 2
| > |> |> | passes. All 'Successful' and no errors found.
| > |> |>
| > |> |> Very good. The RAM is fine.
| > |> |>
| > |> |> | The 'WinDiag / mtinst.exe' confusion was all mine. Wasn't sure
| > |> |> | what to call it so typed the test name AND the file name.
| > |> |>
| > |> |> I see. OK.
| > |> |>
| > |> |> | There's probably an easy way to copy/paste or print the BIOS
| > |> |> | settings but I just wrote them all down
| > |> |> | and put them in the attached Word document.
| > |> |> |
| > |> |> | The large extra HD (for file storage) is the Seagate. The small
| > |> |> | main HD is a Quantum.
| > |> |> | Will try the Quantum/Maxtor links again and maybe the other RAM
| > |> |> | tests.
| > |> |>
| > |> |> Keep us informed. I think something could be wrong either with the
| > |> |> hard drive itself or with the Windows file system. Another
| > |> |> possibility is that there is too much in the Startup Group, going
| > |> |> by your words-- "dangerously low resources". Therefore...
| > |> |>
| > |> |> "START button, Run, MSInfo32, Software Environment, Startup
| > |> |> Programs". Use the Edit menu to copy & post it.
| > |> |>
| > |> |> | Thanks again.
| > |> |>
| > |> |> You are welcome. That BIOS report isn't so huge. It looks fine to
| > |> |> me, (although I don't know what Chassis Intrusion or DAC Snoop
| > |> |> is). Auto is a good setting for the hard drives. I'll post it
| > |> |> here, for others to easily see...
| > |> |>
| > |> |> Pentium II 400 Mhz System memory 15 MB SDRAM
| > |> |> Level 2 Cache 512 KB Integrated Video Memory 8 MB SGRAM
| > |> |>
| > |> |> **********
| > |> |>
| > |> |> Diskette A 1.44 MB
| > |> |> Diskette B Not Installed
| > |> |>
| > |> |> Drives Type CYLS HDS PRE SEC SIZE
| > |> |> Primary
| > |> |> Drive 0 Auto 913 255 -1 63 7509
| > |> |> Drive 1 Auto EIDE Drive 65432
| > |> |> Secondary
| > |> |> Drive 0 Auto CD ROM Drive
| > |> |> Drive 1 Auto CD ROM Drive
| > |> |> **********
| > |> |>
| > |> |> Reserved Memory 15 - 16 M
| > |> |> CPU Speed 400 Mhz
| > |> |> Num Lock On
| > |> |> Chassis Intrusion Disabled
| > |> |> DAC Snoop On
| > |> |> ACPI On
| > |> |>
| > |> |> **********
| > |> |>
| > |> |> Keyboard Errors Report
| > |> |> System Password Not Enabled
| > |> |> Password Status Unlocked
| > |> |> Boot Sequence Diskette First
| > |> |> Setup Password Not Enabled
| > |> |> Auto Power On Disabled 00:00
| > |> |> Power Management Regular
| > |> |> Wake-up on LAN Off
| > |> |>
| > |> |> **********
| > |> |>
| > |> |>
| > |> |> | "PCR" <pcrrcp@netzero.net> wrote in message
| > |> |> | news:uQX2aw%23fIHA.2448@TK2MSFTNGP03.phx.gbl...
| > |> |>
| > |> |> ...snip
| > |> |> |> |> keith wrote:
| > |> |> |> |> | Have seen a few errors at different times lately when
| > |> |> |> |> | booting / rebooting after system lock-ups.
| > |> |> |> |> |
| > |> |> |> |> | 'While initializing device VPICD: Windows
| > |> |> |> |> | protection error.' 'While initializing
| > |> |> |> |> | (installing??) V86MMGR:
| > |> |> |> |> | error cannot
| > |> |> |> |> | install 386 enhanced MXSD'
| > |> |> |> |> | Not sure if it said installing or
| > |> |> |> |> | initializing. Not sure I got the MXSD
| > |> |> |> |> | part correctly - MVXD?
| > |> |> |> |> | or some variation.
| > |> |> |> |> | And one about dangerously low resources.
| > |> |> |> |> |
| > |> |> |> |> | Tried a couple of SCANRE /RESTORE dates from prior to
| > |> |> |> |> | errors but still got the VPICD error on this last boot.
| > |> |> |> |> |
| > |> |> |> |> | W98 with 2 drives - First is just Windows and other
| > |> |> |> |> | programs - only 2 out of 6 gigs used
| > |> |> |> |> | Second is just files,
| > |> |> |> |> | fotos, vids - about 80 out of 95 gigs used.
| > |> |> |> |> | Second has been
| > |> |> |> |> | as high as 90 out of 95 without problems.
| > |> |> |> |> | Its usually in
| > |> |> |> |> | the 70-75 out of 90 range
| > |> |> |> |> |
| > |> |> |> |> | Have start up sequence set to display Normal, Safe
| > |> |> |> |> | Mode, Command Promp Only , etc menu with 30 second wait
| > |> |> |> |> | period. Ocasiionaly Normal doesn't load and it goes
| > |> |> |> |> | back to the
| > |> |> |> |> | menu with Safe Mode hilighted but can usually choose
| > |> |> |> |> | Normal again and complete the start-up.
| > |> |> |> |>
| > |> |> |> |> When an installation boots poorly only occasionally, the
| > |> |> |> |> bootstrap is probably fine. That includes BIOS, MBR (Master
| > |> |> |> |> Boot Record), PBR (Partition Boot Record), & all the files
| > |> |> |> |> needed to boot, even the Registry.
| > |> |> |> |>
| > |> |> |> |> | Nothing out of the ordinary with SpyBot, Ad-Aware,
| > |> |> |> |> | SpyWare Blaster or AVG scans.
| > |> |> |> |> | Nothing new in Add/Remove Programs list or
| > |> |> |> |> | ALT/CTRL/DEL list
| > |> |> |> |> |
| > |> |> |> |> | Thaught I'd post this first while this rig seems to be
| > |> |> |> |> | working OK and will start searching for solutions /
| > |> |> |> |> | references.
| > |> |> |> |>
| > |> |> |> |> (1) Run the RAM test as philo posted.
| > |> |> |> |> (2) Make a backup of your boot partition.
| > |> |> |> |> (It may be on its way out!)
| > |> |> |> |> (3) Run the hard drive diagnostic for your brand.
| > |> |> |> |> This repairs the structure of the hard drive, if
| > |> |> |> |> necessary. (4) Run a ScanDisk & Defrag.
| > |> |> |> |> This repairs the Windows file system, but could also
| > |> |> |> |> wreak havoc, if a big repair is necessary...
| > |> |> |> |> http://cquirke.mvps.org/9x/scandisk.htm
| > |> |> |> |>
| > |> |>
| > |> |> ...snip
| > |> |> --
| > |> |> Thanks or Good Luck,
| > |> |> There may be humor in this post, and,
| > |> |> Naturally, you will not sue,
| > |> |> Should things get worse after this,
| > |> |> PCR
| > |> |> pcrrcp@netzero.net
| > |>
| > |> --
| > |> Thanks or Good Luck,
| > |> There may be humor in this post, and,
| > |> Naturally, you will not sue,
| > |> Should things get worse after this,
| > |> PCR
| > |> pcrrcp@netzero.net
| >
| > --
| > Thanks or Good Luck,
| > There may be humor in this post, and,
| > Naturally, you will not sue,
| > Should things get worse after this,
| > PCR
| > pcrrcp@netzero.net
| >
| >
|
|

98 errors -VPICD, V86MMGR, 386enhanced

philo

keith

philo

keith

PCR

keith

PCR

keith

PCR

keith

PCR

keith

PCR

Franc Zabkar

keith

keith

PCR

MEB

Similar threads