Text 85, 68 rader
Skriven 2005-05-21 08:33:26 av Mike Luther (1:117/3001.0)
Ärende: CID PEERINST on MCP2?
=============================
You know, used to be when I got in trouble with PEER on good old Warp, I just
UNINSTALLED it.  I copied the CID core stuff to a CID directory on the target
hard disk in the normal boot partition.

Then I shoved in the Warp 4 Install CD-ROM and went into the CID image
directory and ran PEERINST.EXE there. Poof!  New PEER setup and away we went
for a new joy ride.

Oh you did get two different sharing and connecting folders in your CONNECTIONS
folder on the desktop!  One is called SHARED RESOURCES AND CONNECTION in the
NETWORK SERVICES folder.  The other is called simply SHARING AND CONNECTIONS. 
And either seems to work just fine to do those things, but whatever.. grin.

The main reason I learned to do this was that the as-furnished install on the
older WARP PEER installation was broken for CONFIG.SYS files with lines over
256 bytes long in it, as well as those with an EOF mark at the end of the
CONFIG.SYS file.  IBM fixed that in later issues of the Warp installation
CD-ROM operation and it made its way into the CID PEERINST.EXE version of the
install which let me get around the line length restriction in my 'normal'
CONFIG.SYS files.

Now, there was also another good 'reason' to install PEER this way.  The second
reason was that if I insalled PEER this way, I got a much more filled up folder
for the network control operation.  In it is the AUDIT log file viewer, and so
on.  That's the way, years later, moved to MCP1 thence MCP2, I know a given box
was set up from CID as opposed to the older before-then networking.  And yes I
sure do look at the errors in that log too.

But in these new days of, 'But wait!  There's less!", just when I thought I'd
remove PEER on this strange DOS-VDM corruption of networking and try a
re-install..  I start a PEER Uninstall and ..

     Puppy digs into the MCP2 CID game to do this.  No PEERLAN.EXE ..

Uhhhhhh .. Well, yes, when you migrate Warp 4 to MCP, you DO get a whole new
JAVA based TCP setup game.  And MCPT settup is seemingly different. You get
different folder names for things like MCPT to Adapters and Protocol icons and
so on.

But where now do you get to re-install PEER?   If I click on the UNISTALL PEER
icon that is left on the desktop to get started at this,It tells me to put in
the installation CD-ROM.  If I want to INSTALL the new PEER, it tells me to put
in the CID enable CD-ROM diskette with PEERINST.EXE in it.  So I shove in the
MCP2 CD-ROM stuff for PEERINST.

Which ain't there no mo' suh!

MCP2 and MCP1 ain't got no mo' PEERINST.EXE on 'em, folks.  I feel like I'm
being watched by a grinning possumn in a persimmon tree!

Can I just shove that old Warp4 CD-ROM diskette into the tray and re-install
PEER from that?  And then apply the three PEER fixpacks to it which have been
released since day whatever?  Including the one which goes on top of PEER for
MCP#?

And then what will happen to the TCP/IP setup coffee drinking beast as opposed
to the native OS/2 hard rock cafe original bippy that was there when this other
method of speak-easy peer conversation was in 'vogue'?

Inquiring mind wants to know..


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)