Troubleshooting a Memory Error with SB.Drv Driver

  • Thread starter Delzac
  • Start date
In summary: Thanks for the help though. In summary, the conversation discusses the issue of trying to install an old DOS game on a modern operating system, and the error message that appears regarding not having enough memory to load the SB.Drv driver. Suggestions are given to allocate more memory and resources, partition the drive and install an old copy of DOS, or use a memory resident program. The conversation also includes attempts to solve the issue using the Debug command and creating a memory resident program, but these do not work. The conversation ends with the suggestion to try using DOSBox, but this also does not work. Overall, it seems that there is no solution to playing the game on a
  • #1
Delzac
389
0
Hi all,

i tried to install a game(very old one) on DOS(i know there is no DOS for XP, but nvm), not matter which version of OS i use(window 95, 98 bla bla bla) this erroe also comes out...

memory not enough to load the SB. Drv driver
SB.Drv driver seem not the one come along with the game"

What does is mean and can anyone help me to solve this.

P.S. i tried to allocate more memory and resource by right clicking the program, properties, then memory and maxing all the viarables there.

Any help will be greatly appreciated. thx!
 
Computer science news on Phys.org
  • #2
I'd suggest partitioning your drive and installing an old copy of DOS if you want to run old DOS games.

- Warren
 
  • #3
hmmm, how do u partition ur drive.

And u can actually install DOS? how? is there a programme in the net?

Thx for the help
 
  • #4
This problem was caused by a bad calculation of the size of phyical memory in the machine.
They used a 16 bit register that could overflow.

Real DOS took up much more low memory than the vm does.
It was also a problem with later versions of real DOS.
We used to load memory residient programs to take up enough low memory to fix the problem or edit the .exe file to fix it.
Never tried loading one of these in the vm.

You should be able to edit the .pif file to limit the amount of memory.
256k should be a good value.
Right click the .exe or .com file to access the .pif editor.

Chances are that you will have clock speed issues with this game, if you do get it to run.
 
  • #5
so do i have to load a memory resident program? i tried to right click and lower thw amount memory to 256, but it didn't work.

where can i get a memory resident program?

Thx
 
  • #6
Delzac said:
so do i have to load a memory resident program? i tried to right click and lower thw amount memory to 256, but it didn't work.

where can i get a memory resident program?

Thx
No idea on the memory resident thing.
Could probably write one.
IIRC its only a couple lines of code.

What's the name of the game?
 
  • #7
I just thought of another way.
At the Dos prompt type

Debug [filename]

At the Debug prompt type g

This should push it high enough in memory.
 
  • #8
Name of the game : Amika <精武战警> ( it is a chinese game)

BTW the debug thingy didn't work here is what is type.

" C:\>debug amika
File not found
-g
C:\> "

that is what happen, i am rather sure that the folder is there, but this still happens. i will look up how to write the program and wil get back to you. :)
 
  • #9
Hi again,

i dun think it is that easy to write the program, take a look at the link below,

http://web.sau.edu/LillisKevinM/csci240/masmdocs/programmersguide/15LMAPGC11.pdf#search=%22Memory%20resident%20program%20how%20to%20write%22 [Broken]

i looks like gibillish to me, any other alternatives?
 
Last edited by a moderator:
  • #10
Delzac said:
Name of the game : Amika <精武战警> ( it is a chinese game)

BTW the debug thingy didn't work here is what is type.

" C:\>debug amika
File not found
-g
C:\> "

that is what happen, i am rather sure that the folder is there, but this still happens. i will look up how to write the program and wil get back to you. :)
I don't have that particular game.

You have to switch to the directory the game is in first.
CD \amika if it is in the c:\amika directory
Also you need to type the entire file name.
For example debug amika.exe
.com was also a common exension.
 
  • #11
Delzac said:
Hi again,

i dun think it is that easy to write the program, take a look at the link below,

http://web.sau.edu/LillisKevinM/csci240/masmdocs/programmersguide/15LMAPGC11.pdf#search=%22Memory%20resident%20program%20how%20to%20write%22 [Broken]

i looks like gibillish to me, any other alternatives?
The green parts are how it should respond
You must type this exactly. <enter key> is just hit enter.
And the responses should match exactly.

In the command window type
debug
-a
xxxx:100 mov ax,3100
xxxx:103 mov dx,1000
xxxx:106 int 21
xxxx:108 <enter key>
-rcx
CX 0000
:
100
-n memres.com
-w
Writing 100 bytes
-q
c:\xxxxxx>

You now have a program called memres.com
It's in whatever directory you were in when you started debug.
when you run it, it will take up 1000h (or 4k) bytes of memory.
 
Last edited by a moderator:
  • #12
i couldn't get my com to spit the green words, it just gave me

16E9:2382
16E9:2385

and stuff, but nvm i think there is no chance for me to play that game ever again. Thanks for the help. :)
 
  • #13
Maybe you could give DOSBox a try?
 
  • #14
Delzac said:
i couldn't get my com to spit the green words, it just gave me

16E9:2382
16E9:2385

and stuff, but nvm i think there is no chance for me to play that game ever again. Thanks for the help. :)
Would it help if I mentioned that 'xxxx' ment undefined? It can be any 16 bit hex number?
16E9: would be valid, but high. I would expect something more like 12xx or 13xx.
I have no idea how you got to 2382. The "a" command always starts at 100 unless you specify something else.
 
  • #15
i have no idea also, i tried DOSbox b4 no use. It is able to load the game, but after the screen is blank, after 4 to 5 secs i closes by itself.
 

What is a driver problem?

A driver problem refers to an issue with the software that connects a computer's hardware components to its operating system. It can cause malfunctioning or non-functioning hardware, and can be caused by outdated, corrupted, or missing drivers.

How do I know if I have a driver problem?

You may have a driver problem if you are experiencing issues with your computer's hardware, such as devices not working or malfunctioning. You can also check your device manager for any yellow warning symbols, which indicate a problem with a driver.

How can I fix a driver problem?

The first step to fixing a driver problem is to identify which driver is causing the issue. You can do this by checking the device manager or using diagnostic tools. Once the problematic driver is identified, you can update it to the latest version or reinstall it to fix the issue.

What can cause a driver problem?

A driver problem can be caused by a variety of factors, such as outdated or incompatible drivers, corrupted system files, or hardware conflicts. It can also be caused by user error, such as accidentally uninstalling a necessary driver.

Is there a way to prevent driver problems?

While driver problems can occur unexpectedly, there are some ways to prevent them. Regularly updating your drivers to their latest versions, avoiding downloading drivers from unreliable sources, and being cautious when making changes to your system can help prevent driver problems.

Similar threads

  • Computing and Technology
Replies
4
Views
2K
  • Computing and Technology
Replies
4
Views
3K
  • Computing and Technology
Replies
6
Views
5K
  • Computing and Technology
Replies
2
Views
3K
  • DIY Projects
Replies
23
Views
4K
  • Computing and Technology
Replies
18
Views
6K
  • Computing and Technology
Replies
15
Views
4K
  • Computing and Technology
Replies
2
Views
2K
  • Special and General Relativity
Replies
13
Views
2K
Back
Top