View Full Version : Not enough Memory for jump table, HELP ME!
jelun005
March 11th, 2006, 23:47
Hi everyone!
When I start my project 64k, an error message appear:
Not enough memory for jump table
and then
Failed to allocate Memory
I have read forums about this but nothing works, please help me!:(
Game boy2
March 12th, 2006, 00:05
try to get some more memory?
jelun005
May 5th, 2006, 21:26
I have a lot of memory. My brother has the same computer as me and it works for him. We got the same free memory when we are trying to start Project 64k, but it only works for him. What is wrong?
Agozer
May 5th, 2006, 21:34
Exactly the same computer down to the exact same hardware?
Bongo Kong
May 5th, 2006, 21:45
Let us know your computer's specs and we may help you better
jelun005
May 5th, 2006, 21:47
yes, exactly the same computer
jelun005
May 5th, 2006, 21:51
System:
Microsoft Windows XP
Professional
Version 2002
Service Pack 2
Computer:
Intel(R)
Celeron(R) CPU 2.80GHZ
2.80GHZ, 224 MB RAM
I hope this will help you.
Agozer
May 5th, 2006, 21:53
Graphics card (the most important part actually)?
jelun005
May 5th, 2006, 22:46
How do I know that? Can I find it somewhere in the computer?
Agozer
May 6th, 2006, 00:13
Run dxdiag. Check the Display tab.
MooglyTwo
May 6th, 2006, 01:54
224 megs, running Windows XP? Wow, that's a seriously crappy amount of RAM. I don't know who told you that that's a lot, but you must be really gullible.
squall_leonhart
May 6th, 2006, 02:10
watch your mouth moogly.
windows xp can run perfectly well on 128mbs of memory, and i would know becoz im the one that did it.
Mouser X
May 6th, 2006, 02:39
My brother got WinXP to run off of an install that took up about 300-400mb of harddrive space. Considering that it usually takes nearly a gig, I'd say that's pretty good. However, he apparently removed some essential software, since he couldn't install, or uninstall, anything, including additional hardware, or software... He got it running in a much more useable manner at about 500mb. Though, that machine got fried (I think the power supply went bad), so he lost that install. He hasn't bothered to cut down on WinXP's install since then, so he's not to sure what you can remove without it not working anymore. Though, I suppose with the way HDDs are these days, 300-500mb isn't as big of a deal anymore as it once was. Mouser X out.
jelun005
May 6th, 2006, 09:26
Operative: Microsoft Windows XP Professional (5.1, build 2600)
Language: Swedish (National settings: Swedish)
System manufacture: Acer
System model: AP F1b
Bios: Phoenix - AwardBIOS v6.00PG
Professor: Intel(R) Celeron(R) CPU 2.80GHz
Memory: 224MB RAM
(växlingsfil) :256MB in use, 289 MB is available
DirectX-version: DirectX 9.0c (4.09.0000.0904)
Scren: (flap number 3)
Entity
Name: SiS 650/651/740/661FX/741/760 series
Manufacture:
Circuit type: SiS 661FX Rev 01
DAC-type: Internal
estimated total memory: 32.0 MB
Current screen mode: 1024 x 768 (32 bit) (60Hz)
Screen: standard screen
I hope the translation is correct.
Agozer
May 6th, 2006, 11:35
I'd say that the SiS chip is your problem.
jelun005
May 6th, 2006, 16:51
why
Doomulation
May 6th, 2006, 17:38
Sis has nothing to do with the memory problem. You shouldn't be running XP with that little amount of RAM let alone run games or emulators.
The graphics card may cause glitchy games because it's old and bad, though, if you get the emulator running.
Agozer
May 6th, 2006, 19:57
Sis has nothing to do with the memory problem. You shouldn't be running XP with that little amount of RAM let alone run games or emulators.
The graphics card may cause glitchy games because it's old and bad, though, if you get the emulator running.
Well since the SiS in and intergrated chip, it shares RAM. So it isn't exactly alleviating the problem either.
squall_leonhart
May 8th, 2006, 19:21
Sis has nothing to do with the memory problem. You shouldn't be running XP with that little amount of RAM let alone run games or emulators.
The graphics card may cause glitchy games because it's old and bad, though, if you get the emulator running.
has nothing to do with memory
anything loaded into memory is dumped off into the pagefile when a memory aggressive application is loaded.
Doomulation
May 8th, 2006, 19:49
has nothing to do with memory
anything loaded into memory is dumped off into the pagefile when a memory aggressive application is loaded.
Has everything to do with memory. While I may not know the inner workings of Windows, such little amount of RAM is just a killer. How much must Windows unload into the page file?
Also note that while Windows increases the page file, some applications may be denied memory. In any case, the memory is certainly a bottleneck, though I haven't stated it is the source of the problem.
Nevertheless, running Pj on a machine with such little memory is nothing sort of disaster.
squall_leonhart
May 8th, 2006, 20:54
mate, i used to run PJ64 on 256mbs of memory. and it worked pefectly fine. its more likely either a corrupt pagefile or bad video drivers.
Doomulation
May 8th, 2006, 21:15
Once more, I repeat, I am not saying it it is the cause of the error. But it is disaster to run XP with such little RAM. It isn't designed for it and it never will be.
squall_leonhart
May 8th, 2006, 22:13
THE REQUIRED MEMORY SIZE IS 256MB it says so on the box and on MS's site
it is designed to run on 128mb of ram without problems.
Windows XP Professional System Requirements
Published: August 24, 2001
Here's What You Need to Use Windows XP Professional
•PC with 300 megahertz or higher processor clock speed recommended; 233 MHz minimum required (single or dual processor system);* Intel Pentium/Celeron family, or AMD K6/Athlon/Duron family, or compatible processor recommended
•128 megabytes (MB) of RAM or higher recommended (64 MB minimum supported; may limit performance and some features)
•1.5 gigabytes (GB) of available hard disk space*
•Super VGA (800 x 600) or higher-resolution video adapter and monitor
•CD-ROM or DVD drive
•Keyboard and Microsoft Mouse or compatible pointing device
its funny.. the people at MICROSOFT appear to agree with me on this point.
oh wait.. IT WAS THEM I GOT THE INFO IN THE FIRST PLACE.
pls take your 6000+ posts and go learn something before posting again.
squall_leonhart
May 8th, 2006, 22:13
stupid double post.
why is there no flood filter on this site...
Doomulation
May 8th, 2006, 22:26
Don't take everything what they write literally. XP itself easily consumes about 256 mb of memory, not to mention all the other programs you have running easily consumes up to 512 mb of memory. I know this, as I have witnessed it MYSELF.
Now let's stop this stupid discussion before it turns into a flamewar.
squall_leonhart
May 9th, 2006, 00:34
it won't become a flamewar.
on systems with 256mb and less alot more page swapping occurs.
i have and can again set up a XP installation to run in less then 100mbs simply by disabling the eye candy.
gman932
May 9th, 2006, 04:57
I have the same problem with a
Athlon xp +2800
1g ddr....400 or something i think been awhile
ati 9800 pro
i think the next patch might fix it ...but if anyone finds anything out... let us know
squall_leonhart
May 11th, 2006, 03:23
what ati driver are you using?
Dragonix
May 11th, 2006, 21:33
i got the same problem with pj64k, my system:
MotherBoard: MSI K8T Neo2-FIR (latest drivers)
CPU: AMD Athlon64 3200+
Ram: 1024MB (DualChannel (2*512))
GraphicAdapter: nVIDIA 6600GT (128MB Ram) (latest drivers)
OS: XP Prof - Service Pack1 (+All updates)
but on my second system, the pj64k runs without any problems:
CPU: AMD AthlonXP 1900+
Ram: 768 MB
MoBo: Asus A7V-600X
GraphicAdapter: ATi Radeon 9600XT (with the normal, latest catalyst driver)
OS: XP Prof - Service Pack1 (+All updates)
i would be very happy if you could help me!
edit: the windows "swap" file has on both systems the same size!
gman932
May 11th, 2006, 23:50
what ati driver are you using?
omega 6.03 drivers......tried with 6.4 ati drivers too with no luck
please can someone tell me if there is a link or a file of somesort in this link posted under Radeon video card users, click here please
http://www.emutalk.net/showthread.php?s=&postid=60635#post60635
thanks
squall_leonhart
May 12th, 2006, 21:43
i don't have permission to access it.
squall_leonhart
May 12th, 2006, 21:45
i got the same problem with pj64k, my system:
MotherBoard: MSI K8T Neo2-FIR (latest drivers)
CPU: AMD Athlon64 3200+
Ram: 1024MB (DualChannel (2*512))
GraphicAdapter: nVIDIA 6600GT (128MB Ram) (latest drivers)
OS: XP Prof - Service Pack1 (+All updates)
but on my second system, the pj64k runs without any problems:
CPU: AMD AthlonXP 1900+
Ram: 768 MB
MoBo: Asus A7V-600X
GraphicAdapter: ATi Radeon 9600XT (with the normal, latest catalyst driver)
OS: XP Prof - Service Pack1 (+All updates)
i would be very happy if you could help me!
edit: the windows "swap" file has on both systems the same size!
research leads me to believe that the MSI K8T (Via?) board requires SP2. it has updated support for the chipset
Dragonix
May 12th, 2006, 23:16
research leads me to believe that the MSI K8T (Via?) board requires SP2. it has updated support for the chipset
yes, via k8t800. ok, i'll try that later, thx
squall_leonhart
May 12th, 2006, 23:32
ok well. SP2 has updated Drivers for VIA based chipsets and has an updated memory management handler.
SP1 had some leaks in the memory management and SP2 patched that.
Powered by vBulletin® Version 4.1.11 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.