B
Bob Bailey
As for your other post, much is displayed about your character.
1) Outhouse Excess user.
2) Top poster.
3) Quotations in the signature.
4) [MVP].
Conclusion:
Shit for brains.
As for your other post, much is displayed about your character.
The Ghost In The Machine said:In comp.os.linux.advocacy, (e-mail address removed)
<[email protected]>
wrote
If one squints real hard, it sure appears that way. However,
Microsoft still gets paid, methinks.
How do the manufacturers of the $250 clones stay in business? Even with
the reduced rate that doesn't leave a lot for hardware.
How do the manufacturers of the $250 clones stay in business? Even with
the reduced rate that doesn't leave a lot for hardware.
Given that under Win2k you'd do *exactly* the same thing if you have a
corrupt registry (and really, it's very simple - I can't imagine why
you had a problem - you probably didn't know how to fix the registry
once you'd booted from the original version found in
c:\windows\repair), so I don't see why you say Win2k is any different
here.
Safemode didn't work, I'm assuming. What actually happened with the
machine? What was the error?
BC said:Since the Dell 2400 didn't have a convenient floppy drive
to use, I took out the hard drive and attached it to a
Win2k system to manipulate the registry hive. That got
me nowhere fast except to an unknown Administration PW.
Since it was a spare PC that had been infected and cleaned
of worms before and had nothing important on it, I decided
the time would be better used to wipe it and reinstall.
The end result is that my friend wants me to do the same
for all his XP PC's -- the 2400 is now easily the fastest
workstation in his office despite it having the slowest
hardware.
Which I suspected would happen....
Since their DOJ loss, that's no longer the case. Manufacturers no longer
have to pay for a Windows license on computers sold without Windows.
Mark said:["Followup-To:" header set to microsoft.public.windowsxp.general]
BC said:Since the Dell 2400 didn't have a convenient floppy drive
to use, I took out the hard drive and attached it to a
Win2k system to manipulate the registry hive. That got
me nowhere fast except to an unknown Administration PW.
Since it was a spare PC that had been infected and cleaned
of worms before and had nothing important on it, I decided
the time would be better used to wipe it and reinstall.
The end result is that my friend wants me to do the same
for all his XP PC's -- the 2400 is now easily the fastest
workstation in his office despite it having the slowest
hardware.
Which I suspected would happen....
2 little things:
1. Make sure you have the activation information, or you could
be very embarrased as you run through your Microsoft Windows
reinstallation routine.
That was unintentional -- I was just doing a reply to2. Please don't x-post.
Me thinks I know a wee bit more about registry fixin'
than you.
While in theory this sort of problem can
happen to Win2k, I've never seen it. WinXP, though....
The exact error was:
Windows XP could not start because the following file is
missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
Since the Dell 2400 didn't have a convenient floppy drive
to use, I took out the hard drive and attached it to a
Win2k system to manipulate the registry hive.
That got
me nowhere fast except to an unknown Administration PW.
Since it was a spare PC that had been infected and cleaned
of worms before and had nothing important on it, I decided
the time would be better used to wipe it and reinstall.
The end result is that my friend wants me to do the same
for all his XP PC's -- the 2400 is now easily the fastest
workstation in his office despite it having the slowest
hardware.
Which I suspected would happen....
-BC
I highly doubt that. Your own words here belie the point.
I've seen it in any NT-based OS, I hate to say it. Registry
corruption is rare on a per-machine basis, but it happens.
You don't need a floppy - that's what the recovery console is for.
You get to that via CD. Or RIS.... a floppy won't help you at all
unless you have a FAT32 system, which in this day and age is very
rare. I'll assume you didn't know about the recovery console, as
that's a far easier method of doing what you needed to do.
And if you knew as much about the registry as you claimed, you'd know
that you use XPSP1 or later (or 2003) to look at and fix corrupted
registries due to the built-in capability of those OSs to fix common
registry issues immediately after loading said registry. (That's one
reason it's becoming pretty rare to have issues.)
But in any case...continuing on...
Sorry to hear that. Your password, if you followed MS's
documentation, would have been what it was when you initially set up
the machine, or when your vendor initially set up the machine.
Well, Microsoft's RIS can make setting up hundreds of machines as easy
as "Hit F10 (assuming a Dell with PXE-capable NIC), select Network
Card, press enter, fit F12, key in the admin name and password, and
sit back while the OS + all your apps are deployed automatically", but
that's up to you.
Sorry it happened, but you aren't troubleshooting this in a rational
manner. Why not try to find out what the problem is, before you
reformat, particularly if you believe this is hitting multiple PCs?
To do so, follow the MS article (make backup copies of the 4 main
registry files, then copy the originals from \repair into \config)
then boot up. Then take a look at the other 'bad' registry and figure
out what's going on. Use XPSP1 or later, or 2003, too.
BC said:Whoops -- I meant to say that it had already
been "upgraded" to SP2. Not THAT'S bloated
crap. And I understand some companies were
not pleased with some side effects of it....
-BC
Windows XP Home has some artificial limits imposed on its use in
order to justify Microsoft charging more money for XP Pro, which
has those limits removed. If you just have a single home computer,
you won't miss the extra abilities of Pro.
http://www.newegg.com/app/ViewProductDesc.asp?description=37-102-151&depa=0
That would be an OEM version, not a retail version. There may be issues with
support in this case. The last time I tried to get support from MS for an
OEM version they referred me to the OEM. I would not think newegg would be
a great place to get technical support for MS software!
The question is, how did you install SP2?
You arguing about this stuff belies your claim to expertise.
I renamed and saved all the hive files, and tried using the
copies, both ones in the Repair folder and the .sav ones in
various combos and got diddly squat done for my time. Since
I know XP to be an all-too-willing sucker of time (I'm
roughly responsible for about 1000 PC's in very, VERY varied
environments) and since there was no handy-dandy disk image
to reload, and since there was nothing worth recovering on
essentially a spare PC, the obvious solution was to wipe it
clean and and reload everything. Since the PC was also very
sluggish, that would also take care of some performance
issues. I also know from past mucho past experience that
Win2k runs about twice as fast as XP, so.....
As I said, I deal with a lot of PC's in a variety of
environments, some very PC hostile, and to be honest, I
wish Microsoft stuck with Win3.11, at least as a lightweight
alternative OS and just kept improving it. Of all the
flavors of Windows, XP and ME have been the big turkeys.
Duh. I know quite a lot about the half-ass Recovery Console,
but I wanted to run some scripts to automate the hive saving
and renaming, including a Microsoft-supplied one. Since the
Recovery Console inconveniently locks the CD drive and since
the 2400 didn't come with the floppy drive....
Get it now?
I originally opened the 2400 to attach a spare floppy drive,
but decided it would be easier to just pull the hard drive
to directly and much more conveniently examine it.
That was running SP1. Rare my ass. What a bloated, useless
piece of crap upgrade.
It was just when I tried a particular saved hive combo
that didn't work and the following Recovery Console then
asked for a different and totally unknown password.
Have I mentioned yet how half-ass the so-called "Recovery
Console"
That "deployment" thing is high-maintenance crock.
Good
for virus app updates maybe.
Huh?
It's better to keep an
absolutely pure model and deploy images from that to
keep the PC's running clean and fast.
Let people be
responsible for backing up their stuff. The time saved
from updating buggy, increasingly slow PC's is worth
the hassle of full reimaging.
I've seen no improvement whatsoever with SP2. No
noticeably decrease in infection rates, no noticeable
decrease in the rate of critical updates against
hacks. There is that new Security Console, but initially
it didn't recognize F-Prot as an antivirus program. An
update eventually fixed this but you have to wonder
what the hell Microsoft was thinking -- that people only
use McAfee and Norton? The built-in firewall still sucks
compare to the better free ones.
By the way, there is this one very clever bug that's starting
to appear that seems unremoveable by normal means:
it loads up even in Safe mode and can't be deleted. I
know a guy who got it (I forget its name.) I'm going to test
to see if Recovery Console can be used to get rid of it,
but it's absurd to have to do this. Again, this points out
the serious design flaws in XP.
Sufice to say many others disagree with you and have seen massive
improvements - a better security baseline, a more stable system
overall, countless fixes to issues or vendor flaws, and overall a much
better system.
There are many user-enhancements too, including System
Center
(updated required from some vendors) and Windows Firewall,
which is an excellent tool for the majority that had nothing before.
How so? People argue about anything in here. I also don't claim
expertise - I simply doubt your claim, that's all.
Well, if you'd used what was in repair, you'd get what you had when
the OS was set up or when you did your last NTBACKUP.
No test has ever borne that out outside of some *very* contrived
circumstances. Take 2 similar machines, put either OS on, and most
won't tell a difference. Certainly not 2x the speed.
Win3.11 was a POS. Multitasking was only as good as the Mac's
(cooperative!) and no real protected memory space. Horrible.
You don't put those scripts in your core image?
Sounds good.
Sorry you feel that way. Most people don't, outside of COLA, that is.
And it does, in fact, fix the registry when you load it up.
It did exactly what you told it to do, so I fail to see the problem.
Keep the four hive files together at all times - don't mix 'combos'.
How so? Do you know what RIS is?
Huh?
Sysprep works fine too; RIPREP is essentially RIS + Sysprep to get the
core OS plus all your programs on there. Familiar with RIPREP? It
works on a RIS server.
With a roaming profile and centrally stored data, reimaging doesn't
need to cost the user anything like what it did in the old days.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.