PDA

View Full Version : OS requirements for PCSX2?


Dorkboy
December 8th, 2006, 01:45
I feel stupid for asking these, but I haven't seen it actually mentioned elsewhere, so I wanted to ask. (And I've looked in the forums and on the main page already, and I freely admit I very well may be blind and not see the answers.)

1st - I see a lot of mention that one wants bigger/better hardware to run this, but I haven't seen anything specificing OS.

Yes I know that WinXP Pro SP2 is prefered, but 'should' both the TLB and VM versions work on Sp1? (Feeling silly, but Win2k? ;) )

2nd - Looking though past posts - I've seen mentioning the problem with VM not running. ("Unable to allocate enough memory", which for me turned in to the "cannot allocate mem addresses 0x20000000-0x40000000, err: 487". This is the one problem which seems that multiple people get.)

From what is mentioned it's a 'memory' issue, and the program can't get the OS to allocate enough resources to run. Most seem to fix this with reinstalling XP, but not all. There also doesn't seem to be a definate 'fix' or area to look in to to see what's going on.

In playing with this, I'm curious to see if any of the Dev's think this might be related to chipset or directx drivers?

(Thank you for taking your time to read this. :D )

emwearz
December 8th, 2006, 01:48
The VM version requires Windows XP Pro or Home with SP2.

The TLB Works on most others Windows OS's from I would guess 98 and up (Maybe be 2k). Of course the error would be a memory issue as VM stands for Virtual Memory. Sometimes for whatever reason, pcsx2 and windows wont get along when it comes virtual memory.

cyclonmaster
December 8th, 2006, 01:50
TLB works with Windows XP SP1 or SP2 or Win2K. But VM only works with Windows XP SP2.

thc
December 8th, 2006, 07:30
"cannot allocate mem addresses 0x20000000-0x40000000, err: 487"

Devs could help this a bit by reserving less memory in winmain.c ( as not whole 1G [message is wrong], is used elsewhere ), not that it will help much.

Anyway most likely You get this due some program injecting pcsx2.exe using VirtualAllocEx ( virus/spy/ad/malware/antivirus ).