Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
ATTEMPTED MURDER - Setup Wizard is trying to kill me....
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00141126
Message ID:
00144272
Views:
30
I tried everything again:

No setup32.stf was left in existence on the local drive or LAN.
All wizsetup.ini files were removed.
Distrib directory was deleted.
All dkcontrol files deleted.

I didn't see any strange paths specified.

I still get the error messages of "object 8" and "object 20", telling me that my setup files may be damaged and that I should try running from where I previous did.

I finally had to install VFP on every machine and delete the program files just so I could get the .dll's registered. This of course worked fine.

I am still mystified, but appreciate your help.

Thanks again,
Jace

>>The trouble machines are clear of any VFP files. Creating the setup disks or netsetup using the setup wizard from in VFP works fine. Trying to use the setup from a machine to install it is when the errors occur. I will either get error #825 or #824 sometimes it says object error #8, it is very strange. In running the setup I am able to get as far as specifying the desired directory on the machine to install the program and right after that it croaks.
>>
>>I used to get these same messages for VFP 5.0, but even after upgrading to 5.0a I still can't get anything to work.
>
>824 & 825 indicate some bad lines in setup32.stf (#8 is a line there). The fix is to delete wzsetup.ini on both vfp directory and distribution file directory, as well as vfp DISTRIB directory, and all setup image files. This should do the trick for both 824 & 825 setup wizard errors.
>
>I've never seen this while installing, though. If there's a bad setup, you usually just get the "missing/corrupted file" error. Are you sure there are no vfp setup files anywhere (server or machine) from a previous bad setup on the problem machines? That might cause the problem...also, open up the setup32.stf and see if any of the files around line 8 look odd, like maybe a path that isn't correct...
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform