Since there seems to be a million kazillion threads, im going to do this in effort to clean up this forum. If you have a issue with surreal64 loading or playing games read here first, and try any suggestions in relation to your problem. If it is not fixed after trying, then reply with your specific problem.

Firstly, are you having problems loading the emulator? Does it freeze on loading/black screen? Check these things..

Are you running a 4977 bios? (One thats been patched for lba48) Or 4978? Both are known to cause issues -
Reflash with a evox bios, or 4976.06 or 4979.06/67 +

Do you have all the correct files and folders on your xbox? (most specifically the media directory, default.xbe and surreal.ini)

Are you using a old modchip such as xecuter 1, or enigmah/xtender? - Try patching first (all your xbe files)with dexbe to retail, and if that doesnt work your going to need to use Phoenix Bios Loader (PBL) to boot another bios into memory before launching. This will not go into support for using PBL. Please use at your own descretion.

People who cannot get it to load by patching with dexbe should also try xbe patcher

Are you having a problem with your Roms not showing up?

First and formost, have you edited the Surreal.ini *before* you run it to point to your roms?

You need to change it to be Rom Path=F:\Path\to\your\roms . If you are putting the roms in the 'roms' folder inside your surreal64 install dir, then make the Rom Path=D:\Roms

If you have already ran Surreal64, then your ini was saved to the TDATA folder, and you have to edit it there.

/E/TDATA/a64fea57/Surreal.ini <-- That is the path to it. Simply edit that file right there to reflect the directory of your roms, and then launch the emu and hit the 'refresh' button in the lower right hand corner.

Are you trying to run Roms off the dvd and cannot get it to work?

First, you must create a xiso of your roms. Create a New folder...name it whatever you please. Go into it, and make a directory called "Roms". Put all of your N64 Roms in there. Use Simple Xiso and select that 'new directory' that you created for creating a xiso. The point is to create a xiso with a roms folder on there, and NOT your roms on the root directory of the disk. If you put them directly on the disk it will not work. Create the xiso, and burn using record now max or nero or whatever your favorite burning software is. Make sure you are using media your xbox can read, i.e. if you have a samsung you can use cd-r, if not you can only use cd-rw/dvd-r/dvd+r. If you have not launched surreal64 on your xbox, then you can edit your ini right there to say A\:Roms or if you have already launched it you must edit /E/TDATA/a64fea57/Surreal.ini to reflect A:\Roms . Relaunch Surreal64 with your disk in the tray and hit the refresh button.

Are certian Roms not showing up?

Check your roms!

GOODN64

Download Goodn64, bin.zip, and good windows. Extract them all to a directory of your choice. In goodwindows select 'Good tool' as your mode, and then select Nintendo 64 as your system. The rom directory is in the lower left corner, simply choose the directory of your roms, then hit the big button on the lower right (Should say Goodn64.exe rename). It will put all of your roms renamed properly in a N64Ren folder, and any bad/unknown in another.

If a specific rom is not showing up, and you have renamed it, check and make sure the surreal.ini has a entry for it. Example...

You have Banjo-Kazooie (E) [!].zip and for some reason its not showing up. Open surreal.ini with a text editor (most of you will use notepad, but use ultraedit if you have it).

Do a search for Banjo until you find the entry for that rom. In this case..it would be

[733FCCB1-444892F9-C:50]
Game Name=Banjo-Kazooie
Alternate Title=Banjo-Kazooie (E) [!]
Comments=Playable
Preferred Emulator=0

If your rom has been renamed by goodn64, and does not show up, you should not be able to find it in the surreal.ini. This is merely a confirmation of what exactly is happening. If this is the case, obtain the correct version of the rom. All (U) and (E) [!] roms are supported (to show on the romlist). Also, if your zip file is compressed a certian way (dont ask me which way) surreal may not be able to extract the rom from the zip to verify the crc. If this is not the case, and your rom IS renamed, AND you have found the entry for it in the ini (and you are sure it is the correct rom), you've tried unzipping, and it is still not showing up, then i have no clue = ) I would advise you contain another version supported by the surreal.ini

If you have a rom that you have verified to be a good dump, and transfered it to your xbox, and refreshed your romlist, and it is *still* not showing up, then unzip the rom and transfer it, instead of the zip archive. The reason this might happen is because its using a non standard compression, and surreal 64 wouldnt be able to unzip it to see which rom it is.

Also, in regards to romplaying/stability/capability i have noticed that evox takes more memory somehow if launched from it (the dashboard, not the bios). I would imagine the reason is because evox patches the kernel, and also uses debug TSR tools. Try to not launch surreal64 from evox to minimalize any problems.

---ROM CONFIGURATION SECTION---

Most of the games should run fine with the default settings.

For audio you only have two choices, Azimer, which is the audio source from apollo used with jttl's SDL sound output, or PJ RSP, which is the basic audio plugin with LLE.

If a game is not playing (as in loads and freezes, or runs slow) you may be able to tweak the preformance by adjusting the memory settings.

The best way to go about this is to load the game, and turn on the debug display by right clicking on the analog stick and selecting it.

This will display how much memory is free. Start playing your game and keep in mind how much is free.

A example would be...super smash brothers. Ingame while your playing you have say.. 7.5MB free on average.

Quit the game and go back to the romlist and go into the settings.

The default setting should be 4MB video.

For 1964 dyna should be 8mb, and paging 4mb.
For PJ64 dyna should be 16mb, and paging 4mb

Now you will want to adjust your settings dependant upon which emulator you used.

Keep in mind that in order for the menu ingame to display correctly, you need atleast 4mb free. With 7.5 mb free on our example, that would give you 3.5 mb to play with, if you want the menu to show. If you dont give a damn about the menu, then i would suggest only going as low as 2mb free, which would give you 5.5Mb to play with.

The most noticable impact you will see is by increasing the dyna. Only in very few games (like super smash brothers and banjo tooie that comes to mind) need alot of video memory for textures. You'll notice some backgrounds missing in SSB if your video setting is too low.

So, by default, say in 1964 you have 8mb dyna. You have anywhere from 3.5-5.5 MB to play with. My suggestion would be to trial and error and see what does best for you. Try increasing the dyna by 4mb first, and see if that improves your preformance. If that doesnt work, increase it by 2, and increase the paging by 2. If that doesnt improve, drop the paging to 2mb and increase the dyna by 6mb.

Some games, like perfect dark, simply need more memory than a 64mb xbox can provide with the current core. It needs about 16mb dyna and 16mb paging in order to run smooth.

In some cases you can drop the paging to 1mb without a noticable difference. This may increase stuttering, or draw the FPS to nothing when trying to load a level/scene/texture that requires large memory.
----------------

Are you getting a BLACK SCREEN after loading a rom? Make 100% sure you are using Surreal v1.0 and NOT the gueux.net version. That version is for softmod exploits on newer xbox kernels.

Yes, .ZIP files are supported, aswell as all the known extentions for n64 rom's such as .usa and .v64

A specific rom not showing up on the list?

Please keep in mind this is not a bug or compatibility list. This is merely a help thread getting surreal *Started*. Please post to the appropriate thread if you wish to submit a bug within the emulator.

I will update this post with helpful information as i recieve it.

Let me repeat this one more time since some people apparently do not understand.

This thread is not about compatibility issues or bugs. This is a thread about getting surreal64 to launch.

Do not post bugs about games not working.

you talk about a prog called good windows...where can i find that?

Did you try hovering your mouse over the GOODN64 text? Its bold and underlined for a reason, it links *directly* to the site that has it.

hey,


so if i have a folder called "roms" on my E: i would just set the rom path to E:roms? and would i change the media path to "/E:/Emus/Surreal64/Media/" where i uploaded the program?

Rom Path=E:\Roms
Media Path=D:\Media

You dont need to change the media path.

hey,

thank you very much Iriez, i finally got it to work after hours of wasting time. thanks for the help!

the first time i load surreal the comments and the * above the emulator that works best are intact but after i load a rom, then exit the comments and * are gone. I have to go to the ms dash and delete the surreal save and reboot surreal in order for them to come back. am i doing something wrong or are other people having this problem too?

That problem does not happen to me. It sounds like you are editing the surreal.ini in the installation directory. You need to edit the surreal.ini in the TDATA folder as described in my first post.

Ok here is my problem all my rom names look really messed up (somtimes it is the game named backwards) when i load the list and then wheren i try to load the game it says it's loading 0% then quits.

What, basically, do the various memory types do? I figure from your post that "Max Video Memory" relates to texture issues... What about dynarec and paging? What are their functions?
Which memory type (if any) relates most to the speed at which a game is running. When I run Mario Kart 64, for instance, it's almost perfect. No noticeable texture problems, no sound issues, normal framerate... but it's simply not as fast as it should be. Not quite. A second (as displayed on my lap time) is longer than a second- if that makes sense. Framerate is fine, it's just the speed that's screwy. Is there a setting that relates to that?

ninja_friend, read Lantus' post here:

http://forums.xbox-scene.com/index.php?act...T&f=17&t=151724

might help answer a few questions you have.

Iriez, I've verified my super mario 64 using goodrom, and it appears in the surreal.ini, but still doesn't show...I might see about finding a different dump, but it should show right?

Does the .zip and the rom filename need to be something specific? I've tried renaming them to the goodrom name, no luck still, after rom refresh. My others show, and they're not all exact name matches to anything in particular.....

Thanks Joshua, that did clear it up a bit. Im still unsure of how to balance the two memory types out, although it appears that dyna mem should be added over paging mem. Paging mem just seems, I think, to be an indication of how often the rom needs to be retrieved from memory? Does that sound accurate? Whereas dyna mem is how quickly information is processed from the rom? Maybe?
I'll fool around with it, I guess. But this sheds some light.

*goes back to toying with a slow as hell Beetle Adventure Racing*

QUOTE

Originally posted by lantus dyna mem is for the 'Dynamic Recompiler' : the process of generating native n64 code from x86 instructions and executing it. Its much faster than normal interpreted code (emulation of each CPU instruction, registers, I/O etc). the dynarec is an important part of the emulator, and the more memory allocated the better because more code would be generated and executed on a smaller dynarec buffer, whereas in a larger one they are already available in memory to be executed. paging mem: because its impossible to fit an entire ROM into the Xbox memory space "paging mem" determines how much of the rom will be in memory at any time. i.e if we have 4 megs of paging mem and we load conkers (64mb). 4 meg of Conkers will be in Xbox memory , and the remaining 60 Mb will require to be loaded from disk. The disk portion is the "pagefile". The pagefile , however is the entire contents of the rom. So its 64mb and not 60mb. Why? because we dont know what portion of the rom will require to be loaded in next. hope this helps

The above quote by lantus in the thread linked by Joshua Wood leaves me with one question:

Would keeping larger roms unzipped, like Conkers, for example make the game run better? Or is the pagefile a seperate file temporarily created when the game loads?

Thanks for the great post, Iriez. Your first entry filled in all the gaps for me.

Just wanted to say that not all patcher programs work the same way; the dexbe patched perfectly when the other programs didn't. (Oh, sure, those programs would say they worked, but they didn't.)

Everything is going great for me now.

QUOTE (Joshua Wood @ Jan 7 2004, 10:23 PM)

Iriez, I've verified my super mario 64 using goodrom, and it appears in the surreal.ini, but still doesn't show...I might see about finding a different dump, but it should show right? Does the .zip and the rom filename need to be something specific? I've tried renaming them to the goodrom name, no luck still, after rom refresh. My others show, and they're not all exact name matches to anything in particular.....

Which rom is it?

mario 64 shows up fine for me.

The file name does not matter as the emulator checks the CRC of the rom.

QUOTE

Would keeping larger roms unzipped, like Conkers, for example make the game run better? Or is the pagefile a seperate file temporarily created when the game loads?

When surreal loads, it unzips and saves the rom to a temporary drive on the xbox. The rom is then accessed, sector by sector depending on what information needs to be loaded. So to answer your question, no, it would not change anything.

QUOTE

Im still unsure of how to balance the two memory types out, although it appears that dyna mem should be added over paging mem.

Depending on the game. Some games require a finer balance. Examples are SSB and banjo tooie.

Think of the recompiler as a machine. It takes computer code, and instructs the emulator how to handle the code from the N64 environment. The more memory this machine has, the more code and instructions it can fit. You can relate this to the capacity of a machine gun. The more bullets it can fit, the more bullets it can fire without being reloaded. If the recompiler has a small memory, it constantly needs to be reloaded (with code)causing the emulator to run slower.

If im incorrect on the matter, im sure lantus will point out the finer details = )

HELP!

Ok When I try to load Surreal it freezes on loading screen. I tried the above solution but still it won't load. I have a X2 lite with 4978.03 bios, 3921 evox dash and I followed the directions carefully and i set the ROM PATH in surreal ini. Any idea? Please help

Ok, updated to 4979 bios and the 3921 evox. Still no go. Surreal loads up just fine, its the roms that freeze at the title screen. Seems like all of them do it. Don't know what else to try. Tried all kinds of roms, verified them and everything, still no go.

tried everything .. cant get it to load ..

I got evolution x 3935 dashboard with a PC-BIOXX modchip ... Xecuter something bios (dont know the version and i cant get it upgraded)

I finally figured out why Surreal64 would run, but wouldnt let me move the cursor or click on anything.

I was using the controller plugged into the 2nd port. So the menu popped up and I can see the games, but pressing any of the buttons didnt do anything. When I tried the controller in the first port everything worked fine.

This may have affected others as it gives the impression that Surreal64 has crashed, when it hasnt.

I too was under the impression that it was not working, but I moved my USB controller to the first port and it worked fine.

QUOTE (SCVNGR23 @ Jan 8 2004, 03:41 AM)

tried everything .. cant get it to load .. I got evolution x 3935 dashboard with a PC-BIOXX modchip ... Xecuter something bios (dont know the version and i cant get it upgraded)

You tried PBL aswell?
You can verify which bios you are using in Evox or with Bios checker.

QUOTE

Ok, updated to 4979 bios and the 3921 evox. Still no go. Surreal loads up just fine, its the roms that freeze at the title screen. Seems like all of them do it. Don't know what else to try. Tried all kinds of roms, verified them and everything, still no go.

Can you give a example of which roms you were trying spcifically? Full verified filenames. Also have you verified all of the surreal64 files are present on your xbox? Does the rom actually write to the drive? (the percentage thing)

Goodnews Iriez

I upgraded my bios from 4978.03 to 4980 and it fixed the problem. Thanks for taking the time to reply to my post.

I still cannot get certain roms to show up on the rom list:

Banjo-Kazooie (U) [!]
Banjo-Tooie (U) [!]
Super Mario 64 (U) [!]
Wave Race 64 (E) [!]
Wave Race 64 (U) (V1.0) [!]

I have run all of the above through GoodN64, and they all run on PJ64 (apart from Banjo-Tooie, obviously), so they are definitely the right roms. They still refuse to show up on the menu. It's not a huge deal for me, as other versions of the same roms will show (Wave Race 64 (U) (V1.1), or Super Mario 64(E) [!], for example) - so I can still play what I want. It just seems a little strange to me.

I've got a bit of a very small problem. I upped all of my roms at one time and am in the process of testing them one by one. One of the roms displays a funky name...just jumbled letters and symbols. I tried to run it to see which game it was but it just causes surreal to reset except that it doesn't show the rom names. I have to hit refresh.

I tried to delete this problem rom but don't know which rom in the directory to delete. I never transferred any rom with this type of messed up name.

Do you have any clues on how I can figure out which rom is causing this problem so I can delete it? I'd hate to have to try going through the list one by one to find it.

Thanks

on a few games i have tried, banjo-tooie and zelda OOT, when i press in on the right thumbstick to bring up the surreal menu, the menu will not come up, instead it just slows the game down and will not go back to regular speed unless i restart the xbox. Does anyone know what would cause this? The roms are good too.

QUOTE (teyene @ Jan 8 2004, 11:20 AM)

I still cannot get certain roms to show up on the rom list: Banjo-Kazooie (U) [!] Banjo-Tooie (U) [!] Super Mario 64 (U) [!] Wave Race 64 (E) [!] Wave Race 64 (U) (V1.0) [!] I have run all of the above through GoodN64, and they all run on PJ64 (apart from Banjo-Tooie, obviously), so they are definitely the right roms. They still refuse to show up on the menu. It's not a huge deal for me, as other versions of the same roms will show (Wave Race 64 (U) (V1.1), or Super Mario 64(E) [!], for example) - so I can still play what I want. It just seems a little strange to me.

Im not sure about that one .. i have alot of those same roms and they display fine for me.

I suppose you'll have to use the counterpart version until we get it figured out.

bcb07: sounds like you are out of memory. Play with the paging/dyna settings.

fezzman: I cannot think of anyway to figure out which is the problem rom other than trial and error, sorry = /

GhostHavoc: Yes, 4978 (the one with the ftp) is known to cause some problems. I will add that to the list. Thanks for your input.

QUOTE (bcb07 @ Jan 8 2004, 06:39 PM)

on a few games i have tried, banjo-tooie and zelda OOT, when i press in on the right thumbstick to bring up the surreal menu, the menu will not come up, instead it just slows the game down and will not go back to regular speed unless i restart the xbox.  Does anyone know what would cause this?  The roms are good too.

a lot of times when im running zelda, there is usually less than 4 mb of free memory, so pressing the right thumbstick doesnt load up the menu, because thats how much the menu needs...but if you have like 2.5-3, it will load w/o the background screen.....i have found that if i run into a building or something it'll free up some ram for the right click menu hope this helps
also, if u have the debug screen on, and it ever gets near 1 or 0, (one time it froze on me) u will have to decrease ur dynarec/pagefile/video (dont do video) to free up enough if you really want the menu to work.....

Just wondered how the save states worked, could someone give me a quick explanation.

I played through the 50CC cup on Mario Kart, and then when I cam back to load after saving states after every race it seems that I have never played it, is there an auto save state, as in when you save in the game it saves on the harddrive, by the way I am using 1964.

Save games refuse to work for me...i can save and load until i exit the emu..when i go back in and load a state it locks up (but i still hear sound being played).

Apologies if this has been covered but i cant find it.

Im using cheapmod chip, latest evo-x, standard 64 meg xbox. All normal roms work..no errors on turok etc like some people.

Right thumb click on the analog stick and press save state 1.

Load save state 1 to load that position.

If loading it doesnt work, then its probably a memory issue that needs to be resolved. The loading states is buggy atm.

It was Super Mario 64 (U) [!] from memory (I"m at work at the mo). I've found alt copies of Super Mario 64 (U) [!] and Super Mario 64 (E) [!] so I'll see what happens with these...but if good64 says my one is ok, it should have the same CRC, so it should be listed....hm....wonder if there are some issues here?

I would just like to know if anyone has successfully been able to run Surreal on a nonflashable mod such as Xecuter1 or Enigmah? I have X1 and am unable to get Surreal to load from Evox, Avalaunch, nor XBMP. I tried patching with dexbe to retail. dexbe shows it as a verified retail xbe but it still freezes. Im at a loss.

Hello, I am running 4034 bios on evox 3753 (old I know, but it was what I started with and has worked fine so far, so no need to fix it yet), when I try to run it, it stays at the EvolutionX logo until I restart. I have an unmodded xbox using the font hack. If the problem is the old evox, then it is time to upgrade. Are there any suggestions that you might have? I know there were the suggestions for the other bioses, but since this wasn't listed, I figured I'd ask. Thank you very much for your time and for your work on the emulator.

Dont you need to patch your files to have them launch on a font exploited box?

To my understanding the only reason your evox is loading is because the font exploit allowed it to be loaded. At this point any other xbe that is loaded is loaded through the retail bios's rules and standards. This is why people use PBL in conjunction with the font hack.

If i am right and this is the case, then of course it wouldnt load. Its a unsigned xbe.

QUOTE

I would just like to know if anyone has successfully been able to run Surreal on a nonflashable mod such as Xecuter1 or Enigmah?

Yes, i have spoken to many people who have. All used either dexbe, craxtion, or xbe patcher.

well, I've been able to run my other applications fine (XBMP, SNES emu, backup games, etc.) having them re-signed, however, I believe this is the first time this has happened for me. I may have to find PBL and try that and see if it works. Thank you for the information.

im still having the same problem the first time i load surreal the comments and the * above the emulator that works best are intact but after i load a rom, then exit the comments and * are gone. I have to go to the ms dash and delete the surreal save and reboot surreal in order for them to come back. i even tried deleting everything to do with surreal including the game save, redownloading it and copying it to my hdd agian, same prob. does surreal write something to my hdd other than /E:/TDATA/a64fea57/surreal.ini that i should be deleting before a reinstall? im using Xecuter2.4979_REPACK bios. i know i asked this question before but not sure where else to go for help.

I love Surreal and was having tons of fun with it until i decided to mess around on the main menu. I clicked on the refresh button in the lower right hand side and all of a sudden all my roms disappeared! WHAT SHOULD I DO. thanks

I've had the same problem with verified zipped roms not showing up in surreal, but I resolved that by unzipping those roms and reuploading. perhaps it's due to zip files having imbedded comments or having more than one file in the zip that causes the problem. hope this helps somebody.

Fixed it.

I am having a problem loading my roms, I already patched the xbe to get the emulator. Now the emulator loads but when I go to select the roms they start loading. It goes from 0 to 100 percent and then the screen just stays black. I seen a couple posts about this, but no replies. Any suggestions would be appreciated.

QUOTE (aliens0098 @ Jan 8 2004, 05:55 PM)

I love Surreal and was having tons of fun with it until i decided to mess around on the main menu. I clicked on the refresh button in the lower right hand side and all of a sudden all my roms disappeared! WHAT SHOULD I DO. thanks

You should read this first post.

Edit the surreal ini to point to your rompath, and refresh.

QUOTE

well, I've been able to run my other applications fine (XBMP, SNES emu, backup games, etc.) having them re-signed

That was what i thought. I dont know about that process, so im unsure of whether it would work with surreal.

QUOTE

does surreal write something to my hdd other than /E:/TDATA/a64fea57/surreal.ini that i should be deleting before a reinstall?

No.

I honestly dont know what your issue is. Are you pressing the Y button before launching? That removes/adds the little star. I dont know whats happening, so im unsure of what advice i can give.

QUOTE (one2 @ Jan 8 2004, 06:05 PM)

I've had the same problem with verified zipped roms not showing up in surreal, but I resolved that by unzipping those roms and reuploading. perhaps it's due to zip files having imbedded comments or having more than one file in the zip that causes the problem. hope this helps somebody.

This would make sense.

If the file is zipped in a way that surreal cannot process, then it will not be able to extract the rom to verify the crc , and check against surreal.ini to see which rom it is.

I'll add that to the first post.

QUOTE (ftc2002 @ Jan 8 2004, 10:04 PM)

I am having a problem loading my roms, I already patched the xbe to get the emulator. Now the emulator loads but when I go to select the roms they start loading. It goes from 0 to 100 percent and then the screen just stays black. I seen a couple posts about this, but no replies. Any suggestions would be appreciated.

You said xbe. That doesnt sound plural = )

Did you patch the other xbe's the same way? All xbe's need to be patched.

Ok, I've just had a strange problem crop up. I have a verified Super Mario 64 [U][!]. It has worked flawlessly ever since I installed SurrealX. Tonight I load the rom up and Mario's head (on the title screen) is mostly white. I have tried deleting the folder in TDATA and UDATA, and I even deleted the "save game" from inside the MS dashboard. Then I unzipped the rom and put it back in my directory. It's still showing this weird mostly-white head. When I load a save game, the game itself looks fine, but I just can't figure out why Mario's head on that title screen is white now.

When I use 1964 his head is displaying fine. I even tried a rom from a different source. 1964 it's ok, and in ultra hle it looks white. It's just got me stumped because the other day it was fine.

Like I said, in-game appears to be okay so far. It's just his head at the beginning. Every other rom I've loaded has been fine as well. Even Goldeneye loaded in Ultra HLE. Is Mario playable/completeable in 1964 or pj-64?

QUOTE

Tonight I load the rom up and Mario's head (on the title screen) is mostly white

Mine has been that way from the beginning, I haven't tried tweaking the memory settings yet though...

Hmm. well thats really odd. Mine was displaying correct for a few days there. I guess as long as the in-game graphics don't get like that it's fine. Maybe I'll play around with the memory settings and see what I can find out.

I'm assuming the only settings that will pertain to Ultra HLE is the Max Video Memory setting, and Audio Plug-in.

QUOTE (Iriez @ Jan 9 2004, 05:29 AM)

QUOTE (ftc2002 @ Jan 8 2004, 10:04 PM) I am having a problem loading my roms, I already patched the xbe to get the emulator. Now the emulator loads but when I go to select the roms they start loading. It goes from 0 to 100 percent and then the screen just stays black. I seen a couple posts about this, but no replies. Any suggestions would be appreciated. You said xbe. That doesnt sound plural = ) Did you patch the other xbe's the same way? All xbe's need to be patched.

Thanx Iriez that did the trick, I can't wait to try the rest of my roms tomorrow.

QUOTE (Beelzebud @ Jan 8 2004, 11:45 PM)

Even Goldeneye loaded in Ultra HLE. Is Mario playable/completeable in 1964 or pj-64?

Of course golden eye loaded with ultrahle, thats the emulator your supposed to play with.

And i would play with 1964/pj64 for mario64 over UltraHLE anyday. I dont know why oDD selected it as the default. It should have been one of the others.

I have patched all my .xbe files and still I can't get it past the Xbox loading screen. It just keeps freezing

I'm not sure if this matters, but I am running Bios EVOX 2.2. And I can't reflash it because of my modchip. It is a homebrew chip and the only way to flash it I was told , is to take it out (out it has 32 wires) and flash it manually. And I have no idea how to do that.

So I hope I can still run this with my current Bios. I also have all the in game Reset switches set to OFF.

I Just want to get this working because all of you's are making me jelous with the games you are playing