Access Violation startig EXE from Login Script



Hi All,
I wrote a C program that colects machine inventory - it is started from a
public share (eg. //SRV/Share/prog.exe) at user Login Script....
Now Windows9x are experiencing Access Violation errors when the .EXE is
started from Logon$ directory (eg. //DC-SRV/Logon$/prog.exe).

Do you have any idea why it is happening??

TIA,
Marcio

PS: It's seems not to be a bug on prog.exe, since it works fine on W2K, XP
machines... and also, it works fine when started from a local disk on Win9x
machines that are experiencing AV. errors...


.



Relevant Pages

  • Access Violation startig EXE from Login Script
    ... Now Windows9x are experiencing Access Violation errors when the .EXE is ... machines that are experiencing AV. ...
    (microsoft.public.win2000.cmdprompt.admin)
  • Re: Spooky netwoking behaviour! XPHome, Win98SE, XPPro...SP2, SP1....H
    ... Other machines on the same network work fine. ... This particular exe uses an XP visual style manifest resource compiled into ... Note that the exe is written in VB6, not .NET, but it uses a XP visual style ...
    (microsoft.public.windowsxp.network_web)
  • Re: Running VF8 EXE on a machine
    ... >the VFP8 book. ... >in a separate folder such as the folder where your app resides. ... >As far as keeping the EXE on the network goes, ... > Most of my client machines do not have VFP8 installed on them. ...
    (microsoft.public.fox.helpwanted)
  • Re: Question on exe size
    ... box..I get a 96 mb exe. ... whether you tried building something different on the various machines & ... or checking revs down to the build numbers. ... etc. if you need something that's quick to sort with. ...
    (microsoft.public.vb.general.discussion)
  • Re: How to dristribute Screen saver and configure it through GPO
    ... You can copy it from a central location to all machines with a startup script. ... But it sounds that the .exe has to be installed on the client machines? ... And if that screensaver has multiple settings i think you have t create your own .adm to manage it. ... confused with how to distribute the screen saver file to all client ...
    (microsoft.public.windows.group_policy)