--------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200000 Date: 06/01/97 From: MIKE BILOW Time: 11:44am \/To: IGOR MYNKIN (Read 3 times) Subj: netware 4.10 + ide cdrom Igor Mynkin wrote in a message to Dmitry Yatcenko: IM> You're wrong! The only thing required is correct IM> ATAPI interface of CD ROM - so I had CD ROM mounted on IM> NW4.11, but some IDE CD can,t be mounted. There are only very special circumstances which will interfere with IDE CD-ROM support. If you have an IDE controller based on the buggy CMD640 chip, you may have problems with both hard drives and CD-ROM drives. If you have an IDE CD-ROM drive which was manufactured before the interface was standardized, such as the NEC 260, you may have problems. Nearly all newer CD-ROM drives will work correctly. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200001 Date: 06/01/97 From: MIKE BILOW Time: 11:50am \/To: SREN HEDEMAND (Read 3 times) Subj: Secondary ISA controller in 3.11 server Sren Hedemand wrote in a message to Mike Bilow: MB> What is the exact brand and model of the ESDI controller? SH> It's an Adaptec ACB-2320D, and acording to the SH> documentation, I'm supposed to use ISADISK.DSK for it. Yes, you're stuck. MB> ISADISK should pick up the geometry of the disk from asking the BIOS. MB> If the machine can see the ESDI drive under raw DOS, then the BIOS MB> knows the geometry. It could happen that the controller is not MB> reporting good geometry. SH> That's it exactly. The BIOS on the motherboard only has SH> support for the primary controller. To make it work under SH> DOS, I would have to dig out a devicedriver from somewhere. SH> Any ideas? I can give you a copy of UNIDRVR. This is a TSR I wrote many years ago as part of the BruteForce(TM) Utilities package. Basically, it allows you to force the machine BIOS into believing that the drive has some particular geometry, setting up a synthetic parameter table on the Int 41h vector. Let me know how I can get the files to you; either Internet e-mail or Fidonet netmail will suffice. UNIDRVR.COM is only 2 KB, but I don't think posting a uuencode would be appreciated in this echo. I can also send you one of the companion programs, RHDP, which tells you what the BIOS and parameter table think the drive is. For an ESDI drive, you usually set it as Type 1 in CMOS, so the parameter table is invalid. This is probably what is confusing ISADISK, but the BIOS should still report the geometry correctly. If you have a motherboard BIOS which supports a user-defined type, you can try that. Most ESDI controllers ignore the type code as long as it is not zero. MB> OS/2 uses the IBMINT13.I13 driver to access any disk controller which MB> has no protected mode driver. You can use the RMVIEW utility (and MB> the "/D" switch) to see which driver has picked up responsibility for MB> your ESDI disk. SH> Under OS/2 I use(d) the IBM1S506.ADD driver, which worked SH> just fine, as long as I specified the geometry in SH> CONFIG.SYS. How do I do it under NetWare? You can use my UNIDRVR TSR to set up the geometry under DOS, and then use the ISADISK driver as originally intended. (Obviously, do not "REMOVE DOS.") I do not think that ISADISK has any command line switch equivalent to "/GEO" in OS/2's IBM1S506.ADD driver, but a newer version may have added it. Not to sound foolish, but have you considered using NetWare for OS/2? This would fix all of your problems at once. It has some nice side benefits, such as adding support for virtual memory and allowing administration from the server console. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200002 Date: 06/01/97 From: MIKE BILOW Time: 12:06pm \/To: DOUG SCHLACHTA (Read 3 times) Subj: Alternative clients for Windows 95: Nove12:06:4006/01/97 Doug Schlachta wrote in a message to Mike Bilow: > Thanks! Are you using the TRXNET drivers or something else? DS> Nope thats what I'm useing. That should work. ARCnet is really simple stuff compared to Ethernet, since all ARCnet cards use a similar hardware interface and drivers tend to be vendor independent as a result. ARCnet is also an extremely robust protocol in the face of wiring problems, and will usually work except in the case of the most grievous wiring errors. > DS> I would love to know if anyone has a working setup > DS> of os2 warp ver3 working with novell and arcnets cards. > Now you're in an area I know something about! Apply OS/2 > server WR08210, which upgrades MPTS. Note that you must > apply UN00067 if you apply WR08210 in order for TCP/IP to > work afterward. DS> I am suposed to apply this to my client? DS> Sorry you just blew me out of the water, are these file DS> names? And are they available on there web site? I'm used to DS> plain dos and windows setups. This is a new project I'm DS> trying. Oh, I apologize. Those are code numbers for what IBM calls APARs and what normal people call bugs. The two-letter prefix indicates the general type of bug or bug fix, usually associated with some corporate division, and the five-digit code identifies the item serial number. Services are available on the Internet, but are tracked by APAR number. I can give you the locations for U.S. English fixes; you will have to hunt down the appropriate files yourself if you have other than the U.S. English version of OS/2. You will need the LOADDSKF utility to extract these disk image files *.DSK or *.?DK) to floppy disks: ftp://service.software.ibm.com/ps/products/os2/tools/ldf/loaddf.zip Base OS/2 service (XR0W026): ftp://service.software.ibm.com/ps/products/os2/fixes/v3.0warp/ english-us/xr_w026 Dec 11 13:47 text/plain csfboot.1dk 1041Kb Dec 11 13:47 text/plain csfboot.2dk 956Kb Nov 18 1996 text/plain xr_w026.1dk 1433Kb Nov 18 1996 text/plain xr_w026.2dk 1436Kb Nov 18 1996 text/plain xr_w026.3dk 1436Kb Nov 18 1996 text/plain xr_w026.4dk 1436Kb Nov 18 1996 text/plain xr_w026.5dk 1436Kb Nov 18 1996 text/plain xr_w026.6dk 1436Kb Nov 18 1996 text/plain xr_w026.7dk 1435Kb Nov 18 1996 text/plain xr_w026.8dk 1436Kb Nov 18 1996 text/plain xr_w026.9dk 1436Kb Nov 18 1996 text/plain xr_w026.adk 1436Kb Nov 18 1996 text/plain xr_w026.bdk 1436Kb Nov 18 1996 text/plain xr_w026.cdk 1436Kb Nov 18 1996 text/plain XR_W026.CID 9Kb Dec 3 09:54 text/plain xr_w026.ddk 608Kb Nov 18 1996 text/plain XR_W026.RM1 85Kb Nov 18 1996 text/plain XR_W026.RM2 94Kb Nov 18 1996 text/plain XR_W026.TIP 40Kb Dec 18 10:44 text/plain XR_W026.TXT 2Kb MPTS service (WR08210): ftp://service.software.ibm.com/ps/products/mpts/fixes/ english-us/wr08210/ May 31 1996 text/plain LSESSERV.NEW 306 bytes May 31 1996 text/plain us8210b1.dsk 1268Kb May 31 1996 text/plain us8210b2.dsk 1103Kb May 31 1996 text/plain us8210b3.dsk 1143Kb May 31 1996 text/plain us8210b4.dsk 1213Kb May 31 1996 text/plain us8210b5.dsk 1420Kb May 31 1996 text/plain us8210b6.dsk 859Kb May 31 1996 text/plain WR08210.LAB 2Kb May 31 1996 text/plain WR08210.TXT 2Kb TCP/IP service (UN00067): ftp://service.software.ibm.com/ps/products/tcpip/fixes/v3.0os2/un00067 May 16 1996 text/plain ls4tool1.dsk 1216Kb May 16 1996 text/plain LSESSERV.NEW 306 bytes May 16 1996 text/plain UN00067.LAB 1Kb May 16 1996 text/plain UN00067.TXT 1Kb May 16 1996 text/plain un0067b1.dsk 1435Kb May 16 1996 text/plain un0067b2.dsk 1322Kb -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200003 Date: 06/01/97 From: MIKE BILOW Time: 12:40pm \/To: JONATHAN HUNTER (Read 3 times) Subj: Alternative clients for Windows 95: Nove12:40:2406/01/97 Jonathan Hunter wrote in a message to Mike Bilow: JH> I was very happy with the MS client, until all the people JH> saying "You should switch to Novell" finally got to me. I JH> downloaded it (all X megabytes of it!), and had no end of JH> problems with it. Things like the login script handling - JH> users with names longer than 8 characters had their names JH> truncated in the login script... I found that out myself. It was particularly irritating because, of course, "SUPERVISOR" has more than 8 characters. In the login script, %LOGIN_NAME was truncated. I also discovered that, in the Client32 properties, you can configure what the client returns for %OS, %OS_VERSION, and %SHELL_VERSION; that could be very dangerous. I also discovered that Client32 reports %OS consistently as "WIN95" by default, even if you are logging in from a DOS prompt, but changes %OS_VERSION to be "V4.00" for a GUI login and "V7.00" for a text login. The change to %SHELL_VERSION was even worse, reporting "V1.01A" for a GUI login and "V5.00" for a text login! JH> Things like: c:\> k: JH> Invalid drive c:\> map JH> (yes, k: is mapped correctly) c:\> map k:=server:vol/path JH> (ok) c:\> k: k:\> (it works this time! but why not before?) I found that one, too. All text utilities will assume the first logical board in the ODI stack, and it seems to be more or less abritrary whether this is Ethernet 802.2 or 802.3 if the server supports both. You need to go into properties again and select the primary logical board manually for the correct frame type if you want the text utilities, such as MAP, to work reliably. Personally, I still believe that the best practice is to bind 802.2 to IPX and not bind 802.3 frame type at all on the server, but that may be impractical for administrative reasons. JH> I chucked it out because of these bugs. Plus, of course, it JH> brought me no benefits at all! The one thing it would have JH> let me do is run a couple of progs that depended on the JH> Netware DLLs (Pegasus Mail), but I just downloaded a JH> different version of that that didn't care about the JH> manufacturer of the DLLs. Interesting. The only good thing I have to say about the Novell client is that I was not even able to install the Microsoft client successfully! -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200004 Date: 06/01/97 From: MIKE BILOW Time: 12:50pm \/To: MARC BUFFET (Read 3 times) Subj: Alternative clients for Windows 95: Nove12:50:0106/01/97 Marc Buffet wrote in a message to Mike Bilow: MBi> would be particularly interested in hearing about any problems that MBi> developed which led to a decision to switch from one to the other. MBu> Whe took the microsoft client with the DNS service because MBu> of performance problems with the Novell 32 bit client ! Performance problems in what way? I was shocked that I could push the server to 85% utilization with a single client doing a lot of file copying, where the same operation would not have broken 20% under Windows 3.11. I don't know if this was packet burst or large packets or what, but the difference was striking. If the Microsoft client is any faster, the server would be pegged. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200005 Date: 06/01/97 From: MIKE BILOW Time: 12:58pm \/To: STEVE SORENSON (Read 3 times) Subj: Client based NW 3.12 back Steve Sorenson wrote in a message to Mike Bilow: SS> Won't do a restore from a Win95 machine. Crashes everytime. As SS> soon as Arcsolo does a tape seek, and finds the file(s) it's SS> looking for, I get Win95's blue screen of death. Besides that SS> fact, it doesn't support LFNs. MB> You may have a SCSI driver problem, not an Arcsolo problem. As MB> much as I despise Cheyenne's products, this is not normal. MB> What kind of SCSI controller are you using for the tape drive? SS> All Adaptec. I've used a 1542, a 1515 and a 2940W all with the SS> same results. After trying the latest miniport drivers for SS> each, and calling Cheyenne, they're actually the ones that told SS> me it wouldn't work. I've yet to hear anyone say that they can SS> do a restore from a Win95 client using Arcsolo 3. What happens if you configure Arcsolo to use ASPI rather than its Adaptec drivers directly? SS> For what it's worth, I think I've solved the problem by using SS> Cheyenne Backup v2.0 and using Wolfgang Schrieber's SS> BINDCLOS.EXE and BINDOPEN.EXE to get the bindery on tape. Well, at least you have a workaround. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200006 Date: 06/01/97 From: MIKE BILOW Time: 01:02pm \/To: ROB BERKERS (Read 3 times) Subj: Automatic loading and unloading of NLM's13:02:2006/01/97 Rob Berkers wrote in a message to Charles Miller: RB> I have heard that Backup Exec is a very good program. But we RB> decided to take a look at Arcserve (because in the past we RB> always worked with Arcsolo). Also a great program, with many RB> and many options to discover yet :-) After Arcserve 4 actually destroyed a server volume on us, that was the last straw and we will no longer use it. We switched to Backup Exec and have been very happy for several years over many server installations. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200007 Date: 06/01/97 From: MIKE BILOW Time: 01:09pm \/To: UFFE JENSEN (Read 3 times) Subj: PC3270 vs. NWClient Uffe Jensen wrote in a message to All: UJ> Is there anybody the in this conf. who have tried a IBM UJ> PC3270 communications program together with novell 32client UJ> for win95. I can get it to work together :-( UJ> The PC3270 tells me about a config error. But the error only UJ> exist with nw32client. If I use the Microsoft enclosed UJ> novell (win95) everything works. Any body ??? I'm guessing here, but PC3270 expects to communicate with an NDIS stack, while the Novell Client32 replaces the NDIS stack with an ODI stack. If you elect to install ODINSUP (which Windows 95 considers to be an adapter type), then you should be able to support NDIS client software such as PC3270. You should check your frame type for PC3270. The most commonly used is Ethernet SNAP, which is an extension of Ethernet 802.2. You should therefore configure the IPX client for Ethernet 802.2 also. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200008 Date: 06/01/97 From: MIKE BILOW Time: 01:23pm \/To: VINCENT SOEURT (Read 3 times) Subj: Novell, Instant Internet & OS/2 clients Vincent Soeurt wrote in a message to Eric Tam: VS> Instant Internet is a router/gateway who's translating VS> TCP/IP calls to IPX and back, specially designed for IPX VS> networks which don't have TCP/IP. The only question which VS> Bay Networks could not answer was if OS/2 clients using the VS> Novell Netware Requester also were supported. Perhaps VS> someone over here could confirm or deny this. I can't speak from actual experience, but an OS/2 machine should look like any other machine on the wire. You may need to apply some services to OS/2 if you require DHCP client capability, but I would be surprised if it did not work. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: EA200009 Date: 06/01/97 From: MIKE BILOW Time: 01:25pm \/To: BRYAN HOCHBERG (Read 3 times) Subj: %OS_VERSION w/Client 32 Bryan Hochberg wrote in a message to All: BH> Well, I'm getting a bit baffled here. Hopefully, somebody BH> will be able to point me in the right direction: BH> Where, exactly, does Client 32 for Windows 95 get its BH> information for the %OS_VERSION, as used in the login BH> script? I know that machine types and DOS name can be set BH> in the client properties sheet, but see no place where the BH> version is set. BH> Why I'm asking is that I have observed some workstations BH> running Client 32 for Win95 on my network who are showing BH> V7.00 (MSDOS), while others are showing V4.00 (WIN95). The BH> MS Client for NetWare appears to be consistent in reporting BH> MSDOS V7.00. I actually kind of like seeing WIN95 V4.00 BH> being reported, but am unaware of where this is coming from. BH> Any authoritative source of an answer to my pondering BH> appears to elude me. Perhaps somebody here knows??? Not surprisingly, what Client32 does is ask the OS. If it is running the GUI login (the little box that appears on startup), then the OS reports 4.00 and Client32 sets %OS_VERSION to "V4.00". If the login is done in text mode (from a DOS prompt), the OS reports 7.00 and Client32 sets %OS_VERSION to "V7.00". Client32 allows you to change %OS so that, say, "MSDOS" is reported by a text-mode login, while "WIN95" is still reported by a GUI login. My opinion is that it makes more sense for a text login to report "MSDOS V7.00" than "WIN95 V7.00" -- and I'm sure this is going to blow up in three more versions of Windows 95, if it lasts that long. The best idea might be to change %OS in text mode to something unique, such as "WINDOS", so you know what is really going on. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107)