#Mouse Lock UP
11 messages in this thread
Anne,
My mouse is locking up my system when I move some of the slide bars in the
Material Editor like the diffuse light side bar. Any ideas on how to fix this
problem. I using a logitech 3 buttom mouse.
Thanks
Wayne
<< My mouse is locking up my system when I move some of the slide bars in the
Material Editor like the diffuse light side bar. Any ideas on how to fix this
problem.>>
Sounds like a memory conflict. Below are instructions to help you diagnose the
problem.
-b
Title: Clean system boot; diagnostics for memory conflict…
Description:
To confirm that the problem is caused by a memory conflict, re-start the
computer with simplified settings (a 'stripped system') and see if the problem
goes away.
For DOS-only computers, a stripped system means that the computer is rebooted
without terminate and stay resident (TSR) programs nor device drivers that are
not absolutely necessary for the operation of the operating system and
computer. The Autodesk program should also be configured for VGA display if
possible, to rule out display driver conflicts.
To reboot into a stripped system for 3D Studio and Animator Pro, change the
system files as follows:
CONFIG.SYS should contain only:
FILES=40
BUFFERS=20
AUTOEXEC.BAT should contain only:
PATH=<your path>
PROMPT=<your prompt>
You may want to use the DOS SYS command to create a bootable floppy for this
trouble-shooting exercise and place these simplified system files on the
diskette. Or, you may edit the existing CONFIG.SYS and AUTOEXEC.BAT files
currently on the hard disk (make back-up copies first). Make sure you have a
bootable DOS floppy on hand, just in case the computer has trouble rebooting.
Note: Quarterdeck QEMM users may find it helpful to review the QEMM
trouble-shooting documentation and use the Analyze utility to track down memory
conflicts.
Trouble-shooting:
If the program now operates correctly, the next step is to determine which
program or driver in your system files is causing the conflict. Edit the
CONFIG.SYS and AUTOEXEC.BAT files, adding one device driver or TSR command at
a time, rebooting, and starting 3D Studio/AAPRO until the error reappears.
When the error happens, the last item you added to the configuration is
probably the trouble maker. Once we know which drivers are conflicting, we can
determine the proper course of action.
If you are using special display adapters (for example, a Targa frame buffer),
you should check the documentation that came with the display driver to see if
special memory settings or EMS exclusions are needed.
<< My mouse is locking up my system when I move some of the slide bars in the
Material Editor like the diffuse light side bar. Any ideas on how to fix this
problem.>>
Brian,
I was able to correct this problem with my system by changing the VIBRANT
driver from 640×480 by 16M colors to 640×480 by 64K colors. My system does not
lock up when moving the diffuse side bar in the Material Editor.
What does this tell me? I'm using an Orchid Farenheit Card with 2 Meg of
Vram. I did not have this problem before. Is there something wrong with my
Vram or a problem with the memory maping of the video? Or none of the above.
Wayne
<< What does this tell me? I'm using an Orchid Farenheit Card with 2 Meg of
Vram>>
This tells you that the Vibrant drivers and your Mouse drivers are most likely
experiencing memory conlicts. I would strip the system and see if the problem
still happens in a vanilla environment. I have included some help on stripping
the system below.
-Brian
Title: Clean system boot; diagnostics for memory conflict…
Description:
To confirm that the problem is caused by a memory conflict, re-start the
computer with simplified settings (a 'stripped system') and see if the problem
goes away.
For DOS-only computers, a stripped system means that the computer is rebooted
without terminate and stay resident (TSR) programs nor device drivers that are
not absolutely necessary for the operation of the operating system and
computer. The Autodesk program should also be configured for VGA display if
possible, to rule out display driver conflicts.
To reboot into a stripped system for 3D Studio and Animator Pro, change the
system files as follows:
CONFIG.SYS should contain only:
FILES=40
BUFFERS=20
AUTOEXEC.BAT should contain only:
PATH=<your path>
PROMPT=<your prompt>
You may want to use the DOS SYS command to create a bootable floppy for this
trouble-shooting exercise and place these simplified system files on the
diskette. Or, you may edit the existing CONFIG.SYS and AUTOEXEC.BAT files
currently on the hard disk (make back-up copies first). Make sure you have a
bootable DOS floppy on hand, just in case the computer has trouble rebooting.
Note: Quarterdeck QEMM users may find it helpful to review the QEMM
trouble-shooting documentation and use the Analyze utility to track down memory
conflicts.
Trouble-shooting:
If the program now operates correctly, the next step is to determine which
program or driver in your system files is causing the conflict. Edit the
CONFIG.SYS and AUTOEXEC.BAT files, adding one device driver or TSR command at
a time, rebooting, and starting 3D Studio/AAPRO until the error reappears.
When the error happens, the last item you added to the configuration is
probably the trouble maker. Once we know which drivers are conflicting, we can
determine the proper course of action.
If you are using special display adapters (for example, a Targa frame buffer),
you should check the documentation that came with the display driver to see if
special memory settings or EMS exclusions are needed.
Brian,
I ran my system stripped clean as you suggested except I did include the
mouse.sys driver in the config.sys. The system still locks up in the material
editor with the vibrant driver set to 640×480 with 16 M colors.
What do I do next?
Wayne
<<The system still locks up in the material editor with the vibrant driver set
to 640×480 with 16 M colors.>>
What about at different resolutions/color depths. Does it still lock up?
-b
Brian,
With the system stripped, 3DS works with 64K colors in the material editor.
This system has no problems with the rendering display set to 16M colors by 640
x 480.
Wayne
in that case the problem might be related to the Vibrant Driver at that
particular resolution/color depth. If you have the time, you might fill out the
Vibrant BUG form (VIBBUG.TXT).
-Brian
Brian,
How do I get the Vibbug.txt form?
Wayne
File Info for VIBBUG.TXT
Section: HWare/OpSys/Video Contributor: 70421,76 Size: 1053
Submitted: 11/18/94 Type: Text Accesses: 339
Title: Bug form for 3D Studio Vibrant drivers
Keys: AUTODESK 3D STUDIO VIBRANT BUG 3DS FORM REPORT BUGS
Please use the information in this text file as a checklist to help report
your problems
with 3D Studio video drivers. You may report your problems to SYSOP, or Nik
Grant, 70421,76. Thank you.
This is a text file and can be viewed on line.
Hi Wayne,
<<…lockups.. >>
What happens when you follow the following steps.. ?
Title: Clean system boot; diagnostics for memory conflict…
Description:
To confirm that the problem is caused by a memory conflict, re-start the
computer with simplified settings (a 'stripped system') and see if the problem
goes away.
For DOS-only computers, a stripped system means that the computer is rebooted
without terminate and stay resident (TSR) programs nor device drivers that are
not absolutely necessary for the operation of the operating system and
computer. The Autodesk program should also be configured for VGA display if
possible, to rule out display driver conflicts.
To reboot into a stripped system for 3D Studio and Animator Pro, change the
system files as follows:
CONFIG.SYS should contain only:
FILES=40
BUFFERS=20
AUTOEXEC.BAT should contain only:
PATH=<your path>
PROMPT=<your prompt>
You may want to use the DOS SYS command to create a bootable floppy for this
trouble-shooting exercise and place these simplified system files on the
diskette. Or, you may edit the existing CONFIG.SYS and AUTOEXEC.BAT files
currently on the hard disk (make back-up copies first). Make sure you have a
bootable DOS floppy on hand, just in case the computer has trouble rebooting.
Note: Quarterdeck QEMM users may find it helpful to review the QEMM
trouble-shooting documentation and use the Analyze utility to track down memory
conflicts.
Trouble-shooting:
If the program now operates correctly, the next step is to determine which
program or driver in your system files is causing the conflict. Edit the
CONFIG.SYS and AUTOEXEC.BAT files, adding one device driver or TSR command at
a time, rebooting, and starting 3D Studio/AAPRO until the error reappears.
When the error happens, the last item you added to the configuration is
probably the trouble maker. Once we know which drivers are conflicting, we can
determine the proper course of action.
If you are using special display adapters (for example, a Targa frame buffer),
you should check the documentation that came with the display driver to see if
special memory settings or EMS exclusions are needed.