GCOS problem :-(

[festwa]

Hi,
when i try to boot GCOS using AR/Memory card method I have to boot AR twice before GCOS loads...

I have to insert AR, powerup Gamecube, load AR, select start game, open lid, close lid, load AR, select start game, open lid, close lid, GCOS loads

Is this normal?

Once I finally get GCOS loaded when I try to boot a backup i manage to do the swap, but the listing of the game details (name region etc) stay blank, and no matter which region i select/force all i get is a black screen :(
I have tried Ritek g05 full sized DVD-R, Hyundi 8cm DVD-R, Datawrite 8cm DVD, bulkpaq 8cm DVD along with several diffrent boot games (Mario Kart: DD, PSO, AR, Metroid Prime, Mario Sunshine, Paper Mario)

The other parts of GCOS i've tried work without any issues at all (once its booted)

Has anyone got any idea to what is going on? Is it me or is my setup just incompatable?

Festwa

(I am yet to tweak the laser as I would prefer not to unless I really have to)

Forgot to mention I am using a PAL DOL-001 GC (drive04 I think), with an AR V1.06)

[Mookdog]

Did you enter the NEW master code for AR ?? Here is a url explaining it all


http://www.ngcdev.com/snakecompat/index.php


Hope that helps you with your issue


Mookdog

[festwa]

Thanks for the reply, I didn't get chance to try it out last night as the girlfriend wouldn't let me near the 'cube, but I am planning on trying it tonight and i'll let you know what happens.

[dixgray]

Hey,

Booting AR twice is normal for Samson's AR bootloader. The master code everyone on this board is talking about is a HACKED code that is not a proper alteration of the AR bootloader program. Parasyte discussed this at length on the dextrose forums, and a bunch of idiots over here are just spreading it around like it's the greatest thing ever.

Do NOT use the so called "new" master code unless you want to take risks with your games and game data.

I've been having trouble with GCOS 1.4 on my drive dol-001 drive 04 version, the only media I got to boot was TDK full-size 8x, but I have some Ritek G04 minis on the way to try. I've gotten Resident Evil 4 to boot and run for hours without any problem by using both the original disk as a boot disk and the AR as a boot disk. The problem is that it booted fine the first few times and now it doesn't seem to boot and run at all. At this point I'm chalking it up to media/laser compatibility. We'll see how the Ritek G04 minis do.

[djgarf]

but until proper codes are found for every action replay version then people dont have much choice but to use the hacked codes

[festwa]

I thought AR version 1.06 had a known code that wasn't the universal code?
I've followed the guide Mookdog posted a link to and now GCOS boots first time, but I'm still not having any luck booting a back up, still getting the black screen after I swap a disc.

I've justy tried Moltons custom build but still the same booting problem...

[molton]

I think the only way my build would solve your problems would be if you're too retarded to know which region to select :D

I just don't want people wasting their time testing my build and the original GCOS because it fixes absolutely nothing, work with the original GCOS if you're just trying to get GCOS to work.

[Mookdog]

Well black screen on backup means either one of many things. Media Issue or perhaps you need to use FSTFIX on it or perhaps a pot tweak



Mookdog

[festwa]

thanks for the tips guys, but so far no luck. I've now tweaked my laser (was about 400 Ohms, tweaked to about 180Ohm). but i keep getting the same black screen problem :(

I have now tried several diffrent images burned to diffrent makes od DVD-R but still the same problem...

I have been using a Sony DWU-18A drive to burn with (a rebadged Lite-on)... could this be the problem?

[festwa]

Thought I should just give a quick update...
After almost 3 weeks of playing with diffrent laser settings, and media I have finally managed to boot into a game (zelda 4 swords & Starfox Assult) and played for a few hours without a DRE.

Thanks for the help guys :-D

[nukleuzdj]

Originally posted by dixgray
Hey,

Booting AR twice is normal for Samson's AR bootloader. The master code everyone on this board is talking about is a HACKED code that is not a proper alteration of the AR bootloader program. Parasyte discussed this at length on the dextrose forums, and a bunch of idiots over here are just spreading it around like it's the greatest thing ever.

Do NOT use the so called "new" master code unless you want to take risks with your games and game data.



what "risks" does using the code open?
what is so bad about using a code that works for the bootloader.
i dont get what, if anything it could possibily do.


also @ the original poster, opening and closing the lid too fast, after selecting the AR from the memory card sometimes causes a reset for me.

[dixgray]

Um, it's my understanding people have gotten weird glitches, and it could potentially damage save data. Basically with the hacked mastercode, the ar is running ar codes as assembly code, which is just garbage basically. Parasyte gave a more complete explanation on the dextrose forums.

[Z80]

Parasyte's explanation just stays on the side of caution. But the fact is, yes, the FACT is, using the "hacked code" with many AR versions atleast, forinstance my 1.06, there are no "side effects" or "glitches". It executes the code that I put on it and after that there are no ills that could come from the hacked code as all it does it load my GCOS.

People that say otherwise are just paranoid or unknowing. I've had zero problems with the hacked single open/close master code. So has everyone else that I've talked to.

[dixgray]

Originally posted by Z80
Parasyte's explanation just stays on the side of caution. But the fact is, yes, the FACT is, using the "hacked code" with many AR versions atleast, forinstance my 1.06, there are no "side effects" or "glitches". It executes the code that I put on it and after that there are no ills that could come from the hacked code as all it does it load my GCOS.

People that say otherwise are just paranoid or unknowing. I've had zero problems with the hacked single open/close master code. So has everyone else that I've talked to.

I wouldn't describe people who think "EXECUTING GARBAGE CODE is a bad idea" as paranoid or unknowing. Your anecdotal "evidence" is meaningless when we know exactly what is really going on.

[dixgray]

Actually what we really need is someone to modify Sasmon's bootloader code to be compatible with this master code, suprisingly no one has done it yet, and it's probably because everyone thinks this solution is acceptable. Until that happens though, it's double open/close for me.

[tempest]

Originally posted by Z80
Parasyte's explanation just stays on the side of caution. But the fact is, yes, the FACT is, using the "hacked code" with many AR versions atleast, forinstance my 1.06, there are no "side effects" or "glitches". It executes the code that I put on it and after that there are no ills that could come from the hacked code as all it does it load my GCOS.

People that say otherwise are just paranoid or unknowing. I've had zero problems with the hacked single open/close master code. So has everyone else that I've talked to.
um
I may be remembering wrong but...
I believe there are 2 sets of codes the original (Samson's default) made exclusivly for AR 1.06 and the "hacked" works for all AR versions. You should not have any issues with 1.06 and the original codes, unless you are using the hack codes (which makes no sense)?

for me the hack work great with AR 1.07. If I understand correctly the risk I am taking by using the hacks is with the data on my mem cards. Personally I can live with that (my 4 yr old may have issues though;) )

[festwa]

Originally posted by dixgray
Actually what we really need is someone to modify Sasmon's bootloader code to be compatible with this master code, suprisingly no one has done it yet, and it's probably because everyone thinks this solution is acceptable. Until that happens though, it's double open/close for me.

I did have this issue but found that re-formatting the card and installing everything from scratch solved the issue and now i only have one open/close to boot GCOS...

could be worth trying if you haven't already?