Windows XP Professional SP2 OEM (English) ????

[Pennywise]

certianly

I just switched from Forte Agent 1.93 to 6.0. I'm used to a spell check
after I hit send, it's not happening and I'm not used to it.

 

[Seum]

Thank you again P.W.

Ya, I figure you got screwed on that deal. On purpose, a bad CD.
If you did a scan like Paul mentioned you should find a bad spot or many bad
spots. if you couldn't read the .SIF file in notepad that's pretty much a good
clue it's bad.

I had no idea how to open that .sif file and I accidentally discovered
that Notepad could read it, after I tried four other possibilities.

However, I hadn't a clue how to modify the .sif. If you can tell me how
to do that, I would give my XP CD a last try. Yeah, Paul told me about
it but it seems I was sleeping :-( At times I get woefully distracted.

BTW that post from "Steve" was a reply to me (I posted) that they had added
a .SIF file could be opened by Notepad or any text editor. While I sent you
to that link it never did say it was a text file so I posted a note to them
(it's a good site) http://www.fileinfo.com/extension/sif

While there are many products out to check for errors and recovery of CD's.
I've just always used Isobuster http://www.isobuster.com/ There's a free
version that should at least tell you if it's good or not.

I used Isobuster about 10 years ago and then completely forgot about it.
I have just downloaded it. Thanks for that tip. I guess it would NOT
find the error in the .sif file.

When I did the search for "Bundesgerichtshof Urteil vom 06.07.2000 - I ZR 244/97"
I wanted to read the decision, but all I got at the time were deals on software,
so yes there would be price wars.

I only linked to Win7 to show a huge price difference. XP could be very
cheap and a price wouldn't mean much.

I would certainly return the XP CD from reading your post.

I will give it one last try, after I get .sif figured out.

Good luck

Thanks P.W. for all your efforts.

PS I use Thunderbird for my emails and newsgroups and it always kicks me
in the pants when it sees spelling errors

 

[Pennywise]

I had no idea how to open that .sif file and I accidentally discovered
that Notepad could read it, after I tried four other possibilities.

However, I hadn't a clue how to modify the .sif. If you can tell me how
to do that, I would give my XP CD a last try. Yeah, Paul told me about
it but it seems I was sleeping :-( At times I get woefully distracted.

One thread was that a .SIF file could be opened and edited with
notepad, yet it would be the last program I would use for that purpose.
Just any text editor will work.

I don't know if you can fix a problem with the install. I can tell you what to
look for but you have to be able to determine what is causing the problem.
----

First you need a CD to be able to edit "stuff" I use Hiren's BootCD
http://www.hiren.info/pages/bootcd you just need to find it.
Bart's CD is available, or similiar type CD.

First just try to install it again formatting the hd in the process.

It fails, reinstall it again but when it gives you the count down that it's
going to reboot (first Reboot) exchange your xpcd with Hiren's BootCD,

You will boot into hirens CD -or- turn off the system and boot until you do.
Don't lets windows start.
Use a program of choice from Hiren's to search for the textsetut.sif file, I
would expect it's missing, if so replace it with the one on the XPCD that you
have on hand for this, to C:\textsetup.sif. or just copy to C:\

Remove Hirens CD and reboot any error you get now will be real (in that you
have the files needed from the CD) and now you need to read *.log files to see
what the problem might be.

I have a very good link for of all the *.log files you can read to see what the
problem with an install (and program installs) are if it goes wrong or doesn't
install http://www.mcmcse.com/microsoft/guides/troubleshooting_setup.shtml

Can't remember the log I would view, thought it was called setup.log but the
link claims SETUPERR.LOG so first log file to view is c:\SETUPERR.LOG
and see what you can see...

As for repairing the textsetup.sif file, that's just not going to happen.
Deployment packages create that file. There are a few changes you
can make but as a whole you not going to edit, or repair it.

If your having problems with your key there's alway RockXP
http://www.snapfiles.com/get/rockxp.html it's more versatile
than most sites let on. Read up on it. My NOD32 lights up when
I try to download it, just ignore any malware alerts.

Good luck.