Activate Windows Executable Via Samba From HPUX? 1

[PrgrmsAll]

I am new to Samba and have been reading this forum with much interest. In my corporation we have HPUX preinstalled with a version of Samba.

Assuming we get it configured correctly, would it be accurate to assume the following:

When we see the Windows Server drives from the UNIX side, we will be unable to activate a Windows executable since that would cause an attempt to run it on the UNIX side in the UNIX shell?

Ideally we would love to be able to do this, i.e. activate a windows executable, to run in the windows environment, from a UNIX box. If Samba cannot facilitate this, does anyone have any advice for achieving this via some other means?

Thanks in advance.

 

[stanhubble]

No it wouldn't.

I am not all that familiar with HPUX but my assumption is that it is preinstalled with the Samba "Server".
This will enable you to "share" pieces of your unix filesystem to cifs/smb client systems.

There is also a Samba "client" (smbclient) that will give you a "ftp like" command line for some limited functionality. Mounting shares onto your unix filesystem is limited to those systems that understand smbfs (linux does but not much else).

you can only execute binaries on the OS they were compiled for.

hmmm, running remote commands on a windows system..........
sounds like a disaster waiting to happen....but what you could do is:

1. with samba installed on hpux, share a directory, have the windows system "map" it.

2. start a process on the windows system that waits for a particular file on the mapped drive to exist, and when it sees it then start the real process you want to happen.

3. on the hpux system when the conditions are right (via cron or when another process has completed) just "touch" the file in the shared directory.

 

[PrgrmsAll]

actually, what happens is that unix jobs run on the 9000. they create flat files. these flat files need to be formatted (MS Excel Macros exist to do this). we wanted to move the macros into a VB executable and activate it when the file was created. a watch job on the windows side is an option, however, we already use ECGateway and have had problems with this in the past. being able to explicitly activate the executable (non interactive) from within the job or at a prompt would be ideal. but the file-watch process is defintely a step closer. thanks for the valuable post. any other recommendations/advice would be welcome.

 

[mattjurado]

Not to make this any more complicated that it already might seem to you, but you could run a windows emulator on that computer, and activate macros in that environment.

Or perhaps openoffice/staroffice macros might be workable?

CrossOver Office?

Not sure if these are workable for what you are specifically trying to do, but just thoughts...

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.