Text 84, 76 rader
Skriven 2005-05-21 07:55:06 av Mike Luther (1:117/3001.0)
     Kommentar till text 83 av Peter Knapper (3:772/1.10)
Ärende: Logged on Peer chucks access!
=====================================
OK Peter ..

I've talked the Friend On Site into:

 PK> Ok, go back to BEFORE you start Peer and open a DOS 
 PK> VDM, leave it open THEN start Peer and see what 
 PK> happens.

doing this.  You can log on to PEER.  THe session is contaminated from the git
go.  Even with nothing other than a DOS-VDM window session open when you first
log on to PEER!

So the gent tells me cross his heart and hopes to live..

 PK> DOS sessions inherit the System environment present at the time they are 
 PK> started. If a Drive Network Connection is NOT present 
 PK> when the DOS session is openned, then the DOS sesion 
 PK> knows NOTHING about that drive letter and no 
 PK> virtualisation is needed for that drive.

Now I think the Friend On Site did this exact thing.

 PK> If this works, and subsequet DOS sessions cause the same problem, then 
 PK> the issue revolves around the Virtual Networking 
 PK> environment of the DOS session. Pull the DOS 
 PK> Networking stuff and your Networking connections 
 PK> should work fine (except in DOS sessions). It is 
 PK> probably the DOS VDM support of Network resources that 
 PK> is the culprit here. At a ROUGH guess it may be 
 PK> something to do with -

 PK>         vdostcp.vdd
 PK>         vdostcp.sys
 PK>         VDOSCTL.EXE

And just for curious sake, Friend On Site tried to copy a 'known good' set of
these from a working MCP2 latest box on the same PEER LAN into this curious
Wonderland box.  He got in the vdostcp.* files.  With no log on from a fresh
boot, so he tells me VDOSCTL.EXE produces a sharing error when the replacement
is tried, though.  The ALT F1 trapway to the rabbit hole in this looking glass
hall of mirrors isn't familiar to him and, so noteed, 'e doesn't know where to
find the utility diskettes for the operation any mo'.  Sigh .. (?)

 PK> Are these boxes using NETBIOS over TCP/IP or just NETBIOS?

Nope. All of the whole (hole? - grin!) site is just IBM NETBIOS and IBM TCP/IP.
 none of the PEER LAN boxes are even seen to the outside world at all except
for one which connects via a POTS phone line with DHCP and an Injoy dialup on
rare occaisions.

 PK> No, I am picking its going to be DOS VDM specific, as 
 PK> the resource works fine until you invoke the VDM 
 PK> session.

But how can this be it when even if a DOS-VDM is open before you log on and it
still breaks it?  Is this a queer sort of one environment fits all
manifestation of what is now broken of what OS/2 normally does as in 'children
go where I send thee!'

I think I've seen this strange rabbit peering at me from the hole!

   One pill makes you taller
   One pill makes you small
   And the ones your Mother gives you
   Don't do any good at all!

   ;)


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

Mike @ 1:117/3001


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