>>I tried going through the setup wizard. It appears the setup wizard makes a slew of changes to the NT registry and copies numerous support files to the local disk. Well this is not cool when all my users are restricted from doing this. (Having this restriction is why I chose NT in the first place!) When I did install it on a work station it ran fine from the local copy as administrator and as enduser - but I need it to run fine from the network. Is there a way I can just do the VFP6 runtime installation for the end users? And then be able to deal with exe's on the network like I used to in 2.6?
>
>My approach has been slightly different from Ed's, but requires more work from me. I've made setups which place a PM item for the app. The created PM item points to the app the setup places on the local hard drive. I run the install on each workstation (logged in as administrator) which will use the app, to get the necessary registry changes and runtime files installed. Then I delete the directory with the app which I just installed on the local hard drive, and change the PM item to point to the network app.
>
>My way is probably more work at each workstation than Ed's, but it's worked for me.
>
>Regards,
>Rich.


Rich, After a re-boot it works only when I click on the super.exe icon in the c:\supsys directory. If I run from a shortcut and have target: c:\supsys\super and start in: h:\apps\ it works. But if I run h:\apps\super.exe and start in h:\apps (the settings I want) it doesn't work. H:\apps has all the same files in c:\supsys (I even tried it after moving the setup subdirectory to h:\apps. Didn't think that would work and it didn't.)

What have I done wrong?
(This is beginning to scare me!)