>Hi all:
>
>I'm normally in the VFP forum, but need some networking help...
>
>We're near the end of developing a generic batch VFP process that will run on a PC workstation under Win95 attached to a Novell 4.x LAN, using Novell Client32 v.3.1, running unattended essentially 24 x 7...
>The process 'goes to sleep' during nightly backups -- with only a time-setting table open, so assure maximum availability of files for current backup activities.
>
>Our old DOS batch processes all re-boot themselves after 'waking' back up in the morning, to assure fresh network connections, and also reboot upon fatal errors (like 'not a database file' and stuff like that, that is otherwise hard to recover from without user intervention. In the DOS world, the Autoexec.Bat file starts, invokes the DOS login command -- with a saved username and no password -- so it just blows by with no user intervention needed, then invokes the FP runtime for the batch process, then when the FP process exits, it runs a DOS ColdBoot.Com executable that restarts the system.
>
>We have added a WinAPI call in our VFP app that will gracefully shutdown both VFP and Windows -- ie: "Restart the computer". The problem is that our Novell Windows Client login dialog requires pressing/clicking the "OK" button, even if there is no password. Without the ability to bypass that step, our re-boot/freshen environment technique is no good.
>
>Any ideas on a either a replacement for the Novell Client login that does not need the "OK" button if no password, or a way to 'stuff the keyboard' or something else??
>
>TIA
>
>Rob

Have you tried taking a look at the auto-login feature available in TweakUI (available on MS's site, don't have an exact link... Try www.microsoft.com/windows95 (or /windows98))

This creates an entry in the registry that automatically logs the user in, I'm just not sure it works with the Novell login (works with workgroups, windows logon and NT Domain login).

Hugo