Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Setup Error 280
Message
 
À
27/11/1997 02:01:53
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00062006
Message ID:
00062568
Vues:
47
>>>>I have completed and EXE that I now want to distribute. I created the directory tree on my machine of how I want the files to be when installed, ran the Setup Wizard choosing to include the VFP Runtime and to create the 1.44 disk images. Everything to this point works fine.
>>>>
>>>>However, when I test the setup by running the install disks I get to the point where you get the large install command button. When I choose to install I get the following error:
>>>>
>>>>Setup Error 280
>>>>Object 9
>>>>Your Setup files may be damaged.
>>>>Try restarting the setup program.
>>>>
>>>>I have tested using different disks and even tried the Netsetup option but keep getting the same error. Many thanks in advance as I need to get this delivered.
>>>
>>>One of my customers had the same error some time ago when they tried to install my program on a machine that did not support long filenames.
>>
>>I forgot to mention that this is VFP5. Since it can only run on Windows95 and NT this is not the problem. Does anyone know if there is a bug in the Setup Wizard in VFP5 and if so if there is a patch. Also, I have tried this on two different machines, a P90 with 24M and a P166 with 32M, and get the same error on both machines.
>
>There exists a bug fix for the setup wizard, but I don't know if it can fix the error.
>
>Try to look under:
>http://support.microsoft.com/support/kb/articles/Q162/0/04.asp

Thanks Benn. I'm now wondering if it is a file size issue when compressing. I removed the EXE from the directory tree, reran the setup wizard and the install worked fine. I put the EXE back, ran the setup wizard and same error. I then went into the project manager and removed all the pieces (forms, reports, etc.) that I am working on but not ready to deliver and rebuilt the EXE. I then ran the setup wizard again and the install worked great.

So, the EXE was causing the problem and the only thing I did to fix it was reduce the size. Odd!! I wonder if anyone else has encountered this?
Colin Magee
Team Leader, Systems Development
Metroland Media Group Ltd.
Mississauga, Ontario, Canada

cmagee@metroland.com

Never mistake having a career with having a life.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform