OS/2 Shareware BBS: 36 Tips/36-Tips.zip/acad_os2.zip/ACAD_OS2.INF

OS/2 Help File | 1994-04-11 | 78KB | 540 lines

ΓòÉΓòÉΓòÉ 1. AutoCAD Under OS/2 Here ΓòÉΓòÉΓòÉ

March 11, 1994

This is the Unofficial Help File for running AutoCAD R12 under OS/2. Feel free
to distribute to other users and BBSs.  I suggest that you print this document.

At my office we presently run AutoCAD R12c2 (DOS) under OS/2 2.1 and on Netware
3.11.  I'm also going to offer some tips on running under NetWare near the end
of this file. Netware 3.11 was installed by my VAR and I have installed the
requester on the workstations, setting up the systems to work in the manner we
prefer.  Since everyone seems to have a preferred method for setting up their
network, my information will be more of a guide rather than a how-to article.

For the purposes of this file, I'm assuming the user has some experience with
OS/2 2.x and needs help in getting AutoCAD to run under this OS. OS/2 2.1 and
AutoCAD R12c2 are the BEST combinations to use.  NO PATCHES ARE REQUIRED WITH
THIS COMBINATION! If you use older versions of OS/2 and AutoCAD, then you will
need specific patches as follows:

o   If you run OS/2 2.0, you must have a service pak installed (I had IBM
Service Pack level 6055).  There are two service paks available, but either
will contain the required fixes that will fix the system to allow AutoCAD to
run.


o   If you run AutoCAD R12c0 or c1 under OS/2 2.0 with a service pak installed,
you must also apply the patch "OS2PCH.ZIP" file located in the AutoCAD forum in
library area #9 ("What's New").


o   If you run AutoCAD R12c0 or R12c1 under OS/2 2.1, you will need the
"OS2PCH.ZIP" patch also.

The below settings should be used as a guide for tuning your system. A minor
changes, like the VIDEO_8514A_XGA_IOTRAP  setting can make significant
performance changes. Most of these settings are the default values and don't
require any tweaking at all. The sheer number of settings available for the
user to adjust can be a bit overwhelming; these should work with minor, if any,
changes to most systems.

Help can be found on CIS in the IBM OS2USER and OS2SUPPORT forums as well as by
users in the AutoCAD OpSystms/Networks subject in the ACAD forum.

Autodesk does not officially support AutoCAD running under OS/2, but they have
tried to insured that the program will run under the OS and sometimes an
employee will try to help out (I've seen Christal Moreno offer advice on
occasion.)


ΓòÉΓòÉΓòÉ 1.1. R12c2 And OS/2 2.1 DOS Settings List ΓòÉΓòÉΓòÉ

**************************************

COM_DIRECT_ACCESS --- ON (Try off if you have slow loads, jumpy cursor.  This
setting does not appear if Gwinn's drivers are used.)
COM_HOLD --- ON
COM_RECEIVE_BUFFER_FLUSH --- NONE
COM_SELECT --- ALL
DOS_AUTOEXEC --- C:\AUTOEXEC.BAT
DOS_BACKGROUND_EXECUTION --- ON (Try OFF if other programs unresponsive)
DOS_BREAK --- ON
DOS_DEVICE --- (Blank - C:\OS2\MDOS\ANSI.SYS may be required by some add-ons.)
Other device drivers can be loaded here also.
DOS_FCBS --- 0
DOS_FCBS_KEEP --- 0
DOS_FILES --- 50 (Some add-ins may require more; try 80 if you have problems)
DOS_HIGH --- ON
DOS_LASTDRIVE --- Z
DOS_RMSIZE --- 640
DOS_SHELL --- C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS /E:1024 /P
          (Note: The environment variable can be adjusted
          according to your specific needs. Try 2048 if you
          need more space...the memory cost is only 1k.)
DOS_STARTUP_DRIVE --- (Blank)
DOS_UMB --- ON
DOS_VERSION --- (Accept defaults)
DPMI_DOS_API --- AUTO
DPMI_MEMORY_LIMIT --- 40
DPMI_NETWORK_BUFF_SIZE --- 8
EMS_FRAME_LOCATION --- AUTO (Try ENABLED if you're a heavy Win app user.)
EMS_HIGH_OS_MAP_REGION --- 32
EMS_LOW_OS_MAP_REGION --- 384
EMS_MEMORY_LIMIT --- 0
HW_NOSOUND --- OFF
HW_ROM_TO_RAM --- OFF
HW_TIMER --- ON
IDLE_SECONDS --- 0
IDLE_SENSITIVITY --- 100 (I currently use 75)
INT_DURING_IO --- OFF
KBD_ALTHOME_BYPASS --- OFF
KBD_BUFFER_EXTEND --- ON
KBD_CTRL_BYPASS --- NONE
KBD_RATE_LOCK --- OFF
MEM_EXCLUDE_REGIONS --- (Blank)
MEM_INCLUDE_REGIONS --- (Blank)
MOUSE_EXCLUSIVE --- OFF
NETWARE_RESOURCES --- PRIVATE (Netware setting - some prefer Global)
PRINT_SEPARATE_OUTPUT --- ON
PRINT_TIMEOUT --- 15
VIDEO_8514A_XGA_IOTRAP --- OFF (Some video boards require ON)
VIDEO_FASTPASTE --- OFF
VIDEO_MODE_RESTRICTION --- NONE
VIDEO_ONDEMAND_MEMORY --- ON
VIDEO_RETRACE_EMULATION --- ON
VIDEO_ROM_EMULATION --- ON
VIDEO_SWITCH_NOTIFICATION --- OFF
VIDEO_WINDOW_REFRESH --- 1
VIPX_ENABLED --- ON (Netware setting)
XMS_HANDLES --- 32
XMS_MEMORY_LIMIT --- 64 (enables DOS_HIGH)
XMS_MINIMUM_HMA ---


ΓòÉΓòÉΓòÉ 1.2. R12c1b And OS/2 2.1 WinOS2 Settings List ΓòÉΓòÉΓòÉ

(thanks to Kendall Alton)

*******************************************************

"The following are the OS/2 settings for AcadWin that I use on my 486 Notebook,
212MB HD, 20MB RAM, SVGA Active Matrix. The settings for my IBM PS2 95XP, 420MB
HD, 24MB RAM, XGA, 8514, are set the same." (My note: See "Gotchas" below.)

WIN_RUN_MODE --- 3.1
WIN_DDE --- ON
WIN_CLIPBOARD --- ON
DOS_AUTOEXEC --- C:\AUTOEXEC.BAT
DOS_BACKGROUND_EXECUTION --- ON
DOS_BREAK --- ON
DOS_DEVICE --- BLANK
DOS_FCBS --- 16
DOS_FCBS_KEEP --- 8
DOS_FILES --- 50
DOS_HIGH --- ON
DOS_LASTDRIVE --- Z
DOS_RMSIZE --- 640
DOS_SHELL --- C:\0S2\MDOS\COMMAND.COM C:\0S2\MDOS /E:1024 /P
DOS_STARTUP DRIVE --- BLANK
DOS_UMB --- ON
DOS_VERSION --- BLANK
DPMI_DOS_API --- AUTO (Try ENABLED if you're a heavy Win app user.)
DPMI_MEMORY_LIMIT --- 64 (My note: This is the OS/2 default.  Smaller setting
might be better.)
DPMI_NETWORK_BUFF_SIZE --- 8
EMS_FRAME_LOCATION --- AUTO
EMS_HIGH_OS_MAP_REGION --- 32
EMS_LOW_OS_MAP_REGION --- 384
EMS_MEMORY_LIMIT --- 0
HW_NDSOUND --- OFF
HW_ROM...--- OFF
HM_TIMER --- ON
IDLE_SECONDS --- 0
IDLE_SENSITIVITY --- 100
INT_DURING_10 --- OFF
KBD_ALT_HOME...--- OFF
KBD_BUFFER...--- ON
KBD_CTRL_BYPASS --- NONE
KBD_RATE...---OFF
MEM_EXCLUDE...--- BLANK
MEM_INCLUDE...--- BLANK
MOUSE_EXC...--- OFF
PRINT_SEP...---ON
PRINT_TIMOUT --- 15
SI0_ALLOW._COM1--- ON (Note: These SIO settings are for Ray Gwinn's comm
drivers and may be used with AutoCAD for DOS as well.)
SI0_ALLOW._COM2 --- ON
SI0_ALLOW._COM3 --- ON
SI0_ALLOW._COM4 --- ON
SI0_VIRTUALIZE_16550A --- ON
SI0_VIRTUALIZE_COM_POR --- ON
SI0_VIRTUALIZE_RTS_IS_ --- ON
VIDEO_8514_XGA_10TRAP --- OFF
VIDEO_FASTPASTE --- OFF
VIDEO_MODE...---NONE
VIDEO_ONDEMAND...--- ON
VIDEO_RETRACE...--- ON
VIDEO_ROM...---ON
VIDEO_SWITCH...--- OFF
VIDEO_WINDOW...--- 1
XMS_HANDLES --- 32
XMS_MEMORY --- 0
XMS_MINIMUM --- 0

Note...if you use a digitizer I highly recommend making sure either you have a
16550 uart, or use Gwinn's drivers to prevent a jumpy cursor.  The drivers can
be downloaded from the IBMOS2 USER forum.


ΓòÉΓòÉΓòÉ 1.3. Special Video Notes ΓòÉΓòÉΓòÉ

1. The Default AutoCAD XGA driver does not work under OS/2.  You have to either
use the basic VGA ADI driver, or use the Panacea TurboDLD Drivers(Classic or
Deluxe). IBM has just made these drivers available on the XGA v2.11 drivers
diskette. Also, set VIDEO_8514A_XGA_IOTRAP = ON.


2. With AutoCAD for Windows the std. Windows driver may work better than the
Accelerated display driver on some machines with the XGA-2.


3. The VIDEO_ON_DEMAND setting sometimes needs to be set to off, i.e. for
Panacea's new TurboDLD v2 driver.  I don't know if it results in any speed
penalty, or just memory used.


4. The ATI Graphics Ultra may have to be set to 8 bit mode on most computers.
We have several here, and most are setup in this manner.  This is documented
under native DOS operation also. Be sure to set the jumper on the board and via
the software setup. A blank white screen after the OS/2 logo appearsd, as well
as some other problems which my not appear to be video related are symptoms.


ΓòÉΓòÉΓòÉ 2. General OS/2 Tuning Tips ΓòÉΓòÉΓòÉ

Depending on the amount of memory you have installed, OS/2 can be tuned for
better performance for your particular system. My system is a 33/386 with 16
megs of RAM, 340MB hd (all FAT right now), ATi Graphics Ultra w/ 1MB (primary
video), SummaSketch II digitizer, a Gateway G/EtherTwist 16 network adapter,
and an ATVista video board. I am also running Netware 3.11 with the OS/2
requester allowing DOS, WinOS2, and OS/2 support. This is quite nice in that
you don't have to fight RAM cram for your device drivers; the Netware drivers
load into OS/2's flat memory model.

With my system as a guide, I suggest the following enhancements as a starting
point:

FILES=50  (For better DOS performance)
BUFFERS=70   (For better DOS performance)
DISKCACHE=1024,LW,AC:CD  (Note: I don't think you'll see much improvement over
2 megs. The Proportional Software folks, 71333,2765, have a table of
recommended cache settings.)
THREADS=512   (For better system performance)
DOS=HIGH,UMB  (Allows use of DOS UMB's)
DEVICE=C:\OS2\MDOS\VSVGA.SYS  (Usually better than VVGA.SYS)
SET DIRCMD=/O:GN   (Sorts directories)
SET AUTOSTART=FOLDERS   (Anything I want opened on the desktop I put in my
Startup Folder as a shadow. I personally do not want the CONNECTIONS parameter
here.)

With less memory, use less cache.

Be sure to include all drives in the DISKCACHE AC:XX statement parameters. If
you had drives C:, D:, and F: for example, then your statement would read:

DISKCACHE=1024,LW,AC:CD

"AC" does an autocheck (chkdsk/f) on drives that were improperly shutdown.

OS/2 is very memory sensitive in that all of your RAM should _preferably_ be
the same type and more importantly, speed. If at all possible, get memory from
the same manufacturer and be sure it's rated at the same speed. With chips of
different speeds you are more prone to certain OS/2 TRAP errors and other less
obvious system failures. Just a word of caution.


ΓòÉΓòÉΓòÉ 2.1. Gotchas: ΓòÉΓòÉΓòÉ

o  (Some boards require the following, others are not affected at all...dual
screen setups aren't affected.) When going to the desktop on a single screen
setup, you may find it useful to do an F1 (Flip Screen) to put AutoCAD in text
mode.  This helps prevent video corruption (a plain white or black screen, or
scrambled graphics). Make sure you leave AutoCAD in the Command prompt, not in
the middle of a dialogue box, etc. This is necessary to reintialize the AutoCAD
graphics screen, as we're about to discuss...

If you have a corrupt video screen when you return to AutoCAD, don't panic. You
will need to reinitialize the graphics screen. One method is to type "Config"
and to bring up the text based configuration menu. This will reinitialize the
screen automatically...you don't need to change anything else, just get back
out to the AutoCAD graphics screen.

A better method to accomplish the above is to add the line below to your
acad.lsp (or other suitable custom lisp file) to reinitialize the graphics
screen:

(DEFUN C:RI ()  (COMMAND "SETVAR" "RE-INIT" "8"))

If you return to AutoCAD and find you have graphics corruption, just type the
two letters "RI" and hit enter. This is executes AutoCAD's REINIT command,
which reinitializes the graphics screen.

o   AutoCAD for DOS allows you to shell out of the program to do your chores
outside of AutoCAD. I understand from discussions here in the AutoCAD forum
that WinOS2 users cannot do this, but IBM is working on a fix. Perhaps this
will be fixed in the next maintenance release of OS/2, which is in beta testing
now at the time this file is being written. Of course, unless you have an
add-in program that requires SHELL to be active, you can simply start a DOS or
OS/2 session to get at your beloved command line.


ΓòÉΓòÉΓòÉ 3. Starting AutoCAD On The Desktop ΓòÉΓòÉΓòÉ

I start AutoCAD from an icon on my desktop. Drag a Program object from the
templates folder and put it in your preferred location on the desktop. It will
open to the Program - Settings page of the notebook, ready for your input.
Under Path and file name: type in the information with the file you start
AutoCAD with. Many users have a batch file like ACAD.BAT that includes other
setup information AutoCAD will require in order to execute. So if ACAD.BAT is
the file you start AutoCAD with and AutoCAD is on your D: drive, type this:

D:\ACAD12\ACAD.BAT

You don't need anything in the parameters directory. In the Working Directory
box, type the location of the AutoCAD directory.

D:\ACAD12

Now go Session page, DOS Settings, and make your settings changes. Make sure
you select DOS Full Screen. AutoCAD will not run very well in a window, but it
can be useful for cut and paste. You may have to change your video mode to VGA
for OS/2 to be able to virtualize the AutoCAD graphics screen properly.

On the General page, you can change the icon for the program. There is a file
located here in one of the ACAD libraries with OS/2 CAD type icons that I
uploaded some time ago. You can d/l this file and drag 'n drop a suitable
AutoCAD icon onto the Current Icon on the General page to change it. It's easy!


ΓòÉΓòÉΓòÉ 4. DWG File Association ΓòÉΓòÉΓòÉ

You can easily associate your AutoCAD files by changing your program's object
(the icon we made above) by opening the Settings for that object, going to the
Association page, and adding .DWG files. Then whenever you click on the file,
AutoCAD will load itself immediately. Careful not to load more than one copy of
AutoCAD unless you have your system set up to do this! (Bet that AutoCAD OS/2
port would let you load all the files your system had resources for...sigh.)
Also, if you have lots of .DWG files in a directory, it will take some time to
build all of the file icons.

The OS/2 desktop offers a wealth of customization. Bill Hinkle offers this
specific tip:

   "..., one technique we use on the Acad workstation is to shadow specific
project drawing directories to the desktop (or to an AutoCAD work area folder,
depending on the workstation). Then the user can waste his time making cute
custom folder icons fo r them <grin>. More importantly, though, we set them up
in icon view, showing small icons, flowed or non-flowed, and with the "Always
maintain sort order" flag set, for Name sorting. This makes for convenient
retrieval of drawings by project. The starting  BAT file, of course, has to be
set up to accept a drawing name as a %1 parameter, or something more complex."


ΓòÉΓòÉΓòÉ 5. Multiple Sessions ΓòÉΓòÉΓòÉ

I did this long ago with R10 286, but haven't tried it with R12 recently. It
appears it can be accomplished with R12, and I'll relay what Steve Dulek found
out:

I also learned a trick about setting up multiple sessions of DOS386 r12. You
can start 3 separate batch files (i.e., acad1.bat, acad2.bat, acad3.bat), but
make sure that the SET ACADCFG= is for 3 different directories.  It's the core
of the trick we use to run a single networked version of AutoCAD, by keeping
the configuration file local. I use similar tricks to start up "just plain
AutoCAD", AutoCAD with a certain Architectural menu, and AutoCAD with AEC menu
all using the same ACAD.exe and driver files, etc.


ΓòÉΓòÉΓòÉ 6. NETWARE TIPS ΓòÉΓòÉΓòÉ

As I was finishing up this helpfile, I received my January 1994 issue of OS/2
Monthly. There is an article on installing the requester (now called the
Network Client) on an OS/2 workstation. Worthwhile reading. I understand there
may be an article about running AutoCAD for Windows under WinOS2 in a future
issue.

Novell offers an OS/2 Workstation Kit for about $30.00 or so. It includes a
license for your entire site, so that's pretty reasonable. Also included is a
pretty good manual. Additional help is available in the Novell NOVOS2 forum
here on CIS. I am using the first release of the OS/2 2.0 requester with the
NSD 201...but I use the original NWTools utility, not the one that ships in the
NSD.

The Novell order number for the requester: 1-800-UPDATE1. The current version
is the "Netware Client for OS/2 v2.01", and it can also be downloaded from
CompuServe at GO NOVFILES, Client, OS/2.  There are important fixes available
from that same location.

Since OS/2 is a preemptive multitasking OS, you cannot have any hardware
conflicts. Two devices cannot (never say never, but...!) share the same IRQs.
Tracking down conflicts is an art in itself, especially in ISA machines such as
mine with lots of expansion boards.

The Novell requester installation is pretty nice...a PM interface with
installation selections. Files for OS/2 support will be installed on the server
if needed (do this once, other workstations will use these files) and on the
workstations. The files included on the workstation include the NWTOOLS, which
is a PM utility that I make extensive use of. Your CONFIG.SYS file will be
appropriately updated also...be sure you have the proper driver for your
network board available.

Your administrator should provide you with a login script for initial access to
the network. You can login from the OS/2 command line with the LOGIN command.


ΓòÉΓòÉΓòÉ 6.1. Using The NWTOOLS ΓòÉΓòÉΓòÉ

Here is a sample session to show you how to setup the NWTools to provide a
login and set up your preferred drive mappings.

First, open an OS/2 window or full screen session and do a LOGIN. If all goes
well you will be connected to the network. Great! Now click on your OS/2 System
file, open it, and then open the Startup folder. Leave it open for now...we're
going to put something in it later.

Open you drives object, and click on your Netware directory. You'll see the
NWTools object there. Double click on it to start the program. I have mine open
with the DRIVES and PRINTER PORTS under the TOOLS menu opened so I can see
these connections. Here you can click on a port and set up your printer
connections, or click on a drive letter and map your drive connections. What's
really nice is you can save your connections and recall them when needed.

So let's say you have all of you networks connections and mappings made. Save
them under NETWORK menu as, in this example, RWB.NWS. This saves your choice to
a file in the Netware directory named, amazingly, RWB.NWS. Okay...now go back
to your open Netware directory. Select RWB.NWS. Open the settings and choose
"Create Shadow." Choose the Startup Folder to put your shadow in. Good.

All right. Close all of your folders and open programs and do a Shutdown of the
system. Reboot. When the system starts RWB.NWS will be executed when the
desktop appears. You will then be asked to login and the NWTOOLS will appear on
your desktop. (Hint: Size and place the NWTools where you want on your desktop.
Then exit under the Network menu...you will be asked to SAVE the
position...click on Save Window Position. Now the next time you boot up, after
you login the network, your NWTOOLS will appear just where you want it on your
desktop.)

I have the NWTOOLS make my connections to our CalComp DrawingMaster plotter and
QMS 860 printer. I can change connections during a session if the need arises.
Of course you want to be careful about ending connections/mappings you really
need, like the AutoCAD directory you are working in!

When using anything from the Novell forums (like the requestor files for the
SERVER), be sure you unzip the files with "volume labels" onto a floppy,
otherwise the install program hangs. That might fit under the "gotchas". Your
Novell dealer should be able to help you.

Networking is an entity in itself and a lot of time can be spent getting things
up and running to *almost* everyone's satisfaction. I hope the above overview
gives you some insight and courage in tackling a network installation. Oh, btw,
we do run AutoCAD locally, not from the server.


ΓòÉΓòÉΓòÉ 7. HPFS ΓòÉΓòÉΓòÉ

Although I currently do not use HPFS, users do report that you can install and
run AutoCAD from an HPFS partition. AutoCAD cannot use long filenames, of
course, but you do gain other benefits from HPFS like minimal disk
fragmentation, speed increase with larger volumes, etc. Yet another reason to
request that OS/2 port. <g>


ΓòÉΓòÉΓòÉ 8. Credits ΓòÉΓòÉΓòÉ

That's about all I can think of for this particular help file.  Any comments,
tips, corrections, etc. would be appreciated and can be forwarded to me via
CIS: Richard Blalock 70274,1771.  Or if you use either the Internet or Prodigy
you may wish to give your feedback to Randy Holt.  He created an INF version of
this help file, and can be reached via the Internet: [e-mail] or on
Prodigy: NFRJ99A.  Randy will forward any comments he receives to me.

I would like to thank a number of people for spending their time helping me
with this file possible. I have noted a few in the text above, but many others
contributed corrections, tips, hints, additional items, and suggestions that
went into this file. Others have been quick to help other users in the AutoCAD
OpSystms/Networks subject in the ACAD forum. (GO ACAD)

They are >--|||--< (that's a trumpet I think):

Kendall Alton 72707,473

Jim Brown 72240,1157

Steven T. Dulek 100030,102

Don Gloistein 72662,2256

Bill Hinkle 75300,2050

Randy Holt [e-mail] (Internet) and NFRJ99A (Prodigy)

Christal Moreno 72520,3613

Rene Wagner 72704,3274

Rick Yoder 73457,521

Thanks to all!!!

- Richard


ΓòÉΓòÉΓòÉ 9. The End, Almost ΓòÉΓòÉΓòÉ

Good luck and just one more item...

Please write/call/fax Autodesk and respectfully demand an AutoCAD port to OS/2.
Ask other interested users to do the same.

Autodesk, Inc. Wishlist Department 2320 Marinship Way Sausalito, CA 94965

Below is a form letter to make it even easier...

---------------------------------cut here-------------------------------------

Autodesk, Inc. Wishlist Department 2320 Marinship Way Sausalito, CA 94965

To whom it may concern:

I would like to see a port of AutoCAD for OS/2 2.X. I prefer this environment
for my work and I am sincere in my desire to purchase the port when it becomes
available.

My office has ____ copies of AutoCAD and we would upgrade ____ copies to the
OS/2 version.

Thank you for your consideration.

Sincerely,

________________________________________________________

(Your Name)

________________________________________________________

________________________________________________________

(Address)

-----------------------------cut here--------------------------------

 Be sure to copy John Lynch, Vice President of Product Development, Godfrey
Sullivan, VP of Americas Division, and Ms. Carol Bartz, CEO.


ΓòÉΓòÉΓòÉ 10. Sample DeskTop ΓòÉΓòÉΓòÉ