Re: Question on Windows Server 2003

In article <a3h4j19cs9hdt77nm6r2vva7ruac85qtoa@xxxxxxx>, Onideus Mad
Hatter took the hamburger, threw it on the grill, and I said "Oh Wow"...

> On Thu, 22 Sep 2005 00:13:45 -0500, Noodles Jefferson
> <silverbells@xxxxxxxxxxxxxx> wrote:
>
> >> <snip>
> >>
> >> How long did you wait? Might try letting it sit for 4...5
> >> hours...maybe longer.
>
> >4 or 5 days, it isn't gonna matter.
>
> Um, yeah, actually it does. One time I had this piece 'o junk 75Mhz
> Pentium unit that I was installing Win95 on and it took 14 hours to
> get through the install, just hung up and looked like it was froze,
> but nope, it eventually sorted itself out.

Well, it wasn't a 75Mhz laptop. It was a new Dell laptop.

> Encountered similar
> situations many other times (although that was the longest).
>
> >It stops reading the install disk.
>
> ...well that doesn't mean anything. It's not like that's gonna tell
> you if it's having some kind of memory or processing error.

It didn't tell me anything. When through the first three steps, gets to
installing devices/drivers/something else I forget, counts down the
timer to 34 minutes remaining, little green bar underneath's at just
over a third. No message, no nothing. Just stops. Maybe letting it just
run for a while will work. Not seeing it but hey, could happen so if she
comes back, I'll relay that.

>
> >It hits this certain spot and it stops reading the disk, period.
>
> ...WHICH certain spot.

The certain spot I've been talking about.

>
> >You can tell when it's just sitting and not doing anything. I can anyway.
>
> *shakes head*
>
> Jesus...

What? It's that hard to detect when it's not doing anything? Not really.
I've seen enough proggies stall out enough to know what it looks like.

>
> >> Of course there's a lot of other factors, for
> >> example when it supposedly "locks up" what happens when you press num
> >> lock? Does the lil light turn on and off?
>
> >No Matty, num lock didn't do anything.
>
> ...what do you mean "didn't do anything"

I have to explain didn't do anything?

> , I asked you a plain fuckin
> simple question, does the light stay on, or does it turn off and
> on...yeesh, where is yer head today? You remind me of the people who
> used to call up for hardware support at Sykes.

Happily, I don't need your support. Those poor, poor people. I can only
imagine what talking to you trying to resolve some issue must have been
like.

>
> >Ctrl-alt-del didn't do anything either.
>
> That doesn't mean it's locked up.

Not locked up, stalled out. Install program stops.

>
> >Or hitting the spacebar,
>
> ...why on earth would you be hitting the space bar?
>
> >nor making a face and curling my fingers. It stalls out and stops
> >reading the disk.
>
> "stalls out", huh? *rolls eyes*

Stalls out.

>
> >> If yes, then it's not
> >> locked up. Also, is it trying to read from the disk (I assume CD/DVD
> >> drive) when it supposedly locks up? Is there a discernable pattern in
> >> the noises/activity lights?
>
> >Yes. Everything works normally then it stops. No error message, no
> >nothing. Just stops.
>
> Well if it's actually locking up it's probably some kind of memory
> fuxor...although it depends on WHEN it's doing it. For example if
> it's doing it while it's detecting hardware...yeah, probably not a
> problem with the memory, but a specific piece of hardware.

It did it during that phase of the install but it doesn't say exactly
what it's doing beyond the catch-all installing
devices/drivers/something else with a little green bar underneath it.
The little green bar stops at a little over a third and say there's 34
minutes remaining. That's it.

>
> >> If yes it could indicate that it's stuck
> >> in a loop, like the CD is fucked and it can't read from it...of course
> >> at that point it could also be the drive...or the drivers...or about 7
> >> other things.
>
> >Yeah, could be. Looked at the disk, seemed okay. No obvious scratches,
> >smudges or the like. Then again, maybe the copy wrote bad writing the
> >disk, maybe it's a buggy piece of ***, dunno. Never dealt with
> >winserver 2k3 before. Don't know *** about her computer. Had the BIOS
> >restore the original configuration on the last attempt, same thing.
> >It's the OS install, not the BIOS.
>
> Really at this point one would need to know the EXACT point at which
> is seems to stop functioning.

Which it doesn't give me.

>
> >> From my perspective she ought to find someone like me to *** her up
> >> the ass for 3 or 4 hundred dollars and maybe a few years down the road
> >> she'll wizen up and realize she's training for the wrong profession.
>
> >There's more than the just the networking aspect of programming now. I
> >know what I know because I'm a freak on my OS. Pretty much everything I
> >learned was out of necessity. Had to go find out or else be bummin'.
> >Not everyone's like that though.
>
> Yes well everyone who isn't like that shouldn't be attempting a career
> in the computer industry, their failing stupidity is just a mess that
> people like me tired of cleaning up.
>
> >It's why I'm there at the rat lab.
> >***, I don't mind taking a shot at it. I just couldn't help her all
> >that much. I can't do much if I can't get to desktop or a command
> >prompt.
>
> No offense, but you should see about getting out of the lab and doing
> more hands on repair stuff.

Yeah, I know. Next semester's gonna be linux, networking 1 and haven't
decided on the other two yet.

> Lab duty will make ya good at Solitaire,
> but not much else.

It's good when I have a lot of homework to do.

> Most of my knowledge comes from the 3 years I
> spent doing repair and networking in high school. After installing a
> dozen different operating systems on 7 to 8 hundred machines a couple
> thousand times over the course of the run you eventually encounter
> just about every imaginable problem.
>
> >> If she weren't a deficient going for the wrong career the first thing
> >> she ought to do is check her BIOS settings, make sure everything is
> >> peachy (of course she'll actually need to UNDERSTAND what all those
> >> different settings do and why) after that she ought to try installing
> >> it on another box, to see if it's the CD itself that's fucked.
>
> >Her BIOS was fine.
>
> Forgive me if I don't just take your word for it...although personally
> I never trust anybody until I've actually seen it for myself. A lil
> hint for ya too...switching to one of the BIOS's default
> settings...not always such a good idea...in fact that'll usually
> create MORE problems.
>

Didn't create problems, didn't solve problems.

> >> If it
> >> works, then it's a problem with the laptop. At which point I'd go
> >> through the install process and find out EXACTLY where it's messing up
> >> and then go from there.
>
> >This may be her only computer. If there is another one, can you
> >seriously recommend installing it on the second computer when you don't
> >know if it's disk or whatever else?
>
> ...what school is this exactly? I mean every school I've been to,
> both high school and college have all had hardware labs where you can
> go in and futz around to your hearts content.

I don't work in a hardware lab.

>
> >Personally, I don't think her
> >computer's up for it. Something's just not allowing the changes that
> >the install's making. Wrong hardware configuration maybe but that's
> >just a pure guess.
>
> Like I said, I would need to know the EXACT point at which it stops
> working to even venture a semi viable guess.

Exactly.

> And like I said, it
> might just need to sit and be left alone. Even if you think it's not
> doing anything, that doesn't mean that it isn't. You really can't
> tell...not unless yer Miss Cleo.

She should just recover using whatever CD's came with laptop. If it
doesn't like the install, it's probably something she isn't going to be
able to resolve easily and quickly anyway. Better just to stick to the
original OS.


--
Noodles Jefferson
mhm31x9 Smeeter#29 WSD#30
sTaRShInE_mOOnBeAm aT HoTmAil dOt CoM

"Our earth is degenerate in these latter days, bribery and corruption
are common, children no longer obey their parents and the end of the
world is evidently approaching."
--Assyrian clay tablet 2800 B.C.



.