ADSM-L

Re: Mac PowerPC native mode executable.

1994-06-28 15:48:11
Subject: Re: Mac PowerPC native mode executable.
From: Bill Colwell <BColwell AT CCLINK.DRAPER DOT COM>
Date: Tue, 28 Jun 1994 19:48:11 GMT
In <1994Jun28.003946.15235 AT draper DOT com>, walkerbl AT vnet.ibm DOT com 
(Brett Walker
 408256-0265 Fax:) writes:
>Re: Note from you attached below
>
>>I've been told that the SoftWindows communication package is Novell
>>IPX based.  Have you actually tried to run an ADSM backup under the
>>Windows app yet?  Anything to watch out for?
>
>My guess is that it won't run.  For the Windows client, we use Novell's
>TLI interface.  Unless SoftWindows supports that, then it probably won't run.
>But I admit, I know nothing about how SoftWindows is handling networking.
>Maybe TCP/IP or NetBios??
>
>If anyone finds out anything or can get the Windows client to work with
>SoftWindows, please send me a note (I'm still trying to get a PowerPC :-(
>
>Brett Walker

One of our PC/Mac support people has been trying to run both the Mac
client and the Windows client from the same PowerMac, with some
success!  There are some networking problems.  I am attaching his note
to me about these issues.
- - -
I have a Power Mac 7100/66 pre-installed with SoftWindows.  Our network is TCP/
IP based ethernet using MacTCP.  As others have noted, the DOS hard disk is just
a large (62MB or more) file to the Mac OS.  Anytime you fire up SoftWindows, it
makes some kind of change in the file to cause it to be seen as different.  This
means that if you fire up SoftWindow every day and do an incremental ADSM backup
every day, you will be backing up this monster file each time.  It is quite time
consuming and probably unnecessary.

To try to get around this, I installed our regular PC networking software, FTP
Software's PCTCP and Syntax's redirector, within SoftWindows.  I uses a generic
NDIS driver for the card.  ADSM for Windows was installed next.  I then excluded
the DOS Hard Disk file from my Mac ADSM backup.

If SoftWindows is the first software requiring TCP/IP communication to fire up,
the connections are made and Windows ADSM backs up the PC disk.  It performs as
expected for a Windows based machine. HOWEVER, if I fire up something like TCP
Connect II then quit, I will not be able to make the SoftWindows network
connection without restarting the Mac.  It appears that the Mac apps which use
the network don't fully release MacTCP when they're done.  It doesn't seem to
affect the Mac apps, just the network connections in the DOS environment.  It
will actually kill a connection within SoftWindows if you fire up something like
TCP Connect II while the DOS (or Windows) session is active.

Until I do something in the Mac environment to kill the DOS connection,
everything within SoftWindows works.  I can do backups and restores just like my
PC.  I can even see my backed-up PC volumes since I am using the same PC client
ID, and restore files from that to my SoftWindows volume (and the other way as
well).

So, my question is, what's going on with the Mac OS level network drivers that's
messing up the SoftWindows DOS environment?
-Dave Beckman
DBeckman AT draper DOT com
DBeckman AT draper DOT com
- - -

Bill Colwell
C. S. Draper Lab
Email: BColwell AT draper DOT com
Voice: 617-258-1550
<Prev in Thread] Current Thread [Next in Thread>