• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Trying to update with SP1a, getting odd error, need help please :)

G

Gogeta4832

Platinum Member
Okay short and sweet.

First time this has ever happened to me.

I installed XP without a problem.
Downloaded the 125mb full SP1a package.
It verified, unpacked, and got to preparing inventory.

The error I got was "unable to open catalog files" or something very close.
all I know is that it didn't install, but didn't affect anything in the system.
also, I haven't updated any drivers or anything else, just a install of XP, that's it.

anyone know why it would generate and error like this??

any help would be greatly appreciated.
 
I had all kinds of problems with installing sp1 when i had to reload my os too. I ended up slipstreaming sp1 into xp and burned it to a disk so sp1 installs with the os.... might be a good idea if you do a lot of reinstalling your os.
 
Stupid question, but are you logged in as a local administrator? That is the exact error message I get when I try to install as a guest.
 
Hey All,

dunno what exactly the problem was.
I went ahead and updated the drivers for the motherboard, connected to the net, downloaded SP1 through it.
And it installed just fine. Not one problem whatsoever now.

I wonder, I renamed it to just SP1.exe.......would that have caused the problem.??

Oh, and Kappo.....no I wasn't logged in as a guest....I made three titles as admin and each one has full access. 🙂

Just an update to let peeps know I got it fixed, just don't know how.
 

A note to ALL:

If you're running NT, 2000, 2003 or XP Pro and you have a problem with a service pack, update or hotfix you get a free support incident with Microsoft. As a matter of fact the person you speak with will likely be someone from the premier enterprise platforms support team...the expensive guys. MS isn't going to say, "Whoops, sorry our update broke your shiz but you're on your own." (call redhat for that)

Renaming the download shouldn't cause a problem. The actual executable is update.exe

Your windows\svcpack.log file will often tell you exactly what's going wrong.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top