Log in

No account? Create an account
an albuquerque not animate be armada. [entries|archive|friends|userinfo]
Okrzyki, przyjaciel!

[ website | My Website ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Geek Time [Jul. 31st, 2003|08:30 am]
Okrzyki, przyjaciel!

Well it took a while, but XP installed on my Celeron 466 MHZ computer.

Of course, a problem-free install was not to be. After I installed Service Pack 1, Windows Update stopped working. I flailed around a while trying various fixes suggested by Microsoft to no avail, so then I just reinstalled XP from scratch on top of XP, which seems to have done the trick -- I left update running when I went to work this morning ... I did download a registry cleaner which found all sorts of gobbledygook in the registry so maybe that helped.

I did learn something interesting something about how Windows Update works: It depends on Windows scripting, and script files have a '.js' extension. One thing certainly wrong with my system the first time I installed XP was that the file association for '.js' files got lost, so they were set to get opened by Notepad.exe. Notepad, for all it's virtues, doesn't know shit about installing Windows patches. That might be why I haven't gotten the Echo Mia drivers to install yet. I'm hoping I won't have any trouble with that.

Another XP anecdote -- I was helping someone at work today, who has one of those cute IBM thinkpads with the 12" LCD. I noticed she was running XP, so I looked at Control Panel/System and it turns out she's running a 500Mhz PIII with 180 Mbytes of memory. It didn't seem that slow either, and it got even faster when I showed her how to turn off all the visual effects. I wouldn't be eager to run XP on anything slower than my 466 Celeron, but I bet you could do OK for everyday email and webbrowsing stuff in XP on a PII 233MHZ with 128Mbytes of memory. It would just take a long time to boot and get the browser and Outlook open. So Microsoft may have done a better job with XP than anyone's giving them credit for.

(Deleted comment)
[User Picture]From: chaircrusher
2003-07-31 08:51 am (UTC)
1) there is no advantage to XP Pro unless you have a dual-CPU system.

2) Laptop updates are scary; Dell tweaks the OS install quite a bit. That being said people here at work do crazy shit, like re-partition the laptop hard disk and dual boot XP and Linux.

3) Point Frank at http://www.musicxp.net/ which is pretty comprehensive on XP audio tweakage.

3) Tell frank to e-mail me if he needs any 'help'

(Reply) (Parent) (Thread)
From: meperidine
2003-07-31 12:15 pm (UTC)
I dual boot linux and xp corp on my laptop for very understandable reasons and I haven't run into a problem yet.

I see where it could be risky though for some people...
thank god my box is custom :D
(Reply) (Parent) (Thread)
(Deleted comment)
[User Picture]From: chaircrusher
2003-07-31 07:32 pm (UTC)

shit going wrong

well shit goes wrong tristan; shit goes wrong. one copes.

I'm comparing this to installing windows 2.0 on a 286 15 years ago. xp is like a cool bath by comparison.

Shit goes wrong on macs too!
(Reply) (Parent) (Thread)
[User Picture]From: jawngee
2003-07-31 09:11 pm (UTC)
That's not true. XP home doesn't have remote access (terminal services), disconnected network browsing, and you can't join XP home to a domain controller.

Which if fine for a basic peer network, but once you want to set it up proper, you're going to have to go pro.

None of this is probably applicable to you, but if your a developer and you want to mimic a production environment, or you have a home network with more then 3 peers, the DC route is the best way to go.
(Reply) (Parent) (Thread)