PDA

View Full Version : epsxe crashes ati drivers


kingkilburn
April 15th, 2004, 06:14
Since i put epsxe on my lap top(but not right after) it crashes my graphics drivers. it started about 2 weeks after i put it on, but i haven't installed any thing since then.

gig4ls
April 15th, 2004, 06:49
Since i put epsxe on my lap top(but not right after) it crashes my graphics drivers. it started about 2 weeks after i put it on, but i haven't installed any thing since then.

I have an ATI Radeon, and I can't get the config wizard to work. After I select the bios, when I click next to select the graphics drivers, it takes a while to respond, then comes back with a popup dialog (windows error message type dialog box) that says "outofsync.bmp" and after that two lines of garbled characters.

kingkilburn
April 15th, 2004, 06:52
i have the same prob but not every time.

kingcold9
April 15th, 2004, 07:13
try omega drivers, they are based on the 4.4 catalyst atm and are the best modded drivers for ATI cards, they can be obtained at http://www.omegacorner.com/

if your not sure how to uninstall/rollback drivers dont install them but they just might fix your problem.

gig4ls
April 15th, 2004, 17:27
Yeah, I only occasionally get the outofsync.bmp error. However, another problem is here...when I play any game, it will run for about 3-5 seconds, then it will say: "Error, recompile block too large".
Does anyone know what this means?

gig4ls
April 18th, 2004, 16:31
Ok, I've done a little more experimenting, and I can give a more accurate description of my problems. First, here are my system specs:

System specs:
AMD Athalon XP 1500+ (1.29 GHz)
1.00 GB RAM
ATI Radeon 9600 pro
Running Windows XP
More than enough harddrive space (21.3 gb free on the games partition, 23.5 gb free on my windows partition)
If I'm missing anything else, I'm sorry. I'll find it out as soon as someone tells me.

ASPI layer stuff:
WINASPI32.DLL 4.6
WINASPI.DLL 4.6
APSI32.SYS 4.6
WOWPOST.EXE 4.6

Ok, description of my problems.
1)
The first time I run ePSXe, no matter what I do (whether I go into wizard config, any other config, or start a game, the program will hang for anywhere from 1-10 seconds, and after a while, give me an error message in a popup window saying: "outofsync.bmp" and some garbage after it.
The program will not crash.
2)
The next time I run it, it will work and return no errors, until I start playing a game.
If I run any of the bioses that I have, it will not screw up.
If I run a CD-ROM (like...a disc that would work in my now-dead PSX), the program will run fine.
If I run an iso, the program will start up, then after about 3 seconds of intro (which runs too fast, I might add, even though I set the fps skip to 60. The game itself ran fine last time before the error: ), the program crashes. The popup error message it gives me says: PSX error: compile block too large. I might add this only happens when I try to use a few isos. I suppose it is possible that my isos in question got corrupted, but I'd be surprised if they did, since I put them on this computer over a network.

I'm sure that the second is isolated, but can anyone tell me why I'm getting the first problem? Sorry for making such a long post, but I tried my best to be detailed.

JericoPaladin
July 31st, 2004, 20:49
gig4ls, I also get that message (compile block too large), and I'd also like to know what that means. It only occurs when I try to load an iso (.bin), though I don't have any other types of files for use with ePSX (just got it) so I don't know if it'd happen with them, but I guess it doesn't

n_w95482
July 31st, 2004, 21:04
gig4ls, I also get that message (compile block too large), and I'd also like to know what that means. It only occurs when I try to load an iso (.bin), though I don't have any other types of files for use with ePSX (just got it) so I don't know if it'd happen with them, but I guess it doesn't
Have you tried remaking the file? Have you tried using Mooby's plugin or Daemon Tools?

Betamax
July 31st, 2004, 22:02
It's 'recomplie block too large' :p. What it means is that when "translating" from psx code into pc code, the output was too large.

In laymans terms about 99.95% of the time that means your game image file is fecked. Try remaking it, or using the cd.