Gary
Tue May 13 22:31:03 PDT 2008
Laptop or box (can't juggle so good these days), it's an "unknown" mess,
with lots of possible problems beyond those covered by your suggestions. If
you want to focus on the problem as presented, fine, but OP *should* start
completely over, starting with investigating make/model for anything
pertinent. If it's a standard "whitebox" with a standard installation CD, it
should be repartitioned. All hardware should be identified and drivers
located. If the problem repeats, at least one is operating from a known
environment. At *that* time I would start looking into your log files, etc.,
but until then, it's a near probable waste of time.
Of course, my guess is that OP is Dan and the whole case is a fantasy
hatched from whole cloth. He's good at that and he's being particularly
squirrelly. Haven't seen him play this cat & mouse game more than just a
little bit in the past. By now he's usually posting long stories under his
real name.
--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com
"MEB" <meb@not here@hotmail.com> wrote in message
news:OM2Ez$XtIHA.4076@TK2MSFTNGP06.phx.gbl...
> setuplog.txt can perform two functions to diagnose - the *date* would
> indicate whether it is recent or from some old installation and when - the
> failed issues contained within would be the devices which setup had issues
> with and tried to *avoid*... taken in conjunction with the other files
> there
> MAY be other indications of why it is stuck..
>
> The other files mentioned could also be useful, for the reason for their
> creation.
> *detlog.txt is created when new hardware is detected, OR present
> configuration is changed.
> *detcrashlog.txt MIGHT contain the failed hardware issue.
> *bootlog.txt would show problem devices or other
>
> Safe Mode, if accessible, could provide useful information, AND provide a
> method to remove any problem issues.
>
> What makes Gary think this is a laptop, "then gave me the box."
>
> IF you have no disks for "the box" we would need to know the make and
> model
> [proprietary or not], attached hardware, and any adapter cards. Also, what
> is the system trying to constantly install?.
>
> --
> MEB
http://peoplescounsel.orgfree.com
> --
> _________
>
> "Gary S. Terhune" <none> wrote in message
> news:%23MK1xyWtIHA.4952@TK2MSFTNGP05.phx.gbl...
> | AFAIK, that message only appears during installation of Windows 98.
> Since
> | you don't say you're stuck trying to reinstall Windows, I can only
> assume
> | the previous owner ran Setup. Perhaps even reformatted, first. So, we're
> | back to, "Do you have the installation CD?" And, yes, Don's advice is
> not
> | bad, but if you're dealing with someone else's abortion, I'd start
> | completely over, and if I'm going to do that, a security wipe makes
> sense
> to
> | do first, then reformat (or vice-versa.)
> |
> | And the problem, IIRC, is usually a royally failed hardware install,
> | suggesting wrong drivers, improper preparation for installation, and who
> | knows what other issues, depending on make and model of the system. Like
> it
> | might be that it can only be reinstalled using the proprietary Restore
> CD
> | but your boss didn't have the right one and tried a different one...
> |
> | What's the make/model of your laptop?
> |
> | --
> | Gary S. Terhune
> | MS-MVP Shell/User
> | www.grystmill.com
> |
> | "schmenge" <schmenge@discussions.microsoft.com> wrote in message
> | news:F7320C1C-4336-4948-998C-E4CD37CD5377@microsoft.com...
> | > Thank you, kind folks. The last 2 replies are more promising; I hate
> to
> | > re-install unless there are no options.
> | >
> | > "MEB" wrote:
> | >
> | >> Check autoexec.bat, config.sys, msdos.sys, and check for
> setuplog.txt.
> | >>
> | >> Files which might be indicative:
> | >> Bootlog.txt - create one by selecting it from the Menu [press F8
> | >> repeatedly
> | >> during boot]
> | >> Detlog.txt - detection log
> | >> Netlog.txt - network detection
> | >> Setuplog.txt - setup information created during installation
> | >> Detcrash.log - detection crash log - obvious
> | >>
> | >> Trying to start in SAFE Mode might let you diagnose issues which may
> be
> | >> affecting the normal startup. Rapidly tap F8 during bootup, choose it
> | >> from
> | >> the Menu.
> | >> MSInfo might provide you with the machine history that might provide
> | >> additional clues. Checking Device Manager while in Safe Mode, delete
> any
> | >> devices that are not still included in the system.
> | >> ASD [automatic skip driver agent] also might be of interest or use.
> | >>
> | >> You also might want to check for corruption of the registry by
> running
> | >> scanreg /fix at the DOS prompt..
> | >>
> | >> --
> | >> MEB
http://peoplescounsel.orgfree.com
> | >> --
> | >> _________
> | >>
> | >> "schmenge" <schmenge@discussions.microsoft.com> wrote in message
> | >> news:88945D34-0E13-4603-88B6-08A30194B0E3@microsoft.com...
> | >> | Every time I try to boot my computer, I get the message that it's
> | >> "preparing
> | >> | to run windows for the first time". I go through that process and
> let
> | >> it
> | >> | detect devices and install drivers, but when I restart I get the
> same
> | >> message
> | >> | again and must repeat the detection process. I remember from a
> while
> | >> back
> | >> | that setup makes some changes to some boot files to reflect that it
> is
> | >> first
> | >> | boot, but I can't recall which files. Can anyone help with this
> issue?
> | >> It's
> | >> | Windows 98 SE, and the computer was given to me by a previous
> owner;
> he
> | >> used
> | >> | it for business and removed all his files then gave me the box.
> | >> |
> | >> | Thanks in advance.
> | >>
> | >>
> | >>
> |
>
>