PSS ID Number: 95438
Article Last Modified on 1/8/2003
The information in this article applies to:
- Microsoft Visual Basic for MS-DOS 1.0
This article was previously published under Q95438
SYMPTOMS
In an OS/2 version 2.0 MS-DOS Window, when you attempt to make an .EXE file from within the VBDOS.EXE interpreter environment or when you run LINK.EXE from the command line, you may get System Error SYS3175 (access violation).
WORKAROUND
To work around this problem, link your program from the command prompt, and use the Link /r option. The /r option prevents Link from attempting to use extended memory. Option /r must be the first option, as in this example:
BC MAIN.BAS;
BC MOD1.BAS;
BC MOD2.BAS;
LINK /r MAIN.OBJ MOD1.OBJ MOD2.OBJ;
In addition, the SETUP.EXE program incorrectly puts LINK.EXE into the \OS2 directory, overwriting the OS/2 system linker. To preserve the OS/2 linker, rename it before installing Visual Basic for MS-DOS using these commands:
CHDIR \OS2
RENAME LINK.EXE OS2LINK.EXE
After you install Visual Basic for MS-DOS, move LINK.EXE to the VBDOS directory and restore the OS/2 linker by using these commands:
CHDIR \OS2
COPY LINK.EXE \VBDOS
ERASE LINK.EXE
RENAME OS2LINK.EXE LINK.EXE
STATUS
Microsoft has confirmed this to be a bug in both the Standard and Professional Editions of Microsoft Visual Basic version 1.0 for MS-DOS. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Additional query words: VBmsdos buglist1.00 1.00
Keywords: KB95438
Technology: kbAudDeveloper kbVB100DOS kbVBSearch kbZNotKeyword3
