#Stealth In Control bug
3 messages in this thread
#Stealth In Control bug — declared parent_msg_num=(none), resolved parent_id points to #(none)
You might want to try the new beta driver that we have just released. The file
name for the VLB ios VVL210.exe.
I am not aware of DOS box problems with the VLB version of the Viper. What
exactly are the problems you are having with them?
–Wayne Johnson
Diamond Multimmedia Systems' ES Dept.
#99467-#Stealth In Control bug — declared parent_msg_num=99467, resolved parent_id points to #99467
>>You might want to try the new beta driver that we have just released. The
file name for the VLB ios VVL210.exe.<<
Seemed like a good idea. I took them home and tried installing them. Didn't
seem to be a good idea. I forget why off hand. But I didn't feel like wrestling
with it any, so I just axed it and reverted. Maybe later this week I'll have
some patience.
But then, maybe not. I've downloaded the drivers over in the Win95 forum, and
since that is what my system is doing right now… I had to move Win3.1 over
and it wouldn't run right now, I don't really want to mess with that, just to
test betas. I think I'll wait on it for now maybe.
>>I am not aware of DOS box problems with the VLB version of the Viper. What
exactly are, the problems you are having with them?<<
I forget when it happened. Didn't used to be a problem for me at all. Then (no
doubt, after some forgotten change, and some drastic ones have happened) all of
a sudden, my DOS boxes stop. And that is literally. Big black screen with no
cursor and no response from the system to my inputs. It really likes it then,
if I press the reset button. It's a given now: run a dos box, reset computer.
It might have been when I downloaded the newest Windows drivers from here and
tried to get them running. It might not have been.
I'm pretty clueless as to what I might diddle with in order to try to fix it.
It's been a bad .5 year for my computer and I, so I'm pretty much on very
frayed thread.
Thanks – gruhn
#100137-Stealth In Control bug — declared parent_msg_num=100137, resolved parent_id points to #100137
>>Seemed like a good idea. I took them home and tried installing them. Didn't
seem to be a good idea. I forget why off hand. But I didn't feel like wrestling
with it any, so I just axed it and reverted. Maybe later this week I'll have
some patience.
But then, maybe not. I've downloaded the drivers over in the Win95 forum, and
since that is what my system is doing right now… I had to move Win3.1 over
and it wouldn't run right now, I don't really want to mess with that, just to
test betas. I think I'll wait on it for now maybe.<<
I can understand that.
>>I forget when it happened. Didn't used to be a problem for me at all. Then
(no doubt, after some forgotten change, and some drastic ones have happened)
all of a sudden, my DOS boxes stop. And that is literally. Big black screen
with no cursor and no response from the system to my inputs. It really likes it
then, if I press the reset button. It's a given now: run a dos box, reset
computer.
It might have been when I downloaded the newest Windows drivers from here and
tried to get them running. It might not have been.<<
Does it occur with the VGA driver that ships with Windows? What version of the
driver are you using? Try a 'clean boot':
Strip your CONFIG.SYS down to the following:
device=c:\windows\himem.sys
files=40
buffers=30
Run Windows and see if the problem persist. If not, a device driver in your
CONFIG.SYS or AUTOEXEC.BAT was causing the problem. You can remark out all the
lines, then add them back one at a time until you find the culprit.
If the problem persists, install a second copy of Windows onto your system,
into a directory such as WIN2. Then install the Diamond drivers onto this
second copy. Use the CONFIG.SYS from above, and see if the problems persist.
If not, some item in your original Windows installation was causing the
problem, and you can reload Windows programs and drivers into the second copy
until you find the culprit.
Dave Johnson
Diamond Multimedia, ES Dept.