Hacking 3ISO'S Studio

[spayrosam]

I have noticed, we can save more work in the "base boot.bin"
if "Base boot.bin"
00 00 00 00 00 00 .. from 32 to 74

Edit:
3 ISO'S Studio V5 plus
Line number 1322 and 1630

 

[nikeymikey]

Hi this may be a silly question but.......in the partion builder, where do i point the final box to? what is the source directory?

 

[boto12]

-

 

[mugotu]

@nikeymikey

in v3/4 you point it to the \ISO's Forwarders\game\make_iso\sound\ folder in 3isosstudio folder
(It's for making custom exchange sounds)

@boto12

You need to have a nand dump with the original wad installed into that nand dump, after that you can have the iso and forwarder dol on sd OR USB. Check this link for setting up a working triiforce.

Before you can use ISO forwarders, you must have a working triiforce setup.

 

[mugotu]

I'm annoyed with some wads not having the manual in the "normal" places so I'm making a list of all wad types and the location/compression type of the manual for that type. I will keep updating this until I have it completed as it will take alot of testing with my coding.
(BTW newest rev tells whether a wad is neogeo, arcade, or arcade namco even though all 3 title IDs start with an "E")
Also added a script to sort wads into folders by console type for debugging, later this can be called to sort all of your processed wads =P. Added Q,E6,E7,EA console identifiers.

PAL and NTSC wads may use different compression and placement of manuals so I'll have 2 lists until I can prove pal/ntsc file placement/compression is uniform.

-----------NTSC-----------
C=Commodore16
(Tested on 4 NTSC Wads, all returned manual)
*05.app\html\USA.ARC (u8it)

E6=Arcade
(Tested on 1 NTSC wad, returned manual)
*05.app\LZ77_html.arc (wwcxtool, u8it)

E7=Arcade(Namco)
(Testing with 3 NTSC wads)
*03.app\html\LZ77_HTML.arc (wwcxtool, u8it)

EA=NeoGeo
(Tested on 18 NTSC wads, all returned manual)
*05.app\html.arc (u8it)

F=NES
(Tested on 81 NTSC wads, all returned a manual)
*05.app\enamual.arc (u8it)
*05.app\lzh8_emanual.arc (lzh8_dec, u8it)
*05.app\lz77_emanual.arc (wwcxtool, u8it)

J=SNES
(Tested on 40 NTSC wads, all returned a manual)
*05.app\enamual.arc (u8it)
*05.app\lzh8emanual.arc (lzh8_dec, u8it)
*05.app\lz77emanual.arc (wwcxtool, u8it)
NOTE: all compressed were JCxE except one which wad JBUE

L=Sega Master System
(Tested 8 NTSC wads, all manuals faound)
*05.app\data.ccf (ccfex, u8it)

M=Sega Mega Drive
(Tested on 59 NTSC wads, all returned manual)
*05.app\data.ccf (ccfex, u8it)

N=N64
(Tested on 15 NTSC wads, all returned manual)
*05.app\html.arc (u8it)
*05.app\htmlc.arc (unknown compression atm)

P=TurboGrafx16
(Tested on 48 NTSC wads, all returned manual)
*05.app\html.arc (u8it)
*05.app\LZ77_html.arc (wwcxtool, u8it)

Q=TurboGrafxCD
(Tested on 9 NTSC wads, all returned manual)
*05.app\html.arc (u8it)

W=WiiWare
(Tested on 75 NTSC wads)
normal manuals not found in wiiware wads.
researching alternative options.

-----------PAL-----------
C=Commodore16
E6=Arcade
E7=Arcade(Namco)
EA=NeoGeo
F=NES
J=SNES
L=Sega Master System
M=Sega Mega Drive
N=N64
P=TurboGrafx16
Q=TurboGrafxCD
W=WiiWare

 

[spayrosam]

decode Huf8 puff8_00.zip

I am working on the covers "data.bin"
also create covers

EDIT:
I am looking for "TurboGrafxCD-logo" (TurboGrafxCD template)
google has no results

@mugotu
Until now none has succeeded. (extract everything in wad file )
We have done a good work

 

[mugotu]

I just want to focus on perfecting the extraction process before we move on to adding the actual making of the covers.

This is going to be amazing when we are done xDD

http://images.swaptree.com/images/vg/51/1996851.jpg

Also Known as "Super CD Rom2 System"
http://www.hardcoregaming101.net/lordsofthunder/lot-duo.jpg

try to figure out the "htmlc.arc" compression, no time right now to open a hex editor.

 

[spayrosam]

I found a good site http://hcs64.com/vgm_ripping.html

 

[pepxl]

you guys are really getting into the flow aren't you lol, got to say your app looks great and cant wait for V5

BTW what source you using for homebrew forwarding? most sources still have trouble and DSI on booting or exiting if forwarding to GenplusGX, SmsplusGX, Wii64 and several others yet work perfectly if the app is booted from HBC

 

[mugotu]

the dols we are using as a base right now are based on craptriiforce, not sure which nandloader tho, since spayro made all that in the last version. when we come to that brige I will test intensively.

best thing I think to do for homebrew apps which don't work very well at the moment is to first install a forwarder channel to the nand dump.. then use the ISO-forwarder to forward to the forwarder channel. (I know it sounds complicated\unefficient, and is the long way around but it shouldnt codedump on you then).

OFC this is just until I get around to modifying the way hombrew is loaded, hopefully I can just put the dol of the homebrew itself into the ISO and not need to forward it at all. Should increase loading speed ALOT. And if I can do that with the triiforwarder dols, then no more triiforwarders folder also xD.

 

[mugotu]

Ok, some research into the WW files and none of them I've tested contain a proper manual, when you load it and go to home>operations guide it only has a simple button map and a button to look at the REAL manual on the wii shop channel. I think maybe the manuals can be found online and downloaded =P. If not we need to pick an option.

1. NOT make covers for wiiware (there is a pack out that has all covers done, with "?" on the back.
2. Use fanart for the back.
3. Download cover_back content from the web from the program directly.

 

[fullstrength]

the dols we are using as a base right now are based on craptriiforce, not sure which nandloader tho, since spayro made all that in the last version. when we come to that brige I will test intensively.

best thing I think to do for homebrew apps which don't work very well at the moment is to first install a forwarder channel to the nand dump.. then use the ISO-forwarder to forward to the forwarder channel. (I know it sounds complicated\unefficient, and is the long way around but it shouldnt codedump on you then).

OFC this is just until I get around to modifying the way hombrew is loaded, hopefully I can just put the dol of the homebrew itself into the ISO and not need to forward it at all. Should increase loading speed ALOT. And if I can do that with the triiforwarder dols, then no more triiforwarders folder also xD.

Now that's what I'm talking about....you accomplish that and your the shiznit!

 

[pepxl]

the dols we are using as a base right now are based on craptriiforce, not sure which nandloader tho, since spayro made all that in the last version. when we come to that brige I will test intensively.

best thing I think to do for homebrew apps which don't work very well at the moment is to first install a forwarder channel to the nand dump.. then use the ISO-forwarder to forward to the forwarder channel. (I know it sounds complicated\unefficient, and is the long way around but it shouldnt codedump on you then).

OFC this is just until I get around to modifying the way hombrew is loaded, hopefully I can just put the dol of the homebrew itself into the ISO and not need to forward it at all. Should increase loading speed ALOT. And if I can do that with the triiforwarder dols, then no more triiforwarders folder also xD.

with this method you have to remember that some homebrew use external files that are set to be loaded from a given location on the SD/USB so would not work unless the extra files are on the SD/USB e.g MPlayer CE, and if not their will error but this should be fine of single file apps

 

[spayrosam]

"Homebrew Forwarders"

that will come

or compile your app with

LDFLAGS = -g $(MACHDEP) -Wl,-Map,$(notdir $@).map -Wl,--section-start,.init=0x8003f000

 

[pepxl]

"Homebrew Forwarders"

that will come

or compile your app with

LDFLAGS = -g $(MACHDEP) -Wl,-Map,$(notdir $@).map -Wl,--section-start,.init=0x8003f000

the apps not the problem really its the forwarder source that boots the app, it would means recompiling apps with modifed entry points to go with forwarders and not the other way round, not everyone would be willing to compile an app just to use a forwarder they like but hopefully i can find the source again that boots the problematic apps without the need to change entry points

 

[mugotu]

well ofc the extra files that are required for homebrew to run will have to be on sd/usb always.... I was just saying maybe a way for it to work for you for now xD. As far as forwarder sources go its not a problem to patch in things from DOS to a dol. There are plenty of apps that work from command line for that and we can implement later if we need to.

The second thing I was talking about was just replacing the main.dol of the ISO with the boot.dol for a homebrew app and sign it so that we wont need nand emu anymore. But thats WAY down the road.

Anyways, new source is up on googlecode, all images extract properly from the manuals, except WW(only returns banner images, no manual in these) and the newer N64 wads that have "htmlc.arc" for the manual. Need to examine htmlc.arc files in hex to determine compression type. After that one is done hopefully the app is 100% compatible as far as making covers go.

I'll be putting part2.txt up soon with the code that Spayro pm'd me. Hopefully Tristar can share his source or work with me to make it compatible with v5, thats half the work to making and ISO automated. Just need a way to do that with wiiscrubber or some alternative app and is noob proof!

EDIT: v5 is coming along nicely with 100% x64 OS support.

 

[mugotu]

if anyone can find a way to decompress this it would help alot xD thx.

 

[spayrosam]

F**k "htlmc.arc" (skipping this shit)
I am looking for the manual link into wiiware wads..
http://www.nintendo.com/games/guide

 

[mugotu]

its a hashed url. gotta decrypt the hash first I think, unless they let us search xD

 

[mugotu]

v5 status: makes beautiful covers finally, updates dols pending data2.bin, tomorrow will make function to create the ISOs (option to NOT create ISOs even though it is automated). After that we move on to homebrew.


I'm holding off on releasing an ISO/Cover maker for homebrew until I can code something that will utilize wiitdb.xml in 3isos. The old way of entering your own custom ID for homebrew is not efficient enough because I don't want people making 50 HB isos/coversets and uploading them to wiitdb only for the next guy to do it again on the same apps and use different IDs. Imagine after 100 ppl do that, wiitdb would be in defcon5...SO...

After having a long chat with lustar I think all homebrew covers and ISOs will follow an ID mapped within Either "D..A" or "D..H" . We are checking up on whether or not ninty will ever release Demo channels for DL from the ninty channel, and it is figured that they will not then it will be "D..A"
(Demo DISCs carry the "D" in the consoleID slot of DISC titles, we are unsure of the possibility of Demo CHANNELS)

like DWFA or DWFH would be wiiflow, depending on which convention is selected.
D is for Dol and H is for Homebrew (since homebrew really isnt localized) and A is ninty-talk for Any-Region.

THEN, if a HB app is not on wiitdb it will only allow creating ID's that start with a certain banned character and have also a region code which is banned from wiitdb.

So the only option is to either add it to wiitdb FIRST or NOT share your covers/ISOs. The app will autoDL wiitdb.xml.

I know this makes this the cover making 1/2 of this program semi obselete in a few months but its for the better good of our covers xD.