>>>>>I sent a set of install disks to a client running WFW and the same app that I tested under Win95 won't run.
>>>>>
>>>>>It appears to not even startup! The client says his screen flashes black and then goes back to the program manager.
>>>>>
>>>>>He's running a 486-66 w/8MB ram...What are the minimum system requirements for the 3.0 runtime? Is there any other problem I could be running into?
>>>>>
>>>>>Any help would be appreciated as I'm in Florida and the client is in NY
>>>>>
>>>>>Thanx!
>>>>>
>>>>>Joe
>>>>
>>>>make sure the setup disks have win32s.... option in setup wizard under req'd files (i think asks win3.x, win95, winnt, check win3.x)
>>>
>>>Can I simply copy WIN32S16.DLL to my customers \windows\system directory? Or is there more that I need? I'm trying to avoid wasting time sending install disks again...
>>>
>>>Thanx!
>>
>>i don't know which files you need, but i'm sure you'll need more than just that one. any help here?
>>
>>i'd suggest doing another build -- it'd be easier in the long run.
>
>The win32s package from MS is 3 disks, and you need to run a setup routine. You can download it, I think it's PW1118.EXE (really mnemonic!).
>
>I distribute it separately from my app, since I prefer to have clients understand that this isn't part of my program.
>
>HTH
>Barbara
Barb
I've just had a heck of a time with 3.0 setup that creates disks that will not load on the user's PC. Seems taht there is a glitch in the setup wizard for 3.0. There is an updated setup wixard on the Microsoft website, I downloaded the beast and setup now works. One more thing, weird but it seem that if any and I repeat "any file names exceed the 8.3 requirement the dumb thing bombs with the old setup, with the new one there is also an 8.3 limit even to the poit that when you run the setup wizard watch setup screen 4 and keep the info down to 8 characters, I had ten in one box and the fool thing did not understand me. C'est la vie. If I can be of further hel let me know
Regards and happy setup
Bob