[THIN] Re: Starting & killing background tasks
- From: "Derek J. Lambert" <dlambert@xxxxxxxxxx>
- To: "John A. Vorchak" <jvorchak@xxxxxxxx>
- Date: Fri, 27 Sep 2002 18:06:07 -0500
I've gotten half the problem to work.
I've created a batch file called faxmaker.cmd and put it in
%SystemRoot%\system32. It contains the following:
@echo off
start fmstart
I've added the Faxmaker client install dir into the system path.
Then I went into HKLM\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon and put faxmaker.cmd at the end of the
AppSetup value.
This successfully starts the fmstart.exe program. I'm sure it will
continue to run once I close out of everything (but I haven't tried it
yet as I'm writing this email...)
-----Original Message-----
From: John A. Vorchak [mailto:jvorchak@xxxxxxxx]=20
Sent: Friday, September 27, 2002 5:52 PM
To: Derek J. Lambert
Subject: RE: [THIN] Starting & killing background tasks
Got the client, and it looks like the shell must be loaded first I am
sorry to say...
One of the dependencies of the fmstart.exe is tiff32.dll which runs with
user32.dll and gdi32.dll as two of its dependencies. Looking at the
GDI32 functions that it calls, it's trying to call drawing functions
right off the bat. So, it looks like a desktop should be present in
order for the application to run...possibly...
I also just tried to install it as a service to test to see if that
would work, and no go... Looks like you are completely out of luck on
this one. I'm going to do a post to thethin to let everyone know that
this app requires the desktop so that no one else gets hammered with
this lousy app.
Good luck.
John
-----Original Message-----
From: Derek J. Lambert [mailto:dlambert@xxxxxxxxxx]=20
Sent: Friday, September 27, 2002 17:38
To: John A. Vorchak
Subject: RE: [THIN] Starting & killing background tasks
I've been playing around will different ways to load this exe and it
looks like it might not load until after the shell is initialized. I
tried running the command directly from my logon script and again it
didn't look like it loaded. So I might be SOL..
-----Original Message-----
From: John A. Vorchak [mailto:jvorchak@xxxxxxxx]=20
Sent: Friday, September 27, 2002 4:14 PM
To: Derek J. Lambert
Subject: RE: [THIN] Starting & killing background tasks
Hklm\software\vorchak software\utilities
I originally just had it go to the current directory, but it blew up on
me for some reason, so a reg value was easy enough to add...
John
-----Original Message-----
From: Derek J. Lambert [mailto:dlambert@xxxxxxxxxx]=20
Sent: Friday, September 27, 2002 17:03
To: John A. Vorchak
Subject: RE: [THIN] Starting & killing background tasks
Is it HKLM\Vorchak Software, or HKLM\Software\Vorchak Software?
-----Original Message-----
From: John A. Vorchak [mailto:jvorchak@xxxxxxxx]=20
Sent: Friday, September 27, 2002 4:02 PM
To: Derek J. Lambert
Subject: RE: [THIN] Starting & killing background tasks
I am now really embarrassed! I forgot to save the README.txt file
before I zipped up the files...Sorry about that...The text is below:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
StartProc.exe and StopProc.exe
Used to start applications at logon of TS session and kill them on=20
exit.
Usage:
1) Put both applications in a folder available to the user, they will=20
be required to have at least RX permission to these files.
2) Make a new file called MyApp.ini Populate it as defined below:
[AppInfo]
AppID=3DD:\windows\notepad.exe
Replace whatever your path and applications proper identification is=20
(e.g. AppID=3DM:\Program Files\Microsoft Office\Office10\winword.exe)
Save the MyApp.ini file somewhere where the user has Read or better=20
permissions.
Create a new registry key on the server:
HKLM\Vorchak Software\Utilities
Create a new String Value (REG_STR), valuename of AppPath, set the=20
value of AppPath to the location WHERE YOU HAVE THE MyApp.ini file=20
[otherwise an error 53 - file not found - error will occur].
In the users logon script, execute StartProc.exe -- the application=20
will start with normal focus to the user
In the users logoff script, execute StopProc.exe -- the application=20
will terminate if it is still running.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-----Original Message-----
From: Derek J. Lambert [mailto:dlambert@xxxxxxxxxx]=20
Sent: Friday, September 27, 2002 16:50
To: John A. Vorchak
Subject: RE: [THIN] Starting & killing background tasks
I have that problem some days too :)
I'll definitely be giving this a try, and let you know if it works!
-----Original Message-----
From: John A. Vorchak [mailto:jvorchak@xxxxxxxx]=20
Sent: Friday, September 27, 2002 3:51 PM
To: Derek J. Lambert
Subject: RE: [THIN] Starting & killing background tasks
Derek,
I am extremely fast with my alt-s fingers today... I meant to let you
know what was happening with the apps....
First, startproc reads the ini, pulls the application information and
starts it. Then it populates a registry entry in HKCU under
Software\Vorchak Software\Utilities called ProcID. That records the
actual process ID for the process the user starts.
At logoff, stopproc is called and it reads that registry value that
startproc wrote and kills the application associated with the process ID
stored in the registry.
Like I said, pretty simple, it's just a matter of having the right code
on hand to do it...
John Vorchak
Vorchak Software
Custom Windows XP Embedded and
Windows NT Embedded Components and Solutions
jvorchak@xxxxxxxx
-----Original Message-----
From: Derek J. Lambert [mailto:dlambert@xxxxxxxxxx]=20
Sent: Friday, September 27, 2002 16:37
To: John A. Vorchak
Subject: RE: [THIN] Starting & killing background tasks
Sure! That would be great!
-----Original Message-----
From: John A. Vorchak [mailto:jvorchak@xxxxxxxx]=20
Sent: Friday, September 27, 2002 3:38 PM
To: Derek J. Lambert
Subject: RE: [THIN] Starting & killing background tasks
Derek,
I'm hitting you off-list for now because I may have a solution, but I
need to email you a zip file to try it. Let me know asap if it's ok to
send a zip to you with a possible fix for this...
John Vorchak
Vorchak Software
Custom Windows XP Embedded and
Windows NT Embedded Components and Solutions
jvorchak@xxxxxxxx
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Derek J. Lambert
Sent: Friday, September 27, 2002 14:44
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Starting & killing background tasks
I've been trying for a couple of weeks to get the GFI Faxmaker client to
work correctly on our Win2k/XPfr2 servers. According to the manufacturer
Citrix is not supported, nor is their "enhanced" form supported under
Terminal Services. When I asked their support people about any possible
"fixes" or "hacks", even if unsupported, I got the following response:
=20
"I will forward your suggestion to the product manager. Please remember
that
this is not a tailor made application and therefore, we cannot add all
the
features that are requested."
=20
I'm sure that comment conjures up all kinds of responses (as it did for
me), but I don't have the time to argue the merits of thin computing
with people who obviously haven't seen the light. I want to get this
working since so far it is the best package I've found considering cost,
management, features and hardware requirements.
=20
What I've discovered on the local console when a user (the
administrator) logs on a small program "fmstart.exe" is run from the
HKLM Run key. This somehow is grabbing requests and opening the form/fax
client (which is just small MAPI application interface to Outlook). If I
run this program (fmstart.exe) in my session the fax client starts
functioning as one would expect. Unfortunately when I do this and close
all my applications, fmstart.exe is still running in the background and
my session never closes. I'd like to try and find a way to run this when
a session opens, and then close it when the session shuts down. Is there
somewhere I can define an "ignore" list so that the session doesn't care
about it? If I open task manager I see that wfshell.exe, winlogon.exe,
and csrss.exe are all running. These are all getting ended automatically
- and I'm hoping I can add fmstart.exe to the mechanism that loads
these. I've tried adding fmstart.exe to the HKCU Run key but this must
not get used when running a seamless session. Is there an equivalent
location for seamless sessions?
=20
Anyway, if anyone can help or has any ideas please let me know. I've
found a number of similar questions in the archives, but no solutions
and nothing any experimentation. I'm sure if there is a solution to this
it would benefit a number of other applications. Acrobat for one I know
has a process like this it starts up and never ends, leaving a open
empty session.
=20
Thanks!!
=20
Derek J. Lambert, MCSE, MCP+I, CCA, A+
MIS Manager
Columbia ParCar Corp.
=20
**********************************************
This weeks sponsor Kevsoft Corporation=20
TScale by Kevsoft Corporation=20
Support 30% to 40% more users on your server farm
without buying new hardware! =20
http://www.kevsoft.com/
***********************************************
For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
**********************************************
This weeks sponsor Kevsoft Corporation
TScale by Kevsoft Corporation
Support 30% to 40% more users on your server farm
without buying new hardware!
http://www.kevsoft.com/
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.
http://thethin.net/citrixlist.cfm
Other related posts:
