Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Problem\s+with\s+IBM\s+Lanserver\s+v3\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Problem\s+with\s+IBM\s+Lanserver\s+v3\?\s*$/: 3 ]

Total 3 documents matching your query.

1. Problem with IBM Lanserver v3? (score: 1): Author: Paul Goodwin <[email protected]>; Date: Tue, 15 Nov 1994 13:46:30 EST; I've got an ADSM user on an OS/2 box who's having a strange problem...when he starts up his OS/2 client, his LANSERVER v3 mounted disk storage shows up as available and everything appears to be koshe; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1994-11/msg00068.html (10,576 bytes)
2. problem with IBM Lanserver v3? (score: 1): Author: David Derk <derk AT VNET.IBM DOT COM>; Date: Wed, 16 Nov 1994 15:19:03 PST; Paul, When a drive is selected ADSM will go out and query the information for that drive to make sure the current information for that drive is still correct. A floppy disk may have been switched or; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1994-11/msg00074.html (11,360 bytes)
3. Re: problem with IBM Lanserver v3? (score: 1): Author: Paul Goodwin <[email protected]>; Date: Wed, 16 Nov 1994 19:34:41 EST; Thanks for your note. We have discovered (about an hour ago) that the problem was due to the disk not being labeled. When trying to back up from the GUI client, we got no indication as to the source; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1994-11/msg00075.html (10,663 bytes)

Current List: 1 - 3
Page: [1]