This computer runs Windows Me. It was working just fine before being shut
down and moved because of a new carpet being put down. When it was hooked
back up and powered up it would progress to the Windows Me logo window and
then stop and start the boot all over. Next up was the Safe Mode option.
When we select Safe Mode it progress into Safe Mode and operates in the mode
as it should. If we select normal start up it loops again.
No error messages have come up. The computer registeres both hard drives,
both CD/DVD drives.
Right now we cannot figure out what it is doing this. Any suggestions please.

Briandp

Re: Boot Loop by Mart

Mart
Thu Sep 28 03:26:25 CDT 2006

Brian, the fact that it appears to boot into Safe Mode without a problem
suggests that it might just be an external hardware issue, especially as
you've moved (disconnected - reconnected) your pc and its peripherals.

Either confirm your external connectors and/or disconnect all external
hardware - except monitor, keyboard and mouse - and see if there is any
improvement.

Also, take a look at the files bootlog.prv and bootlog.txt (in the root
folder of the C: drive) in Safe Mode, using Notepad to read them. Look at
the last item(s) in the file which *might* give a clue as to what is causing
it to fail. (BTW - confirm that the dates of these files correspond to your
recent move.)

Failing to find any external device causing the problem, you may have to
take a look inside your pc for badly seated cables or cards which could have
become dislodged during the movement of your pc. - Good luck!

Mart



"Briandp" <Briandp@discussions.microsoft.com> wrote in message
news:EB0D778C-0E77-4A7F-A424-3AD524D46E26@microsoft.com...
> This computer runs Windows Me. It was working just fine before being shut
> down and moved because of a new carpet being put down. When it was hooked
> back up and powered up it would progress to the Windows Me logo window and
> then stop and start the boot all over. Next up was the Safe Mode option.
> When we select Safe Mode it progress into Safe Mode and operates in the
> mode
> as it should. If we select normal start up it loops again.
> No error messages have come up. The computer registeres both hard drives,
> both CD/DVD drives.
> Right now we cannot figure out what it is doing this. Any suggestions
> please.
>
> Briandp



RE: Boot Loop by Briandp

Briandp
Fri Sep 29 17:56:02 CDT 2006

Did the disconnect and reconnect and it did not work.
Openned the computer and all cards, memory, and drives have a solid
connection.
Went in to the Bootlog.txt and found the following:

It appears that all went well through'

LoadStart=Display.drv
LoadSuccess=Display.drv

InitDone=Display
Init=Display Resources
InitDone=Display Resources

Then it has a long long lsit of:

"Failure code is 0016"

Starting with:

LoadStart=C:\WINDOWS\fonts\MARLETT.TTF
LoadFail=C:\WINDOWS\fonts\MARLETT.TTF Failure code is 0016

Way down at the bottom it then lists:

LoadSuccess=USER.EXE
LoadStart=MSGSRV32.EXE
LoadSuccess=MSGRV32.EXE

THEN:

It has a number of TRSQuery entries.

Any ideas with that.

Thanks Briandp

"Briandp" wrote:

> This computer runs Windows Me. It was working just fine before being shut
> down and moved because of a new carpet being put down. When it was hooked
> back up and powered up it would progress to the Windows Me logo window and
> then stop and start the boot all over. Next up was the Safe Mode option.
> When we select Safe Mode it progress into Safe Mode and operates in the mode
> as it should. If we select normal start up it loops again.
> No error messages have come up. The computer registeres both hard drives,
> both CD/DVD drives.
> Right now we cannot figure out what it is doing this. Any suggestions please.
>
> Briandp

Re: Boot Loop by Mart

Mart
Fri Sep 29 18:59:05 CDT 2006

> Any ideas with that.

Not really Brian except to say that I've heard of this problem (Failure code
is 0016) before but never heard of a definitive solution. ... Just try
Googling!

Suggestions?
Unlikely, but confirm that you haven't been infected with anything, by
running your AV utility. If you can't get yours to run in Safe Mode, try
F-Protect AV for DOS from http://www.f-prot.com/ which you can be run from
Real Mode DOS using your WinMe floppy Startup Disk.

If nothing found, then try booting (using F8) with option 4) Step-by-step
confirmation and eliminate one item at a time (N.B. this could take quite a
while - and a number of re-boots - as you may have a dozen or more items to
confirm (or not!) - But do it methodically!

The fact that your fonts are 'failing' is (in my experience) probably due to
a hardware device/driver issue. But locating which, can be a long-winded
process of elimination.

I would suggest that you also take a look at Device Manager and see if there
are any conflicts (Yellow Question/Exclamation marks, or any duplicated
items.

> The computer registeres both hard drives,
> both CD/DVD drives.

I wonder why you are telling me that - do you know something more?
Are you seeing them in your DOS 'post' screen or in Windows explorer in Safe
Mode? - Very worrying if you can see your CD/DVD drives in Windows Explorer
in Safe Mode - because you shouldn't!!
You should be able to see them in DevMan in Safe Mode though.


Mart


"Briandp" <Briandp@discussions.microsoft.com> wrote in message
news:EACCBE68-60A4-4A6A-A484-8F7D7C977673@microsoft.com...
> Did the disconnect and reconnect and it did not work.
> Openned the computer and all cards, memory, and drives have a solid
> connection.
> Went in to the Bootlog.txt and found the following:
>
> It appears that all went well through'
>
> LoadStart=Display.drv
> LoadSuccess=Display.drv
>
> InitDone=Display
> Init=Display Resources
> InitDone=Display Resources
>
> Then it has a long long lsit of:
>
> "Failure code is 0016"
>
> Starting with:
>
> LoadStart=C:\WINDOWS\fonts\MARLETT.TTF
> LoadFail=C:\WINDOWS\fonts\MARLETT.TTF Failure code is 0016
>
> Way down at the bottom it then lists:
>
> LoadSuccess=USER.EXE
> LoadStart=MSGSRV32.EXE
> LoadSuccess=MSGRV32.EXE
>
> THEN:
>
> It has a number of TRSQuery entries.
>
> Any ideas with that.
>
> Thanks Briandp
>
> "Briandp" wrote:
>
>> This computer runs Windows Me. It was working just fine before being
>> shut
>> down and moved because of a new carpet being put down. When it was
>> hooked
>> back up and powered up it would progress to the Windows Me logo window
>> and
>> then stop and start the boot all over. Next up was the Safe Mode option.
>> When we select Safe Mode it progress into Safe Mode and operates in the
>> mode
>> as it should. If we select normal start up it loops again.
>> No error messages have come up. The computer registeres both hard
>> drives,
>> both CD/DVD drives.
>> Right now we cannot figure out what it is doing this. Any suggestions
>> please.
>>
>> Briandp



Re: Boot Loop by Briandp

Briandp
Sat Sep 30 00:38:02 CDT 2006

Mart, I'm sorry for the confusion. I see the CD/DVD when I'm in the BIOS.
They register there just fine. In safe mode the only drives there are the
hard drives and the floppy drive. Sorry about that. I was just trying to
advise that they are working and operational.

I will try the F-8 process and if that does not work, Then I think I may be
in for an F-disk job. I'll let you know how it comes out.

brianbp Also, thankyou for your assistance.

"Mart" wrote:

> > Any ideas with that.
>
> Not really Brian except to say that I've heard of this problem (Failure code
> is 0016) before but never heard of a definitive solution. ... Just try
> Googling!
>
> Suggestions?
> Unlikely, but confirm that you haven't been infected with anything, by
> running your AV utility. If you can't get yours to run in Safe Mode, try
> F-Protect AV for DOS from http://www.f-prot.com/ which you can be run from
> Real Mode DOS using your WinMe floppy Startup Disk.
>
> If nothing found, then try booting (using F8) with option 4) Step-by-step
> confirmation and eliminate one item at a time (N.B. this could take quite a
> while - and a number of re-boots - as you may have a dozen or more items to
> confirm (or not!) - But do it methodically!
>
> The fact that your fonts are 'failing' is (in my experience) probably due to
> a hardware device/driver issue. But locating which, can be a long-winded
> process of elimination.
>
> I would suggest that you also take a look at Device Manager and see if there
> are any conflicts (Yellow Question/Exclamation marks, or any duplicated
> items.
>
> > The computer registeres both hard drives,
> > both CD/DVD drives.
>
> I wonder why you are telling me that - do you know something more?
> Are you seeing them in your DOS 'post' screen or in Windows explorer in Safe
> Mode? - Very worrying if you can see your CD/DVD drives in Windows Explorer
> in Safe Mode - because you shouldn't!!
> You should be able to see them in DevMan in Safe Mode though.
>
>
> Mart
>
>
> "Briandp" <Briandp@discussions.microsoft.com> wrote in message
> news:EACCBE68-60A4-4A6A-A484-8F7D7C977673@microsoft.com...
> > Did the disconnect and reconnect and it did not work.
> > Openned the computer and all cards, memory, and drives have a solid
> > connection.
> > Went in to the Bootlog.txt and found the following:
> >
> > It appears that all went well through'
> >
> > LoadStart=Display.drv
> > LoadSuccess=Display.drv
> >
> > InitDone=Display
> > Init=Display Resources
> > InitDone=Display Resources
> >
> > Then it has a long long lsit of:
> >
> > "Failure code is 0016"
> >
> > Starting with:
> >
> > LoadStart=C:\WINDOWS\fonts\MARLETT.TTF
> > LoadFail=C:\WINDOWS\fonts\MARLETT.TTF Failure code is 0016
> >
> > Way down at the bottom it then lists:
> >
> > LoadSuccess=USER.EXE
> > LoadStart=MSGSRV32.EXE
> > LoadSuccess=MSGRV32.EXE
> >
> > THEN:
> >
> > It has a number of TRSQuery entries.
> >
> > Any ideas with that.
> >
> > Thanks Briandp
> >
> > "Briandp" wrote:
> >
> >> This computer runs Windows Me. It was working just fine before being
> >> shut
> >> down and moved because of a new carpet being put down. When it was
> >> hooked
> >> back up and powered up it would progress to the Windows Me logo window
> >> and
> >> then stop and start the boot all over. Next up was the Safe Mode option.
> >> When we select Safe Mode it progress into Safe Mode and operates in the
> >> mode
> >> as it should. If we select normal start up it loops again.
> >> No error messages have come up. The computer registeres both hard
> >> drives,
> >> both CD/DVD drives.
> >> Right now we cannot figure out what it is doing this. Any suggestions
> >> please.
> >>
> >> Briandp
>
>
>

Re: Boot Loop by Briandp

Briandp
Mon Oct 02 16:55:02 CDT 2006

Mart:

I have ran down all the hardware for this computer and set it up as it was
before they took it appart for the carpet job. Once I did that I tried a
boot and got the same results.

I then decided to do a step by step boot up and this is what I found.

First log to appear when I started the step by step was:

Create Startup Log file: Yes
Enable SMARTDRV cache: Yes
Device=C:\WINDOWS\DBLBUFF.SYS Yes
Load All Windows drivers Yes
vnetsup.vxd Yes
ndis.vxd Yes
JAVASUP.VXD Yes
vnetbios.vsx Yes
vredir.vxd Yes
ofs.vxd Yes
VIAGART.DVD Yes
Fastpara.vxd Yes
MRTRATE.VXD Yes
C:\WINDOWS\SYSTEM\Dragburn.vxd Yes
ASPIENUM.VXD Yes
vsdata95.vxd When I did Yes on this it restarted the computer.

I then went through the step by step again and when I got to this last note
I entered No and it restarted the computer.

I found out that there are two hard drives a C drive with 40Gb and a D drive
with 6Gb. The D drive is the original drive for this computer, the C drive
is the newer one that was added in and has Windows Me on it. The D drive has
the old Windows 95 operating system in it or parts of it. All the hardware
was joined with this computer when it was running Win 95 as the operating
system.

I have disconnected the D drive and tried to boot up and got the same
results, a restart to the safe mode menu.

Feel that the problem is in this area with a conflict between the Me and 95
os elements that are still in the computer. I'm considering going into the
REgistry and searching out all Win95 elements and removing them, however I
may just compound the problem. If you have any other suggestions I am ready
to try them.

Briandp

"Briandp" wrote:

> Mart, I'm sorry for the confusion. I see the CD/DVD when I'm in the BIOS.
> They register there just fine. In safe mode the only drives there are the
> hard drives and the floppy drive. Sorry about that. I was just trying to
> advise that they are working and operational.
>
> I will try the F-8 process and if that does not work, Then I think I may be
> in for an F-disk job. I'll let you know how it comes out.
>
> brianbp Also, thankyou for your assistance.
>
> "Mart" wrote:
>
> > > Any ideas with that.
> >
> > Not really Brian except to say that I've heard of this problem (Failure code
> > is 0016) before but never heard of a definitive solution. ... Just try
> > Googling!
> >
> > Suggestions?
> > Unlikely, but confirm that you haven't been infected with anything, by
> > running your AV utility. If you can't get yours to run in Safe Mode, try
> > F-Protect AV for DOS from http://www.f-prot.com/ which you can be run from
> > Real Mode DOS using your WinMe floppy Startup Disk.
> >
> > If nothing found, then try booting (using F8) with option 4) Step-by-step
> > confirmation and eliminate one item at a time (N.B. this could take quite a
> > while - and a number of re-boots - as you may have a dozen or more items to
> > confirm (or not!) - But do it methodically!
> >
> > The fact that your fonts are 'failing' is (in my experience) probably due to
> > a hardware device/driver issue. But locating which, can be a long-winded
> > process of elimination.
> >
> > I would suggest that you also take a look at Device Manager and see if there
> > are any conflicts (Yellow Question/Exclamation marks, or any duplicated
> > items.
> >
> > > The computer registeres both hard drives,
> > > both CD/DVD drives.
> >
> > I wonder why you are telling me that - do you know something more?
> > Are you seeing them in your DOS 'post' screen or in Windows explorer in Safe
> > Mode? - Very worrying if you can see your CD/DVD drives in Windows Explorer
> > in Safe Mode - because you shouldn't!!
> > You should be able to see them in DevMan in Safe Mode though.
> >
> >
> > Mart
> >
> >
> > "Briandp" <Briandp@discussions.microsoft.com> wrote in message
> > news:EACCBE68-60A4-4A6A-A484-8F7D7C977673@microsoft.com...
> > > Did the disconnect and reconnect and it did not work.
> > > Openned the computer and all cards, memory, and drives have a solid
> > > connection.
> > > Went in to the Bootlog.txt and found the following:
> > >
> > > It appears that all went well through'
> > >
> > > LoadStart=Display.drv
> > > LoadSuccess=Display.drv
> > >
> > > InitDone=Display
> > > Init=Display Resources
> > > InitDone=Display Resources
> > >
> > > Then it has a long long lsit of:
> > >
> > > "Failure code is 0016"
> > >
> > > Starting with:
> > >
> > > LoadStart=C:\WINDOWS\fonts\MARLETT.TTF
> > > LoadFail=C:\WINDOWS\fonts\MARLETT.TTF Failure code is 0016
> > >
> > > Way down at the bottom it then lists:
> > >
> > > LoadSuccess=USER.EXE
> > > LoadStart=MSGSRV32.EXE
> > > LoadSuccess=MSGRV32.EXE
> > >
> > > THEN:
> > >
> > > It has a number of TRSQuery entries.
> > >
> > > Any ideas with that.
> > >
> > > Thanks Briandp
> > >
> > > "Briandp" wrote:
> > >
> > >> This computer runs Windows Me. It was working just fine before being
> > >> shut
> > >> down and moved because of a new carpet being put down. When it was
> > >> hooked
> > >> back up and powered up it would progress to the Windows Me logo window
> > >> and
> > >> then stop and start the boot all over. Next up was the Safe Mode option.
> > >> When we select Safe Mode it progress into Safe Mode and operates in the
> > >> mode
> > >> as it should. If we select normal start up it loops again.
> > >> No error messages have come up. The computer registeres both hard
> > >> drives,
> > >> both CD/DVD drives.
> > >> Right now we cannot figure out what it is doing this. Any suggestions
> > >> please.
> > >>
> > >> Briandp
> >
> >
> >

Re: Boot Loop by Mike

Mike
Mon Oct 02 17:08:36 CDT 2006

Try booting to Safe Mode and uninstalling Zone Alarm and see if this now
allows you to boot to normal mode. vsdata95.vxd is part of ZA.
--
Mike Maltby
mike.maltby@gmail.com


Briandp <Briandp@discussions.microsoft.com> wrote:

> Mart:
>
> I have ran down all the hardware for this computer and set it up as
> it was before they took it appart for the carpet job. Once I did
> that I tried a boot and got the same results.
>
> I then decided to do a step by step boot up and this is what I found.
>
> First log to appear when I started the step by step was:
>
> Create Startup Log file: Yes
> Enable SMARTDRV cache: Yes
> Device=C:\WINDOWS\DBLBUFF.SYS Yes
> Load All Windows drivers Yes
> vnetsup.vxd Yes
> ndis.vxd Yes
> JAVASUP.VXD Yes
> vnetbios.vsx Yes
> vredir.vxd Yes
> ofs.vxd Yes
> VIAGART.DVD Yes
> Fastpara.vxd Yes
> MRTRATE.VXD Yes
> C:\WINDOWS\SYSTEM\Dragburn.vxd Yes
> ASPIENUM.VXD Yes
> vsdata95.vxd When I did Yes on this it restarted the
> computer.
>
> I then went through the step by step again and when I got to this
> last note I entered No and it restarted the computer.
>
> I found out that there are two hard drives a C drive with 40Gb and a
> D drive with 6Gb. The D drive is the original drive for this
> computer, the C drive is the newer one that was added in and has
> Windows Me on it. The D drive has the old Windows 95 operating
> system in it or parts of it. All the hardware was joined with this
> computer when it was running Win 95 as the operating system.
>
> I have disconnected the D drive and tried to boot up and got the same
> results, a restart to the safe mode menu.
>
> Feel that the problem is in this area with a conflict between the Me
> and 95 os elements that are still in the computer. I'm considering
> going into the REgistry and searching out all Win95 elements and
> removing them, however I may just compound the problem. If you have
> any other suggestions I am ready to try them.


Re: Boot Loop by Mart

Mart
Mon Oct 02 19:10:42 CDT 2006

If Mike's suggestion doesn't bear fruit, go back into Step-by-step and
answer 'No' to each line - one at a time - to see if that helps to pin it
down. The reboot and try a 'No' against the next line etc. (I said it would
be a long process)

Interestingly MS Knowledge Base highlights a 'potential issue' with
mrtrate.vxd and your printer driver :-

"Fatal Exception 0E Has Occurred in VXD mrtRate (01) When Printing"
http://support.microsoft.com/?kbid=252414

I just wonder if it is related to your problem.

Also, take a look at Device Manager - in Safe Mode - and see if there any
conflicts or yellow question/exclamation marks or duplicated entries.

However, if you are quite sure that you've not changed any hardware/software
since immediately before the 'carpet' episode (when things were ok) and then
after the episode when things went down hill, you could try running System
Restore and roll-back to the last time before the carpet job.

Mart


"Briandp" <Briandp@discussions.microsoft.com> wrote in message
news:A6EA8BB7-99C6-4D87-87F8-1F6576546432@microsoft.com...
> Mart:
>
> I have ran down all the hardware for this computer and set it up as it was
> before they took it appart for the carpet job. Once I did that I tried a
> boot and got the same results.
>
> I then decided to do a step by step boot up and this is what I found.
>
> First log to appear when I started the step by step was:
>
> Create Startup Log file: Yes
> Enable SMARTDRV cache: Yes
> Device=C:\WINDOWS\DBLBUFF.SYS Yes
> Load All Windows drivers Yes
> vnetsup.vxd Yes
> ndis.vxd Yes
> JAVASUP.VXD Yes
> vnetbios.vsx Yes
> vredir.vxd Yes
> ofs.vxd Yes
> VIAGART.DVD Yes
> Fastpara.vxd Yes
> MRTRATE.VXD Yes
> C:\WINDOWS\SYSTEM\Dragburn.vxd Yes
> ASPIENUM.VXD Yes
> vsdata95.vxd When I did Yes on this it restarted the computer.
>
> I then went through the step by step again and when I got to this last
> note
> I entered No and it restarted the computer.
>
> I found out that there are two hard drives a C drive with 40Gb and a D
> drive
> with 6Gb. The D drive is the original drive for this computer, the C
> drive
> is the newer one that was added in and has Windows Me on it. The D drive
> has
> the old Windows 95 operating system in it or parts of it. All the
> hardware
> was joined with this computer when it was running Win 95 as the operating
> system.
>
> I have disconnected the D drive and tried to boot up and got the same
> results, a restart to the safe mode menu.
>
> Feel that the problem is in this area with a conflict between the Me and
> 95
> os elements that are still in the computer. I'm considering going into
> the
> REgistry and searching out all Win95 elements and removing them, however I
> may just compound the problem. If you have any other suggestions I am
> ready
> to try them.
>
> Briandp
>
> "Briandp" wrote:
>
>> Mart, I'm sorry for the confusion. I see the CD/DVD when I'm in the
>> BIOS.
>> They register there just fine. In safe mode the only drives there are
>> the
>> hard drives and the floppy drive. Sorry about that. I was just trying
>> to
>> advise that they are working and operational.
>>
>> I will try the F-8 process and if that does not work, Then I think I may
>> be
>> in for an F-disk job. I'll let you know how it comes out.
>>
>> brianbp Also, thankyou for your assistance.
>>
>> "Mart" wrote:
>>
>> > > Any ideas with that.
>> >
>> > Not really Brian except to say that I've heard of this problem (Failure
>> > code
>> > is 0016) before but never heard of a definitive solution. ... Just
>> > try
>> > Googling!
>> >
>> > Suggestions?
>> > Unlikely, but confirm that you haven't been infected with anything, by
>> > running your AV utility. If you can't get yours to run in Safe Mode,
>> > try
>> > F-Protect AV for DOS from http://www.f-prot.com/ which you can be run
>> > from
>> > Real Mode DOS using your WinMe floppy Startup Disk.
>> >
>> > If nothing found, then try booting (using F8) with option 4)
>> > Step-by-step
>> > confirmation and eliminate one item at a time (N.B. this could take
>> > quite a
>> > while - and a number of re-boots - as you may have a dozen or more
>> > items to
>> > confirm (or not!) - But do it methodically!
>> >
>> > The fact that your fonts are 'failing' is (in my experience) probably
>> > due to
>> > a hardware device/driver issue. But locating which, can be a
>> > long-winded
>> > process of elimination.
>> >
>> > I would suggest that you also take a look at Device Manager and see if
>> > there
>> > are any conflicts (Yellow Question/Exclamation marks, or any duplicated
>> > items.
>> >
>> > > The computer registeres both hard drives,
>> > > both CD/DVD drives.
>> >
>> > I wonder why you are telling me that - do you know something more?
>> > Are you seeing them in your DOS 'post' screen or in Windows explorer in
>> > Safe
>> > Mode? - Very worrying if you can see your CD/DVD drives in Windows
>> > Explorer
>> > in Safe Mode - because you shouldn't!!
>> > You should be able to see them in DevMan in Safe Mode though.
>> >
>> >
>> > Mart
>> >
>> >
>> > "Briandp" <Briandp@discussions.microsoft.com> wrote in message
>> > news:EACCBE68-60A4-4A6A-A484-8F7D7C977673@microsoft.com...
>> > > Did the disconnect and reconnect and it did not work.
>> > > Openned the computer and all cards, memory, and drives have a solid
>> > > connection.
>> > > Went in to the Bootlog.txt and found the following:
>> > >
>> > > It appears that all went well through'
>> > >
>> > > LoadStart=Display.drv
>> > > LoadSuccess=Display.drv
>> > >
>> > > InitDone=Display
>> > > Init=Display Resources
>> > > InitDone=Display Resources
>> > >
>> > > Then it has a long long lsit of:
>> > >
>> > > "Failure code is 0016"
>> > >
>> > > Starting with:
>> > >
>> > > LoadStart=C:\WINDOWS\fonts\MARLETT.TTF
>> > > LoadFail=C:\WINDOWS\fonts\MARLETT.TTF Failure code is 0016
>> > >
>> > > Way down at the bottom it then lists:
>> > >
>> > > LoadSuccess=USER.EXE
>> > > LoadStart=MSGSRV32.EXE
>> > > LoadSuccess=MSGRV32.EXE
>> > >
>> > > THEN:
>> > >
>> > > It has a number of TRSQuery entries.
>> > >
>> > > Any ideas with that.
>> > >
>> > > Thanks Briandp
>> > >
>> > > "Briandp" wrote:
>> > >
>> > >> This computer runs Windows Me. It was working just fine before
>> > >> being
>> > >> shut
>> > >> down and moved because of a new carpet being put down. When it was
>> > >> hooked
>> > >> back up and powered up it would progress to the Windows Me logo
>> > >> window
>> > >> and
>> > >> then stop and start the boot all over. Next up was the Safe Mode
>> > >> option.
>> > >> When we select Safe Mode it progress into Safe Mode and operates in
>> > >> the
>> > >> mode
>> > >> as it should. If we select normal start up it loops again.
>> > >> No error messages have come up. The computer registeres both hard
>> > >> drives,
>> > >> both CD/DVD drives.
>> > >> Right now we cannot figure out what it is doing this. Any
>> > >> suggestions
>> > >> please.
>> > >>
>> > >> Briandp
>> >
>> >
>> >



Re: Boot Loop by cquirke

cquirke
Sat Oct 07 04:12:30 CDT 2006

On Mon, 2 Oct 2006 14:55:02 -0700, Briandp

>I then decided to do a step by step boot up and this is what I found.

> vsdata95.vxd When I did Yes on this it restarted the computer.

That's one of two parts of Zone Alarm that are NOT disabled when you
set Zone Alarm to be disabled. The only way to kill them off is to
disable them in MSConfig, or uninstall Zone Alarm.

They can and do interfere with network traffic when Zone Alarm is
disabled, so the above applies when troubleshooting blocked File and
Print Sharing and other networking hassles.



>------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
>------------ ----- --- -- - - - -

Re: Boot Loop by Dan

Dan
Sat Oct 07 08:29:50 CDT 2006

cquirke (MVP Windows shell/user) wrote:
> On Mon, 2 Oct 2006 14:55:02 -0700, Briandp
>
>> I then decided to do a step by step boot up and this is what I found.
>
>> vsdata95.vxd When I did Yes on this it restarted the computer.
>
> That's one of two parts of Zone Alarm that are NOT disabled when you
> set Zone Alarm to be disabled. The only way to kill them off is to
> disable them in MSConfig, or uninstall Zone Alarm.
>
> They can and do interfere with network traffic when Zone Alarm is
> disabled, so the above applies when troubleshooting blocked File and
> Print Sharing and other networking hassles.
>
>
>
>> ------------ ----- --- -- - - - -
> Drugs are usually safe. Inject? (Y/n)
>> ------------ ----- --- -- - - - -

Thanks Chris. BTW, does Zone Alarm Professional fully unistall or must
a user manually remove registry entries.

--
Dan W.

Computer User

Re: Boot Loop by cquirke

cquirke
Sat Oct 07 14:00:37 CDT 2006

On Sat, 07 Oct 2006 07:29:50 -0600, "Dan W." <spamyou@user.nec> wrote:

>Thanks Chris. BTW, does Zone Alarm Professional fully unistall or must
>a user manually remove registry entries.

I don't know... ZA is a moving target (i.e. high velocity of
subversion changes, right up there with Winamp) and I haven't paid for
and thus don't use the Pro version.

I think ZA's OK on cleaning itself up (unlike Norton, for example).
The more common problem is disabling ZA while leaving the two code
files active, and expecting this to stop ZA from affecting things.

You may well find the answer varies with ZA version, too.



>------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
>------------ ----- --- -- - - - -

Re: Boot Loop by Briandp

Briandp
Mon Oct 09 13:55:02 CDT 2006

Thanks everyone for your help. I have been walking through this thing bit by
bit and have found something that I have never come across before. Not that
I have that much experience.

In the Safe Mode, I was reviewing the drivers for the drives simply because
nothing else has worked and I still am fighting the action of an fdisk job.
I found the following in:

Control Panel- System- Performance-

Memory: 256.0MB of RAM
System Resources: 79% Free
File System: Some drives are using MS-DOS compatibility
Virtual Memory: MS-DOS compatibiltiy mode
Disk Compression: Not Installed
PC Cards (PCMCIA): No PC Card sockets are installed

Then the following was listed:

Compatibility mode paging reduces overall system performance
Drive A is using MS-DOS compatibility mode file system
Drive C is using MS-DOS compatibility mode file system
Drive D is using MS-DOS compatibility mode file system

I'm not sure, but I have a feeling that this is my problem. The bigger
problem is that I have no idea as to what to do about it or correct it. The
Help information advises me to go the the "Config.sys" and/or the
"Autoexec.bat" files to correct the problem. I could use some step by step
direction here. How do I get there and what do I do.

Hate to bother you guys with this worn out problem, but I'm learning so
much. Hope this is the animal that will end this.

Briandp

"cquirke (MVP Windows shell/user)" wrote:

> On Sat, 07 Oct 2006 07:29:50 -0600, "Dan W." <spamyou@user.nec> wrote:
>
> >Thanks Chris. BTW, does Zone Alarm Professional fully unistall or must
> >a user manually remove registry entries.
>
> I don't know... ZA is a moving target (i.e. high velocity of
> subversion changes, right up there with Winamp) and I haven't paid for
> and thus don't use the Pro version.
>
> I think ZA's OK on cleaning itself up (unlike Norton, for example).
> The more common problem is disabling ZA while leaving the two code
> files active, and expecting this to stop ZA from affecting things.
>
> You may well find the answer varies with ZA version, too.
>
>
>
> >------------ ----- --- -- - - - -
> Drugs are usually safe. Inject? (Y/n)
> >------------ ----- --- -- - - - -
>

Re: Boot Loop by Mike

Mike
Mon Oct 09 14:23:36 CDT 2006

In Safe Mode only a minimal driver set is loaded with the result that your
drives will always be in compatibility. Just as for the same reason you
can't use your CD-ROM in safe mode.
--
Mike Maltby
mike.maltby@gmail.com


Briandp <Briandp@discussions.microsoft.com> wrote:

> Thanks everyone for your help. I have been walking through this
> thing bit by bit and have found something that I have never come
> across before. Not that I have that much experience.
>
> In the Safe Mode, I was reviewing the drivers for the drives simply
> because nothing else has worked and I still am fighting the action of
> an fdisk job. I found the following in:
>
> Control Panel- System- Performance-
>
> Memory: 256.0MB of RAM
> System Resources: 79% Free
> File System: Some drives are using MS-DOS compatibility
> Virtual Memory: MS-DOS compatibiltiy mode
> Disk Compression: Not Installed
> PC Cards (PCMCIA): No PC Card sockets are installed
>
> Then the following was listed:
>
> Compatibility mode paging reduces overall system performance
> Drive A is using MS-DOS compatibility mode file system
> Drive C is using MS-DOS compatibility mode file system
> Drive D is using MS-DOS compatibility mode file system
>
> I'm not sure, but I have a feeling that this is my problem. The
> bigger problem is that I have no idea as to what to do about it or
> correct it. The Help information advises me to go the the
> "Config.sys" and/or the "Autoexec.bat" files to correct the problem.
> I could use some step by step direction here. How do I get there and
> what do I do.
>
> Hate to bother you guys with this worn out problem, but I'm learning
> so much. Hope this is the animal that will end this.


Re: Boot Loop by walter666

walter666
Mon Oct 09 14:59:23 CDT 2006

As an engineering associate of mine used to say years ago, "It makes no
difference what you do--it's gonna kill you."

> ------------ ----- --- -- - - - -
> Drugs are usually safe. Inject? (Y/n)
> ------------ ----- --- -- - - - -



Re: Boot Loop by Briandp

Briandp
Wed Oct 11 12:10:02 CDT 2006

Just to let you know, I was able to do a work around and salvaged everything.
In stalled a third drive and loaded the OS and then cleared the old drives
of the important programs and data and cleaned them up. Working fine at this
point in time.

Thanks for your help and imput.

Briandp

"walter666" wrote:

> As an engineering associate of mine used to say years ago, "It makes no
> difference what you do--it's gonna kill you."
>
> > ------------ ----- --- -- - - - -
> > Drugs are usually safe. Inject? (Y/n)
> > ------------ ----- --- -- - - - -
>
>
>