Robert Baer wrote:
> * I have Win2K SP2 as initial disk, and the SP4 disk as the upgrade.
> My CPU changed a few times from when i first got Win2K SP2, and i
> noticed that it supported a dual core CPU (my CPU at the time was an
> Intel with only one core).
> Presently i have the AMD Athlon 64x2 dual core processor 5200+, so i
> am assuming that both cores are being used by Win2K but do not know how
> to find that out.
> I have WinXP Pro SP3 which (from your discussion) should definitely
> use both cores and might run faster than what runs now.
In Task Manager, while the Performance window is showing, there
may be a View option to show "one CPU per graph". If you have two
cores and they're enabled, there should be two graphs showing.
You will get the same execution speed from your 5200+ (like when
movie editing), as both Win2K and WinXP can run two cores without
a problem.
Win2K has pathetically slow startup and shutdown. WinXP can have
a slow shutdown, if an ATI video driver is installed, but this can
be fixed with the UPHClean utility.
http://www.microsoft.com/en-us/download/details.aspx?id=6676
What that does, is close open hives in the Registry, allowing
the OS to shut down without a fuss. The functions in that
are native in later OSes. UPHClean is probably invoked near
shutdown.
Win2K has better file caching than WinXP. WinXP accesses the disk
more often, pretending it never read some files on the disk before.
Whereas Win2K performs as well as Solaris or MacOSX on file
caching (and using all system RAM to do it). This kind of
file caching is transparent, and uses RAM not currently
in use for any other purpose. As soon as you attempt to use
system RAM, the (cache) memory is freed up and given to the programs
immediately. So this style of file caching is considered
"free", as in a free lunch. WinXP still has this, only the
lunch is smaller.
>
>>
>> An account on WinXP can belong to the administrator group.
> * Well, since i (very rarely) have a problem with my Win2K OS bitching
> about need of authority "above" whatever i have in fact - when my
> installation scheme (no username or password at logon), i will try a
> scratch HD and install XP PS3 the same way and search around in the
> nominally hidden areas to see if i get the same sass.
As long as you're a member of the Administrator group,
I don't expect a problem for a Win98 style of operation.
>> You don't have to use the actual administrator account.
> * One would think. But it seems that my Win2K install does not give
> administrator powers to everything never mind i am supposedly the
> administrator.
> * I guess that i should expect the same garbage with XP.
> And if so, that means i would have to re-install and _use_ a username
> and password to have real access to that (default) administrator account.
> I hate that because my computer will not boot to the desktop
> un-attended; it will be slowed down by a large amount.
>
You may be able to set autolog using the extended version
of Users and Passwords. Try these commands as administrator.
control userpasswords2
netplwiz
>> Modern motherboards lack floppy interfaces.
> * Yes,i noticed. _BAD_ news, zero excuse as the firmware for floppies
> changed from 2 chips to one chip and then ported to the "do almost
> everything" ASIC on the MB.
> What would be the procedure to make XP SP3 look to a user like (or
> very much) like Win2K?
Usually, there is a "Classic" view option to make some
of the OSes look like older OSes. And if that doesn't
pan out, there are packages you can add to the modern
OSes, to make them look like the older ones.
https://en.wikipedia.org/wiki/Classic_Shell
> Can i un-hide all of the system stuff like i did in Win2K?
Yes. Tools : View should have a similar interface.
And allow extensions to be shown and so on.
> I note there is at least one folder in Win2K that seems to be totally
> inaccessible, and knowing M$ to be ?secretive? that there may be others.
> I like to see what i have.
C:\System Volume Information is where System Restore points hide.
You will likely be denied access in there. I suspect that
area isn't quite as sensitive as Windows 7. I entirely destroyed
a copy of Windows 7 while playing in there (had to restore from
a recently made backup). If you need to get in there, you can
use a Linux LiveCD, if you have an overpowering curiosity.
That's how I got in there in Windows 7, I didn't write to
any file, and yet C: was ruined (unrecoverable). I discovered
some files which seemed to be virtual, large in size, had
exactly zero for a sum.exe run, and yet those attempts at
read operations in the folder, ruined the partition.
The difference between WinXP and later OSes, is the VSS support
(for things like convenient backups) is pretty basic. WinXP cannot
keep a VSS session between reboots, as I understand it. Win7 can,
and then if you mess with the associated files, you can get
in a lot of trouble (as I discovered).
One trick I discovered, is using Task Scheduler, things
you schedule for execution there, run as SYSTEM account.
If something is inaccessible, you might try using
SYSTEM account instead. I think WinXP supports "interactive"
program launches, which later OSes consider a security issue
and they won't allow it. But I think WinXP may allows
cmd.exe to be launched from Task Scheduler and give
you interactive operation as user "SYSTEM". If you
really need to smash something (I did some registry keys
that way), that's an option.
Paul