Error reading setup initialization file

[lil_dutchboy]

I've downloaded the beta 4 times and get the same message
when I try to start the install. I used the previous
version without problem until it expired. I have cleared
the Temp Internet folders before downloading and it still
won't install.

Any ideas?

XP HE SP2, Firefox, ZA free, spybot, ad-aware, spyware
blaster & trojan hunter - no known malware.

lil_dutchboy

 

[Bill Sanderson]

Did you also clear the OS temp folder? One way to do this is with Disk
Cleanup--Start, all programs, accessories, system tools, disk cleanup.

Any chance of getting a copy of the download file via a different ISP--on a
CD from another machine, for example?

 

[lil_dutchboy]

Thanks for the response. I did not empty the Windows Temp
file. I'll give them both a try.

 

[Bill Sanderson]

You are saving the file locally before running it? I know this seems inane,
since otherwise it is simply run from the TIF, but it seems to make a
difference.

--

 

[lil_dutchboy]

Yes, I was saving it to the desktop. I did follow both your
previous suggestions, and had success. I downloaded the
file at work, saved it to a pen drive then after clearing
every Temp file I could find, loaded and installed it at home.

Seems to be working fine.

Thanks for all the help. Now about the BSODs and Stop Error
messages I'm having...

That was a semi-joke, but if you would be so kind as to
direct me to a good place to ask that question, I would
really appreciate it.

lil_dutchboy

 

[Bill Sanderson]

Seems to be working fine.

Thanks for all the help. Now about the BSODs and Stop Error
messages I'm having...

That was a semi-joke, but if you would be so kind as to
direct me to a good place to ask that question, I would
really appreciate it.

There are very few BSOD's related to Microsoft Antispyware, fortunately--the
few I can recall relate to rampant infections which don't get completely
removed, and really trash the machine on a restart--mostly Windows 2000
machines and worms, I think. Early in the beta we used to see that
occasionally.

So--tell me more about the BSOD's and stop errors. There are general
troubleshooting articles for several of the stop errors, so if you let me
know the details, I may be able to point you at one. As a broad
generalization, these probably relate to either hardware/memory problems, or
software drivers. If the BSOD references a filename of any kind--that is
usually a good clue about what the issue is, although sometimes it's just
the unlucky bit of code left holding the bag when things died.

 

[lil_dutchboy]

Roger it's probably not Antispyware related. I've had 2
dozen or more crashes and hangs in the past couple months,
with at least 6 different STOP errors - mostly
IRQ_NOT-LESS_OR_EQUAL, but also
PAGE_FAULT_IN_NONPAGED_AREA, PFN_LIST_CORRUPT, and of
course the lovely BAD_POOL_HEADER. Files referenced tend to
be win32k.sys when there is a reference, although recently
I saw nv4_disp.dll. I've been to Aumha for STOP errors and
followed the links to the microsoft pages and KB articles.

Memtest86 says my ram sticks are OK, but then I only let it
run for about 14 hours, so I suppose there still might be a
problem there.

Window Annoyances has an 8 month thread of posts on the
same thing possibly pointing to an unholy combination of
motherboard/Nvidia/XP deeply buried conflicts. Most of the
people who got fixed did so by chucking parts.

I'm still looking. I haven't yet run a repair install of
XP, so I guess that's the next most likely action.

Man, if you have ideas, I'm ready to hear 'em.

lil_dutchboy

 

[Bill Sanderson]

I'd update all the drivers and the bios before I'd do a repair install of
the OS.

Check at the motherboard vendors website for bios updates and updates for
drivers for components built-into the motherboard.

Perhaps go to the chipset vendor for upgrades to the basic plumbing for the
chipset--Intel, Nvidia, Via.

If you want to try a different memory diagnostic--this one should be good:

http://oca.microsoft.com/en/windiag.asp

Some crashes specify that they can be caused by drivers. Drivers include
not just the stuff that relates intimately to hardware, but also some
low-level software only stuff--including antivirus and antispyware programs.

Beyond that--when it next happens--lets see all the specifics, or some
reasonable amount of them. 'course, it may lead to a lovely KB article like
this one:

http://support.microsoft.com/?kbid=329052

(my computer is crashing. Yes, we know that your computer will sometimes
crash.) end of article.


--

 

[lil_dutchboy]

Thanks for the ideas. I've collected the latest Bios &
Flash tool for the motherboard, as well as all the other
little goodies Abit had. I've also got the latest Nvidia
monster set of drivers (20+Mb!) and with the upgrade of
Firefox & Thunderbird, I will have the latest of most
everything but ZA. Reading the messageboards about ZA
Security Suite has convinced me to stay with the free
edition of the firewall.
I will be on a business trip starting tomorrow and might
not get to all this until Labor Day weekend, but I will
post as soon as I know anything new.

Thanks again,

lil_dutchboy

 

[Bill Sanderson]

Be careful--flashing the bios does entail some risk.

New video drivers always seem to me to entail risk--in fact, my general
feeling about video drivers is almost the reverse of other drivers--if you
are having problems and are on the latest driver, drop back a version. I
wouldn't worry about either ZA, Thunderbird, or Firefox--stick with the
stuff underneath them. I'm hearing some discomfort with the newest ZA
offering--probably better not to go there until you are sure you've got a
stable platform.

That sounds like the collection of stuff I'd try--of course, you should do
one item at a time and run for a day or two and watch the results, but who
has the patience?