Re: VLMUP3.EXE bug report

Article View: comp.os.netware.connectivity

Article #276

Back to comp.os.netware.connectivity Previous Next

#276

From: A. Grant
Date: Mon, 07 Aug 1995 00:00

12 lines
1196 bytes

In article <807653399.7220@conquest.demon.co.uk> Allen@conquest.demon.co.uk (Allen Conquest) writes:
>After trying many combinations of old and new VLMs, I found that the
>problem was due to NETX.VLM.  When I replaced the new version with the
>old one, everything worked fine!  So my conclusion is that there is a
>bug within NETX.VLM.  Has anyone else found this problem?

I found a bug in NETX.VLM in VLMUP3.EXE.  But that was in the
previous version of VLMUP3, and I reported it to Novell.  
What _precise_ version of the VLMs are you using?
With Novell it is not enough to say 1.20a, VLMUP3 etc., you must
give the exact dates on all modules.  Novell just don't understand
change control.

Technical Details

Message-ID: <ag129.2214.000B1F2D@cam.ac.uk>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

References: <807653399.7220@conquest.demon.co.uk>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fe659,64276846ec3660a3
X-Google-Attributes: gidfe659,public
X-Google-Thread: fa939,64276846ec3660a3
X-Google-Attributes: gidfa939,public
From: ag129@cam.ac.uk (A. Grant)
Subject: Re: VLMUP3.EXE bug report
Date: 1995/08/07
Message-ID: <ag129.2214.000B1F2D@cam.ac.uk>
X-Deja-AN: 107628446
references: <807653399.7220@conquest.demon.co.uk>
organization: Systems
newsgroups: comp.os.netware.connectivity,bit.listserv.novell

Reply to Parent Message