Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows 98 / General Topics / November 2007

Tip: Looking for answers? Try searching our database.

Win 98 protected mode startup trouble

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
bob urz - 27 Nov 2007 00:46 GMT
I am working on a Compaq presario 7000 with amd 800MHZ 128mb ram machine
that has developed a strange start up problem. It won't start up in
protected  (normal) mode). i cleared some junk off the machine with no
change by adaware and AV scans. sometimes, it would start with a IOS
error and halt. most of the time, it just bounces you back to safe mode
which it will start in and run now. i tried disabling devices in the
hardware profile, but no change. now, it i do a step by step start up by
using the F8 start up before it boots, i can get it to start normally.
but if i reboot and don't do the same step by step, it kicks me back to
safe mode. boot log in step by step shows all ok. What could cause this
kind of no protected mode behavior? i also disabled DMA in the HD and
CD, but this did not solve the problem.

Bob
bob urz - 27 Nov 2007 02:57 GMT
> I am working on a Compaq presario 7000 with amd 800MHZ 128mb ram machine
> that has developed a strange start up problem. It won't start up in
[quoted text clipped - 10 lines]
>
> Bob
update on bootlog.

when i step through manually on F8 boot, no load failures.

If i try to do a normal boot with bootlog, all is well up until the
fonts. load Display resources ini OK, then 97 fonts are Loadfail with
code  016
14 foreign fonts then load OK after the massive true type load failures.
 It then gets down to
[00149a38] starting unknown (htreereserved\0)
[00149a38
[00149a3a]
[00149a3a] enumerating unknown (Htree\reserved\0)

Then the boot log stops.
On the step through manual boot it continues on with no failures then
boots. Seems like something is not initializing quickly enough?
I had two memory chips in the machine and swapped them, but no change in
symptoms. Does not seem to be any memory timing settings in this old bios.

Bob

Bob
PCR - 28 Nov 2007 04:24 GMT
|> I am working on a Compaq presario 7000 with amd 800MHZ 128mb ram
|> machine that has developed a strange start up problem. It won't
[quoted text clipped - 20 lines]
| 14 foreign fonts then load OK after the massive true type load
|   failures. It then gets down to

I don't get font failures in mine, but I've read that it could be normal
for some machines & should not prevent a boot. On the other hand, going
by...

http://www.google.com/search?hl=en&q=HTREE%5CRESERVED%5C0&btnG=Google+Search
Google finds about 613 for HTREE\RESERVED\0.

..., it does seems the font failures seem to accompany the
HTREE\RESERVED\0 part of it in other complaints. I'm not sure what to
think. Can it be looking for all those missing fonts at boot is putting
an extra strain on the hard drive?

| [00149a38] starting unknown (htreereserved\0)
| [00149a38
| [00149a3a]
| [00149a3a] enumerating unknown (Htree\reserved\0)

Those lines are normal, but you should get another afterwards...

[0017B71B] Starting Unknown (HTREE\RESERVED\0)
[0017B71B] Started Unknown (HTREE\RESERVED\0)
[0017B71B] Enumerating Unknown (HTREE\RESERVED\0)
[0017B71B] Enumerated Unknown (HTREE\RESERVED\0)

| Then the boot log stops.

Normally, the last thing it was trying to do is the culprit.
HTREE\RESERVED\0 may be referring to files on the hard drive.

| On the step through manual boot it continues on with no failures then
| boots. Seems like something is not initializing quickly enough?

It could be as you suspect. Maybe the hard drive is having trouble
spinning up to full speed quick enough.

| I had two memory chips in the machine and swapped them, but no change
| in symptoms. Does not seem to be any memory timing settings in this
| old bios.

I wouldn't willy-nilly do everything I read in that Google search. But
it wouldn't hurt to check the hard drive per this ancient post of
glee's...

.......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.jsp?locale=en-US&name=PowerMax_4.23&vgnextoid=
a37d8b9c4a8ff010VgnVCM100000dd04090aRCRD

or
http://www.majorgeeks.com/Maxtor_Powermax_d1386.html
Seagate SeaTools for DOS:
http://www.seagate.com/www/en-us/support/downloads/seatools

Signature

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

After that, maybe a Scandisk/Defrag will help to make files more quickly
accessible during boot. BUT don't let them constantly restart. If they
try, post back for a cure. Also...

I must warn that Scandisk may not do a great job when there
is a great one to do...
http://cquirke.mvps.org/9x/scandisk.htm
Therefore, perhaps UNcheck "Automatically fix errors" on it's front
screen. It will then ask whether you want each error fixed. If it
sounds truly horrible, say "No!", and post the log. The log will be
"C:\Scandisk.log".

| Bob
|
| Bob

Signature

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

Ben Myers - 29 Nov 2007 19:07 GMT
> I am working on a Compaq presario 7000 with amd 800MHZ 128mb ram machine
> that has developed a strange start up problem. It won't start up in
[quoted text clipped - 8 lines]
> kind of no protected mode behavior? i also disabled DMA in the HD and
> CD, but this did not solve the problem.

Press the F8 key during bootup and select "Logged".  Then examine the
"c:\bootlog.txt" file.

Ben
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.