>From owner-adsm-l AT vm.marist DOT edu Wed Feb  5 08:57:24 1997
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
>   with BSMTP id 1656; Wed, 05 Feb 97 10:27:05 EST
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
(LMail V1.2b/1.8b) with BSMTP id 9463; Wed, 5 Feb 1997 10:27:01 -0500
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8c) with NJE
>          id 7983 for ADSM-L AT VM.MARIST DOT EDU; Wed, 5 Feb 1997 10:26:58 
> -0500
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
>          V1.2b/1.8b) with BSMTP id 9443; Wed, 5 Feb 1997 10:26:57 -0500
>Received: from intfw.MGIC.com by VM.MARIST.EDU (IBM VM SMTP V2R3) with TCP;
>          Wed, 05 Feb 97 10:26:27 EST
>Received: by intfw.MGIC.com (8.6.13/4.03) id JAA20792; Wed, 5 Feb 1997
09:27:50
>          -0600
>Received: from mgicsmtp(2.0.0.90) by tintfw via smap (V1.3) id sma024622; Wed
>          Feb  5 09:27:49 1997
>Received: by MGICSMTP.MGIC.COM (IBM OS/2 SENDMAIL VERSION 1.3.2)/1.0) id
>          AA0518; Wed, 05 Feb 97 09:30:18 -0500
>Received: by MGICHOME (Lotus Notes Mail Gateway for SMTP V1.1) id
>          4365BE895EBF79398625643500551E31; Wed,  5 Feb 97 09:30:17
>X-Lotus-Type: Internet Memo
>Mime-Version: 1.0
>Content-Type: Text/Plain
>Message-ID:
>Date:         Wed, 5 Feb 1997 10:26:58 -0500
>Reply-To:     "ADSM: Dist Stor Manager"
>Sender:       "ADSM: Dist Stor Manager"
>From:         Mary Vollmer
>Subject:      Using FX32 on Dec Alpha Client
>To:           ADSM-L AT VM.MARIST DOT EDU
>Below is the response I received from our NT administrator.  Is there anyone
>else out there in our situation who has found a way around this?  TIA
>
>"A while ago it was suggested that we try running ADSM on the Alpha using
DEC's
>FX32 product.  (FX32 is X86 emulation software).  It looks like a pretty slick
>app except that:
>
>-  It requires NT 4.0 and we are at 3.51
>
>-  It is intended for running End-user apps like Word or Excel and will not
>work with system applications such as services (ADSM uses a service)
>
>Hopefully IBM will make a Win NT Alpha version soon."

DEC's response is that FX!32 will work on NT 3.51, but is not tested and use at
your own risk.  I've got about a weeks experience with FX!32 and ADSM on NT
3.51.  They seem to be pretty happy together.  You'll get one error message at
the end of the ADSM install when it try's to kick off a help message.  That
doesn't work on 3.51, but it won't hurt the installation.

You're right about it not being used for services.  You'll have to use the NT
"AT" scheduler.  In case you haven't run in to it yet, there's a trick to that
too.  You can't just run "dsmc i -password=xxx" like you could from the command
prompt.  You need to call a command file that includes:
cd \adsm
erase *.log
erase *.out
dsmc macro incrback.mac -password=xx 1>adsm.log 2>stderr.out

(there's a readme file with ADSM that says the same thing)

The macro works where for some reason the command line won't.

===> I'd be pretty happy with an Alpha client too <===

---------------------------------------------------------
Get Your *Web-Based* Free Email at http://www.hotmail.com
Get Your *Web-Based* Free Email at http://www.hotmail.com
---------------------------------------------------------
=========================================================================