Slashdot Mirror
XP SP3 Crashes Some AMD Machines
Stony Stevenson alerts us to new information on the XP SP3-induced crashes that we discussed a few days back. Jesper Johansson, a former program manager for security policy at Microsoft, is maintaining an ongoing log and support site for users affected by any of several problems triggered by XP3. Machines using AMD hardware, particularly HP desktops, seem to have several modes of failure; others affect Intel machines.
I suppose now we have to wait until "Windows XP Service Pack 3" Service Pack 1 comes out before it becomes usable.
Do it yourself, because no one else will do it yourself. [beta blockade 10-17 Feb]
You see, SP3 is actually a tool to make users believe they should upgrade to Vista. Relax, I'm just being Facetious.
Let us not become the evil that we deplore.
Only had one problem on my Acer Laptop (TravelMate 8210) with SP3, it forgot that I had a wireless card, restarted and been fine since then (almost a week) so I'd say no problems for me
Bah, you beat me to it. I was trying to get it, but I have SP3 installed on my computer and it crashed >.
Headline singles out AMD machines, body indicates that AMD and Intel are equally affected by various modes of crash. Sounds like someone's trying to drum down AMD stock or something... nah, we'd never have a processor partisan writing for Slash would we?
If you can read this sig, congratulations, you have your glasses on!
Rename the topic to say INTEL drivers on HP AMD systems is the cause.
The topic you have makes AMD look bad.
Why is HP useing the same basic image for there amd and intel systems?
What other driver bloat is in OEM systems?
Is INTEL coding there drivers to mess up AMD systems?
AMD legal should take a look at this.
I have SP3 running on my AMD right now and it's works 100%
I installed SP3 Sunday and three problems immediately cropped up that I haven't seen in the years since I first installed XP. First is a stop, BAD_POOL_POINTER 0x00000019 (0x00000020,0x8a231120, 0x8a231158, 0x1a070000). Second is a problem with the HID service not starting. Third is that PaintShop Pro (V7) now cancels all attempt to enter standby mode. Sigh...
I smurf everything and everything I smurf is perfect.
I'm on both an AMD machine and an HP desktop. Good thing I chose to wait a few months before SP3ing myself. (As for my friend, he didn't and now I'm the one laughing)
Who wrote this article? If you combine the headline and the last setence is basically says "SP3 screwes up some AMD and Intel systems." Gee, you think? Totally biased against AMD if you ask me. You don't just kinda mention "oh yeah, it breaks some intel ones too" at the very end after making it sound like AMD has some huge problem.
Google's Super Secret Search Algorithm: SELECT @search_results FROM internet WHERE @search_results = 'good'
Let's see , is there any where else where M$ and Intel conspired to damage anything? OLPC maybe? EEPC?
Nahh these are good companies beyond reproach.
Right......
* Carthago Delenda Est *
Too bad my submission from monday didn't make it, it would have made for some interesting conspiracy theories. AMD and Intel have made the briefs in their anti-trust case public (With heavy censorship^Wediting). One of AMD's contentions is that Intel's compiler is actually written to reduce speed and stability of programs it compiles when said programs are run on AMD processors.
<conspiracy>Maybe Microsoft has a deal with Intel to do the same with SP3 (and other Windows versions/SPs?) or they use Intel's compiler.</conspiracy>
Worth considering.
Do away with our corrupt tax code. Support the Fair Tax
I imaged my whole Windows partition, in preparation for the horrible instability that would be SP3. I then took a deep breath, and started the download, figuring it would take several hours.
It went reasonably quickly, had exactly one reboot (which brought me fully up to date; no "critical updates" after that), and then ran solidly while I played Portal for another five or six hours.
I was almost disappointed.
It was an Intel machine, though.
Don't thank God, thank a doctor!
As I understand it, this only impacts Windows XP users who are running computers with AMD or Intel processors. There is no evidence of SP3 introducing problems on XP machines with alternative architectures.
It's all in the eye of the beholder. To me, the topic says: "M$ can't make software for other architectures than intel." or; "M$ can't make software. Period." Hopefully people read a lot more than just topics though.
HP should NOT be using the same image for their Intel and AMD-based systems. There's always one for the Intel systems and one for AMD systems of each type (So, a DV2000 laptop has two generic system images, one for Intel-based and one for AMD-based. It's almost ALWAYS been this way.)
By the way, this appears to be Microsoft's problem, since HP maintains and is responsible for their own recovery images (all customized for each model and revision of laptop) and their own drivers.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
Care to back up your assertions with evidence?
Do away with our corrupt tax code. Support the Fair Tax
Isn't the original purpose of a service pack to add reliability, rather than take it away?
One would think that by SP3 there would only the most minor bugs left to close, but instead giant new ones are opened. Machines that become unbootable? That's pre-alpha quality stuff.
Something is badly broken with their methodology... no wonder they were trying to do a people grab at Yahoo, the higher ups are probably pulling their hair out by now trying to figure out how to fix their organizational problem and maybe they thought a new project built on BSD (but independent from Apple code) with entirely new staff would bail them out.
You can't send a takedown notice to an already printed newspaper.
not exactly a cut and dry SP3 problem and certainly not an AMD or INTEL issue at all.
people who write this crap need to all be thrown in a cage and be made to rip each other apart.
If you mod me down, I will become more powerful than you can imagine....
"SP3 causes the computer to crash during boot, and Windows XP, by default, is set up to automatically reboot when it crashes. That is why you end up in the endless rebooting scenario."
Nope, no relation at all. After all, crashing is perfectly normal.
"To those who are overly cautious, everything is impossible. "
Yeah because it's definitively Microsoft's fault that HP is packing Intel drivers on their AMD machines. Typical baseless Microsoft Hatred.
I'm waiting for Service Pack 3.11
One data point. Asus M2N-SLI Deluxe w/ 1502 BIOS version and an AMD 64 X2 4600+ is OK so far.
Moderation in everything, including moderation.
The World is our Beta Tester.
Weaselmancer
rediculous.
I got hit by this bug when the patch went live last week on Windowsupdate. As the article states, the solution in was to disable intelppm.sys from safemode. It's a lot quicker if you do it using autoruns. It's too bad this article wasn't posted last week. It would have saved me a lot of trouble shooting time.
"People should be allowed to keep midgets as pets."
- Gov. Jesse Ventura
All in all, it still seems to be faring much better than Vista SP1. For what it's worth, the latter is still disabled on Windows Update for one of my PCs (because of "incompatible hardware or drivers").
Yeah, sensationalism as usual, I've got SP3 running perfectly on an AMD and an Intel system, both with no problems and the same as they were with SP2.
All your base are belong to Wii.
NT4 ran on Alpha, PowerPC, and SPARC, among others, but it wasn't written by their in-house staff. They hired some away from DEC to write it for them.
SP3 works fine for me but it removed my address bar from the taskbar. MS claim somewhere its a compliance thing but that's totally BS as vista has the address bar and the address bar in SP2 will load the default browser (ie firefox).
There are work arounds and third party patches - but this is just annoying.
Quite simply, if MS wanted to keep customers they would create a product with zero problems (or as close as they can get) and push it out at a VERY competitive price. That is how the marketplace is supposed to work. When your namebrand is trashed, you have to compete extra hard. MS seems unwilling to do this, or at least has failed to show that they are trying to do so.
That might just be bad business decisions on their part, but whether it was malicious or stupidity does not matter. In either case the end result is that MS loses more customers. Nobody wanted to hear that MS was losing or soon to be dead a year ago when predictions were rife, but here it is, in your face. MS is consistently failing to either impress or produce quality product. The dragon^H^H^H^H^Hcathedral is near death... is it time for the penny market to celebrate?
Not on your life, it will be time to celebrate when the dried bones of the dragon are used up as party favors. Until then, it is time to keep competing aggressively, and nothing short of that will do. Competition, not patents, drives innovation. Innovation will bring us secure computing at home. A kind of secure that behaves friendly to the end user.
Now, am I bashing MS for pleasure? No, it is because MS products are in their deathbed and nothing short of a complete restart will get them out of it. It does not appear that MS will do that. There is nothing in current or near future activity that shows MS will do anything different from what got them in the death bed to start with. The beast is dieing. There is nothing more to say.
Call that a troll if you will, but the truth hurts sometimes. Do I want it to die? NO! Emphatically NO!!!! Without competition, quality dies. Would I like to see MS slide into a comfortable second place? Yes.... and the reasons are simple, just ask any Linux fanboi for them.
SP3 failed utterly in the face of the current market that MS faces. There is NO excuse for that in business. If you believe the art of war extends to business, MS deserves to be beheaded ungracefully. That is how business goes, so don't bother telling me that I'm a troll.
Support NYCountryLawyer RIAA vs People
I recall some HP machines had serious problems (driver related?) with installing XP2 too.
You should be flogged.
First Vista Post!
Uhh, hello? Anybody still there?
Excuse me, but please get off my Pennisetum Clandestinum, eh!
Installed SP3 on an intel-based machine, no problems at all.
Why anyone would risk the royal PITA of having their machine completely boned and having to spend hours or even days restoring everything to its original state when a simple disc image could restore it back to health in a few minutes is beyond me. Maybe it's because I've spent so many years fixing Windows boxes in repair shops, but the thought of actually sitting at home for all that time trying to fix a boned Windows install just doesn't cut it for me. So I have an image of each machine in my family with a clean install for when I need to clear the "bitrot", and I keep a monthly image made of each machine on a portable drive in case anything breaks and I need to just send it back a few weeks. But that is my 02c on the subject,YMMV
ACs don't waste your time replying, your posts are never seen by me.
Anyone who build Windows XP images that are rolled out onto both AMD and Intel machines should have long ago learned about the stop code 0x0000007E perils that come from the intelppm driver. The root of all evil here is that processors are not plug and play devices as far as XP is concerned and their associated drivers are hardcoded to start at boot time. Why the hell Microsoft has not taken the time to update intelppm.sys to check for a GenuineIntel x86 Family XX Model YY Stepping ZZ ID before touching HW specific registers is a mystery to me (I hope the conspiricy theorists amongst you will regale me with much food for thought).
Why bother? It's just as fast to reinstall Windows (and you can do it on the same partition, so all you lose are a few settings).
I think you missed this one http://www.sysresccd.org
First, this configuration obviously worked fine for SP2. Second, Microsoft controls the driver certification process, so they should be able to ensure that Intel drivers aren't loading on an AMD system. This is a pretty minor fuckup, but it's firmly in MS's lap.
Business. Numbers. Money. People. Computer World.
This story making the rounds with unwarranted AMD-user-scaring headlines is typical of the kind of FUD that Intel shills have been spreading. There is a gaggle of them here on slashdot and most other blogs and boards of any reach. Most review sites with any impact have been bought and paid for.
"Why not? Shouldn't Windows be flexible enough to use a single system image for commonly available hardware?"
Sadly, no. Due to HP's design methodology, the differences between Intel and AMD based systems are vast. Almost none of the hardware is common, minus the video and perhaps the sound. AMD laptops generally use a Broadcom wireless adapter while Intel uses an Intel-branded wireless adapter, for example. Even the SATA controllers use different drivers (different chipsets, after all,) so even more special drivers are required.
I hated working on laptops for just that reason, so many images to remember for each model and variation. I used to keep a copy of just drivers and a fresh OEM install disc, say screw the laptop reimage bench, and get the OS reinstalled far faster than the overloaded GHOST network.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
That's not the only issue with SP3. One of my monitors is rotated 90 degrees (widescreen that I use upright), thanks to the ATI driver's rotate function.
After rebooting following SP3 install, all my monitors went completely berzerk. They fell back to 4 bits colors (I didn't even know there WAS a 4 bit mode), with some weird effects. Also, rotation was not possible.
It took me about an hour to find a way to bring back monitors to decent resolution and colors. I still couldn't get rotation to work, no matter how hard I tried (Combination of card, drivers, update from ATI, etc)
Then finally I google a bit and found a few forums with user complaints of the same type of problem. So I uninstalled SP3, rebooted, and voilà, everything back to normal.
Needless to say, I promply logged back into WSUS and removed SP3 from the approved for installed list.
Sorry I'm late. I was playing an mp3, drove the latency right up.
Yeah, lord knows that when I installed the Intel version of Linux onto my AMD computer all hell broke loose and I had to reinstall from scratch with the AMD version.
Oh, wait. Linux isn't written by retards, and is capable of loading the proper drivers for the system on boot. It can even enable processor-specific workarounds on boot-up if needed.
Windows is fragile enough that upgrading the BIOS can force you to reinstall from scratch. This is a Microsoft problem, no matter how they spin it. After all, it worked prior to SP3 - it should work with SP3.
I guess I don't understand your POV. Just because you had to sit on it for work doesn't mean that's the right way to proceed. All these things have vendor strings and PCI IDs, Windows should be smart enough to ignore irrelevant drivers. Linux boots on all this stuff with a single kernel after all.
Business. Numbers. Money. People. Computer World.
Personally I tried it on my MCE 2005 machine, and didn't encounter this problem, but it fubar'ed the MCE part good and proper. After several hours aggresivly googling & regediting, still no joy, so reverted back to SP2 image.
And the plural of 'datum' is not 'proof'!
What was the point in all the years spent by the PC industry on "Plug & Play", implementing ideas like unique IDs allocated by a manufacturer to their hardware devices and an operating system which can scan these IDs and choose drivers accordingly?
Fuck off you self publicist asshole. No gives a shit about you posting your shit blog for the 50th fucking time.
...any machine !! That's right, pleebes. If you install SP3 it's possible -- now get this -- to FUCK IT UP so that your machine, anyone's machine, won't boot !! "OMFG", you're saying.
Now, for the other 99.9999% of those installing SP3, no problem, but if you are the 1 in 100,000.000000009 -- pray to the holy mother of pearl !! Or switch to Linix. There you can compile your own death.
Sorry for pointing out that your obvious processor of choice is falling behind at an exponential rate and that AMD is going to go out of business before the decade's up.
Or back up your evidence with assertions?
Seven Days with Ubuntu Unity
I'm running Windows XP SP 3 on an AMD machine and I'm doing just fi
Knowledge is power. Knowledge shared is power lost.
Rewrite: "Over time, Microsoft Windows XP tends to mysteriously ... decrease stability and performance (in every way imaginable".
I've experienced that, many times. Windows is unstable. The instability helps Microsoft sell new versions of its operating system.
Summary of the Slashdot article about Windows XP SP3 crashes:
Microsoft has known about one of the underlying problems for a long time. See KB888372. It would have been easy to prevent the crashes merely by having SP3 installation do the work mentioned in the KB888372 article. However, apparently because of work avoidance, or an attempt to discourage people from using Windows XP, Microsoft did not do the necessary work.
"XP ain't done until AMD won't run"
Windows has had trouble with AMD since at least Win2k. It would stop responding when you used an AGP card, namely Nvidia GeForce 256's and Matrox G400's (not that they were popular or anything...) with an AMD Athlon processor, due to the memory allocated by the video adapter driver becoming corrupted. It took a manual registry edit plus reboot to fix it.
...Rob
The American Dream isn't an SUV and a house in the suburbs; it's Don't Tread On Me.
Or how about that this problem originates from the manufacturer trying to cut corners rather than deploying two separate images for Intel or AMD processors. Besides, I doubt this problem has anything to do with the current issue being discussed in the forum, even though it has similar symptoms. The link you gave discusses a symptom that applies to SP2 users, not users who ran SP2 fine then 'upgraded' to SP3 and crashes.
"The instability helps Microsoft sell new versions of its operating system. "
That would be fine if the newer versions were stabler. My experience with Vista has left me longing for XP.
CommentBot 0.7a running with args "-module irritate,disagree -target random"
You can do it - if you make sure that you're building an install image with the correct OEM drivers on board, booting with the generic HAL, etc. It sounds like HP isn't doing what they'd need to do to build a actual "universal" image. Hardly surprising - back when we used to buy HP where I work, HP was of little help preparing a custom system image for 500+ identical business computers. They just weren't set up to deal with it - we had to send an employee to HP. Contrast that with IBM/Lenovo - they actually know how to do this.
It's certainly Microsoft's fault that their operating system can't figure out at boot-time which drivers are appropriate for the platform it's booting on and only loading those.
Mac OS X and Linux both do this. Why can't Windows?
If he explores all forms and substances Straight homeward to their symbol-essences; He shall not die.
*yawn*
SSDD from you people.
If the driver does not exist on the system, the OS cannot load it. Windows is not going to install an AMD Driver on an Intel System, so the Intel Image would not even have the AMD Driver available.
You bring up Linux, which is interesting because the *only* reason Linux could do this is because it either uses only one driver (bare-min compatibility with both CPU types, which neither AMD or Intel would allow MSFT to include), or includes support for both CPUs separately (referred to in the MSFT world by such as yourself as "bloat").
Care to try again?
I have loaded SP3 on 4 AMD systems, no issues.
I have loaded SP3 on 1 Intel System, system crashed, issues turn out to be the Intel's Video, Modem, and Audio driver issues.
You speak in ignorance.
It's not bloat. It's sound operating system design. I know Mac OS X better, so I can give a good example of how it works on that platform. On Mac OS X, the system has on disk every driver for every system and built-in hardware it supports. From the old G4 modems to the current iMac video cards. The folder containing those "kernel extensions" as they are known is a bit more than 200MB in size on PPC Leopard (10.5.2). That is a pretty insignificant amount of space used on modern systems, I'm sure you'll agree. it would obviously be bloated and inefficient if the system were to load every single one of those extensions every time it booted up. Which is why it doesn't work that way.
When MacOS X boots for the first time, it will scan each and every one of those kernel extensions, and check if the hardware they support is present. If it is, it will load the extension. As it is loading the extensions, it's also building up a cache file of those it needs on this specific system. As it is done, it generates a system-specific UUID with the cache information.
On each subsequent boot, it regenerates the UUID (a quick operation) and compares it to the one stored in the cache. This essentially allows it to see if any hardware changes were made to the system. If it detects no changes, it then loads the extensions listed in the cache file. If it detects that the system has changed, it flushes the cache and starts the process anew as if it had never booted up.
This has the effect of making the first boot after installation of a new system or major update slower, but every boot after is quite fast. It makes for a system that can be universal without any "bloat" loaded in memory, and totally removes the chance things like this SP3 bug would occur.
This works for both built-in kernel extensions and third-party ones, obviously. I'm not saying there's no bloat in OS X, or that it's perfect. But this system of loading drivers only as needed and to refresh the cache as needed is a very nice one, which works very well. Microsoft might do well to learn from it.
If he explores all forms and substances Straight homeward to their symbol-essences; He shall not die.
Why are we both considered trolls? This wasn't even on a machine I put together myself, it came with Windows on it.
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
On my Intel processor / Gigabyte S-series MB, I just don't install SP3. I install all other patches, and it eventually gets what it needs, and stops worrying about SP3.
Andy
Geez, they keep slamming Linux for being "unprofessionally" coded...
Consider yourself spoken to.
I'm installing SP3 now! Save me oh master of Wargames!
All of NT was written by the DEC team, no? And it's the same (mostly very good) kernel code that's running even in vista.
I am trolling
"On Mac OS X, the system has on disk every driver for every system and built-in hardware it supports. From the old G4 modems to the current iMac video cards. The folder containing those "kernel extensions" as they are known is a bit more than 200MB in size on PPC Leopard (10.5.2)" Now try that on Windows, which has had the distinction of supporting *millions* more pieces of hardware. (You think that number's too high? It's most likely *way* too low.) How's about we shipp Vista with 80 DVDs...just so they have the proper drivers. Oh, wait...MSFT doesn't *write* drivers. The Manufacturers do (or don't if they make soundcards). Sure, it's a nice system, but eventually, Apple is going to have to pair it down when the kexts grow to be just a tad more than 200MB. ;) (A Vista example again, I can install Vista on my nVidia RAID without loading drivers, but my 3 year old Lexmark won't work. Ever.) They include the most recent drivers for some of the most popular components (at the time of release) and for components in use by their partners. I don't doubt, once Apple's hardware girth grows, that something similar might be implemented.
I just don't think there'd be any way to apply such a system to Windows, and I really don't see a need for it, even on things like CPU "drivers". If HP had done their jobs right, we wouldn't be seeing this problem. HP took a shortcut and it burned them. One hopes they'll learn.
"The link you gave discusses a symptom that applies to SP2 users, not users who ran SP2 fine then 'upgraded' to SP3 and crashes."
Read the article referenced in the Slashdot story. Also, the Microsoft KB article says:
"APPLIES TO
Microsoft Windows XP Professional Service Pack 2 (SP2)
Microsoft Windows XP Service Pack 3, when used with:
Microsoft Windows XP Professional
Windows XP Home Edition".
The story referenced by the Slashdot story rings true to me. The kind of sloppiness in programming we see from Microsoft sometimes re-activates stopped system services.
1) You are assuming there is an OS market to create a competitive price against, when in fact the business choices are M$, M$ and, well, M$ (unless you count those bit players: Unix, Linux, and Apple).
2) You are assuming and intelligent rational buyer's market, when there is only currently a seller's market (ie in the words of my infinitely wise toddler "You get what you get and you don't throw a fit").
The MS Spin machine will, and has already begun to, spin a new myth around SP3 to dazzle and disarm, and the fiasco will be averted yet again. While in the meantime, it becomes another brick in the crypt of MS among the more educated masses. I'll not argue that Windows is dieing a slow death, but we disagree with perhaps the timespan.
There was no point, Plug n Play never fully worked, s evidenced by Windows XP's behavior to reinstall a driver for a USB device if I move it to a different USB port on the same machine.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
Take an AMD-based image, throw it on an Intel laptop, Windows XP will go "I'm in the wrong machine!!! PIRACY!!!!1!1!" and the computer will lock out. That is all purely Microsoft's fault, not HP or Dell or Toshiba or IBM, it's purely Microsoft's fault. This is why HP has to custom-tailor their system images.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
You suck.
These comments are at least +1 insightful.
If I remember, I'm remodding them up as such when I get mod points again.
XP SP3 is Microsoft's move to get the masses to move to Vista. They have done this before; sabotage software to induce their customers to move to a Microsoft product. This is not the first time that I know of where they sabotage their own product to force an upgrade. The data formats of previous versions of Excel and Word were made incompatible with newer versions of the same products.
Your best bet, turn off the 'Automatic Updates'.
Best regards.
You're confusing installing an OS on a computer vs. installing a pre-installed image.
The former, the OS setup can easily detect the correct CPU type and install the appropriate drivers. The latter is the problem, especially if you take an image of a machine that was install on an Intel system and then lay down that image bit for bit on a harddrive installed on an AMD system.
That's the reason why the HP systems are getting dorked. The image in question was originally installed for Intel system. It would be similar to taking an OSX installed on a PPC based system and laying it down bit for bit for an Intel Mac and expecting it to work. The fact that Intel and AMD are similar enough that the stupidly configured machines actually ran is more amazing than anything else.
Had HP actually installed the OS, there wouldn't be a problem.
You are completely missing the point. The point is not about having every driver available, but about being able to dynamically load them if they are needed on the system you're booting on.
If he explores all forms and substances Straight homeward to their symbol-essences; He shall not die.
Which, as I said...is all well and good, but useless unless you have the driver...which one would expect to be the case for an AMD driver on an Intel OS image....it's pointless. Correct?
"Hardly surprising - back when we used to buy HP where I work, HP was of little help preparing a custom system image for 500+ identical business computers."
That's no longer an issue. If you buy 500 identical laptops, HP has an image for all 500 of them.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
Plug and play, BTW, has nothing to do with a pre-made OS install for the purposes of either system recovery or mass imaging of a new product line. You're thinking about installing an OS on a CLEAN SYSTEM from scratch.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
Excellent information on a potential FUD on a major level. This has the potential to rocik the XP world. Not too scarey if you are armed with the proper information.
Good god, give it break, you pathetic Muckintosh-Linooks weenie!
Just how many big posters of Steve Jobs do you have plastered on your wall of your momma's basement anyhow?
.
- aqk
F U
Sorry-
I've never had a prob with Vista, that I had not experienced under XP, or Win2000.
Of course they stole all the best nav techniques of linux and then added some, but at at least all my devices are supported, so I do not have to do some obscure SUDO -ffg fbt xf=J fr or shit like that.
OK - I'm not some crybaby weenie in momma's basement. I don't have time to fuck around with arcane cmmd-lvl crap. I did that years ago.
And believe it or not, I still dual-boot Linux and Vista. But most of the time is spent on Vista.
Migod you weenies are pathetic.
.
- aqk
F U
(Says me who's adopted a procedure of automatically install XP using a scripted install rather than imaging because XP's implementation of PnP quite simply doesn't, post-install)
I went ahead and loaded up a Vista Ultimate just to run Miro for the TV in my room. After a couple of days it started randomly crashing the machine. Not just Miro, but a complete lockup. It happened several times, where I would reboot, check for updates, and run Miro. I have been running Miro on my MacBook Pro for months and never had a single prolem. My question is, with all this high tech Vista architecture, I am surprised at a silent lockup. I would of expected some exception or other, but with all the protectedness of Vista, a complete lockup is a complete disappointment. I should have known better than to try to use Microsoft stuff for anything, but I didn;t want to waste that Lenovo 3000 J 115 Desktop and I thought using it as a TV would be ok. I guess I will just put OpenBSD back on the Lenovo, as it recognized it as a dual CPU machine and I could make use of it as a server later. What shit Microsoft is serving these days. I am posting anonymously because I am ashamed to still be trying to use this Microshit, and I don;t want people to know who I am.
First I ran the CPUID utility which provided some CPU numbers and stepping information. Then I went to the Intel site and ran their web based CPU identification utility. I tried to plug in the number previously determined, and there wasn't a CPU that matched up. I called Intel and provided the numbers and they wouldn't help me. Five phone calls and eight email messages later they told me that they could not disclose the exact part that was shipped in my system as it was confidential and Dell would have to tell me.
I called Dell four times and emailed seven times and they refused to give me the sSpec number from the chip they used in my machine. They passed me around from department to department, then changed my customer status so I couldn't use regular tech support any more and I would be connected to the chump line. Eventually they told me I must physically remove my CPU chip and read the sSpec number off it. I asked would that void my warrantee and they said YES it would. Eventually I was desperate enough to do just that and after removing the chip and wiping off the thermal transfer jizz, I found that someone had removed the sSpec number with solvent before it was installed.
I will never buy anything else from Dell, or depend on Intel for software engineering support. If I had been from Microsoft, I am sure I would have been given what I needed the first day. After all this, I went Apple Mac and didn't look back. Sure it has an Intel CPU, but I cannot help that Things have obviously changed in the last few years. Engineers used to get a little help from the vendors, but no more. The part number of the chip is a secret, my my.
None. I'm using an HP Hackintosh, because I didn't have 1800 Euros to pay just for a working webcam and Sleep Mode.
Bah, enough replying to that troll. Just posting to point out that AMD is utter crap and I'll say it enough times again. Intel CPUs arebuilt to run at their nominal speed, AMD CPUs are built to run at reduced speeds unless more is needed. My last AMD was a laptop, which fried when it lacked the Amd Processor Support driver, the thing that makes its SpeedStep work. (Yeah, SpeedStep is Intel, but I can't remember the name of the underclocking tech on AMDs.)
Anyway.. What ttriggers the crashes? Do they happen on clean installs of XPSP3? Or only on upgraded Windowses? (Hint : if you upgrade or update any MS software, it will die a slow death, getting slower and slower until your computer refuses to run anything at all. Try running MS Office 2004 on a G4 after you updated it regularly for three years : launch it and weep for an hour, then try to type anything and count the framerate with your naked eyes. It's not that difficult since it's under 1 fps.) That's why I'm asking if it is the Standard issue (don't upgrade/update Windows YOU FOOL!) or it's Microsoft's usual Quality Label. Or to drive people to install OSX (on Pentium4Ds and C2D) or Linux (on AMD crap and older Intels).
Making laws based on opinions that stem up from false informations leads to witch hunts.
Installed sp3 on a clean, brand-new hard drive after initial XP home installation,137+GB. I already had SP2 on my computer and SP3 was automatically downloaded as a update. Asked to reboot system. When I clicked on the reboot-now link, I recieved the blue screen of death. Only flashed for a second so I was unable to see the error code. After restarting computer and @ initial rebooting of my console, I recieved the following error at the time of system startup: BIOS ROM checksum error Detecting floppy drive A media... INSERT SYSTEM DISC AND PRESS ENTER The BIOS copyright notice is loaded before this error. I cant enter the SETUP menu at all to change the boot drive back to my HDD or CD rom. I had previously removed my floppy drive years ago, but after I first recieved error message I went ahead and reinstalled it. Since I only have recovery boots and XP software on CDs I dont have any flops for system recovery. I am not sure what to do next. Any suggestions would be Appreciated. AMD Socket A Duron, M811. KT226A Northridge Chipset, Ultra DMA, AGP Gforce, DDR SDRAM, Award Bootblock BIOS v1....Thanks Ya'll
Blah indeed!
/.ers!
Well, AMD might well be the antichrist.
ALL my Windows systems (Win2K, Xp-Pro and Vista Home run adequately on their respective AMD machines
But-
I cannot seem to install the.. hmmnn latest? Ubuntu 710 on my AMD Duron (currently running Win2000)
Someone, somewhere told me that Ubuntu had probs with some AMD processors. Go figure.
So I am now awaiting my CD of Ubuntu 804 - Ignoble Iguana or whatever it's called...
Perhaps they've solved some of the probs with earlier Ubuntus, but I'm not holding my breath.
BTW my previous comments were done after copious amounts of wine. Rage against the machine! And
.
- aqk
F U
Installed sp3 on a clean, brand-new hard drive after initial XP home installation,137+GB. I already had SP2 on my computer and SP3 was automatically downloaded as a update. Asked to reboot system. When I clicked on the reboot-now link, I recieved the blue screen of death. Only flashed for a second so I was unable to see the error code. After restarting computer and @ initial rebooting of my console, I recieved the following error at the time of system startup: BIOS ROM checksum error Detecting floppy drive A media... INSERT SYSTEM DISC AND PRESS ENTER The BIOS copyright notice is loaded before this error. I cant enter the SETUP menu at all to change the boot drive back to my HDD or CD rom. I had previously removed my floppy drive years ago, but after I first recieved error message I went ahead and reinstalled it. Since I only have recovery boots and XP software on CDs I dont have any flops for system recovery. I am not sure what to do next. Any suggestions would be Appreciated. AMD Socket A Duron, M811. KT226A Northridge Chipset, Ultra DMA, AGP Gforce, DDR SDRAM, Award Bootblock BIOS v1....Thanks Ya'll
I've never trusted imaging; seems too much like asking for trouble. Scripted installs all the way, that's my motto. Granted, this approach probably isn't feasible for OEMs wanting to pre-install. The moral here is to always blow away the pre-installed OEM image and reinstall from the media.