> Thanks for that.
> Also, good to know that memory still serves well enough for general
> outline, even if the detail got a bit lost, some of the time anyway
> :-)
>
>
>
>         Russell

Russell,

This will work,

1.- Copy the whole program directory to a new directory, say NETHOST.
2.- Now you have c:\NETHOST\XXX
3.- in Autoexec.bat of the host machine.
    subst x: c:\NETHOST
4.- Now you have a new drive called x:, with your app directory eg x:\XXX.
    This is the path where the program "must" run in the host machine. To do
    so, modify the path in autoexec.bat to point to this directory
5.- Share c:\NETHOST over TCP/IP
6.- Connect this resource to a drive unit x: on the guest machine.
    Now you wil see x:\XXX
7.- You can force a batch process in the guest machine once it is logged in.
    ...in a .bat file write something like this:
    net use x: \\name_of_the_host\NETHOST
    set path = %path%;x:\NETHOST; '...etc
    application_name  here
    net use x: /d /y  ' this cleans all this mess.

Regard's,
Dennis Crawley
Argentina
www.geocities.com/proyectosenpic




-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist