Hacking 3ISO'S Studio

[mugotu]

@spayrosam (didnt realise i was spelling your name for so long...sorry dislexia)

FOR /f "delims=" %%i IN ('DIR /s /b /a-d "wads\*.wad"') DO CALL :RenameFile "%%i" 
GOTO :eof 
:renameFile 
FOR /f "tokens=1,2* delims=&" %%a IN ("%~nx1") DO (SET "PART1=%%a" & SET "PART2=%%b") 
IF "%PART1:~-1%"==" " SET "PART1=%PART1:~,-1%" 
REN %1 "%PART1%%PART2%" 
GOTO :eof

Ill add this tonight. first I'll check for bad archive names too.. then for wads this changes too:

FOR /f "delims=" %%i IN ('DIR /s /b /a-d "wads\*^&*.wad"') DO CALL :RenameFile "%%i"
FOR /f "delims=" %%i IN ('DIR /s /b /a-d "wads\*-*.wad"') DO CALL :RenameFile2 "%%i"
GOTO:eof

:renameFile 
FOR /f "tokens=1,2* delims=&" %%a IN ("%~nx1") DO (SET "PART1=%%a" & SET "PART2=%%b") 
IF "%PART1:~-1%"==" " SET "PART1=%PART1:~,-1%" 
REN %1 "%PART1%%PART2%" 

:renameFile2 
FOR /f "tokens=1,2* delims=-" %%a IN ("%~nx1") DO (SET "PART1=%%a" & SET "PART2=%%b") 
IF "%PART1:~-1%"==" " SET "PART1=%PART1:~,-1%" 
REN %1 "%PART1%%PART2%"

 

[spayrosam]

Rar archiv have bad archive names "-"
line command Rar rar e -y --@
but it does not work "--"

btw
spayro is my nickname
sam is my name

 

[mugotu]

we will rename archives also xD.

 

[spayrosam]

Create ISO'S and Covers from a nand dump.
a beginning could look like this

Code deleted

EDIT:
@mugotu Iwill PM you!

 

[mugotu]

This changes alot x.X. By the app first making a nand and pulling the covers from there it is a more complete program though. It will take alot of going back in and rewriting to add that but I'll do it xD.

Concept:
Put *.wad,*.zip,*.rar,*.7z into wads folder.
Set option to create Emulated nand.
Set Language.
Set Region.
Program makes you a nand for use with triiforce, covers, forwarder ISOs
Put all on your wii and play.


Also, The old triiforwarders I have on my wii only work in Wiiflow-IOS222, is that supposed to be that way?

I'd like to try and make 2 base ISO's one for IOS222 one for IOS249. Then we just need to inject title ID and Title Name to the ISO for it to be a full forwarder. That should work right? Then to update ISO's you just put the new base ISO in 3apps and your ISO's in the wads folder? I want to get away from using triiforwarders/*dol if we can.

(most of the ISOS HERE dont work well for me, and if they work at all they still have the old green flash on the screen.)

 

[spayrosam]

waive Triiforwarders/*dol means
Find, extract and delete ISO'S from WBFS/FAT32
Update ISO'S
then again use WBFS manager
There is much work to update ISO's

With Triiforwarders/*dol only exchange folder (after update *dol)

(most of the ISOS HERE dont work well for me, and if they work at all they still have the old green flash on the screen.)

I used gx-source for the forwarder ISO's HERE
3 ISO'S Studio has his own source..
Created ISO'S using 3 ISOs Studio work

 

[spayrosam]

I'll send you "Triiforwarders and Homebrew main.dol sources"
Please, "The sources main.dol" are not OpenSource
Thanks

 

[mugotu]

ok then. Thats why those forwarders dont work for me from that page. (I dont even have GX installed anymore xD). I'm going to start a thread soon with DL's for new ISO's with the CORRECT ID's that will be used on wiitdb.

They must be in D..A format to be allowed on WiiTDB (D= Dol, A=Any Region)

First ones will be:
Homebrew Channel = DBCA00 (will forward to the Channel Title JODI and ball back on HAXX)
FCEU-GX Ultra = DFUA00
Snes9xGX = DS9X00
VbaGX = DVBA00
Triiforce = DTFA00
Triiforce_MRC = DTCA00


Loaders (For switching loaders)
Wiiflow = DWFA00
CfgUSBLoader = DCLA00
USBLoaderGX DGXA00
Uloader = DULA00


Let me know what you think.

 

[guitarloser85]

Dig the progress

Posted a request on the googlecode page.

 

[mugotu]

mostly done already xD, just need to propogate the changes throughout the code. The "options" are already written to a configurations file from the program.

I have alot of work to do n this I've been slacking since I had to reformat my computer and decided to rearrange all my drives and IOS on the wii too xD. Should be picking up alot within the next few days...expect changes.


@Spayrosam
I'm considering changing the "wads" folder to "Input"....

That way the program folder of a homebrew app can be thrown in there, some wads, dols, elfs, zips, rars, .7z files. And the program will do with them as it should based on the user options.

Then in the "Output" folder, it can be made so that everything inside that folder is designed to be copied directly to your wii drive.

Output\
---Apps\(processed homebrew copied here)
---Title\
---Ticket\
---Triiforwarders\
---Triiforce_mrc\
---Covers\User Set Covers Directories\
---The ISO



I'm also changing the way we planned extracting wads from archives slightly. Instead of extracting the whole archive, it will generate a list of wads in the archive to a temp file, and then only extract one at a time for processing. (Saves me 46gb of HD space)...

Since we decided to make the output in nand format there is going to be alot of changes needed in the code. Has anyone reported anywhere that wad2nand does not work for any wads? If we switch to ONLY that method we lose the manual I think.

 

[spayrosam]

"Input\ and Output\"
I like it

do not forget "Exchange opening.bnr (Sound folder)

The ISO'S are ~33MB, we can trim it to ~2MB

code deleted

 

[mugotu]

Ill add option to convert it to .wbfs files or keep it as ISO.

 

[spayrosam]

OK !
This process is to trim the ISO'S
~32,4 MB to ~4MB WBFS format (convert ISO to WBFS)
~4MB to ~2MB ISO format (convert again WBFS to ISO)

"Add option to convert it to .wbfs files or keep it as ISO" is a good idea
The user should decide..

 

[mugotu]

Changed Homebrew base files to region A, no more green flash on NTSC, I need it tested on PAL and other NTSC.
WiiXplorer Forwarder-ISO
Looks for wiixplorer in:
SD:\apps\WiiXplorer\boot.dol
SD:\WiiXplorer\boot.dol
USB:\apps\WiiXplorer\boot.dol
USB:\WiiXplorer\boot.dol
Try it and tell me.

(The corrupted draw is cause when the wii tries to force pal output, but has not the capability. A defaults to console region.)


ALSO, wad2nand either needs updated, or we use our own routine to create the nand. It doesnt get all of the files form a wad. (probably why some VC/WW doesnt run when you use that)

 

[spayrosam]

I will make some test..
The ISO's had the Region L, i will change it to PAL or NTSC-U..

EDIT:
Not only the ID: changes the ISO Region. (there are other file to edit)
I think the ID: "D**A" makes problems.

fact is
"PAL ISO" + "PAL WII" Results No Flash
"NTSC-U ISO" + "PAL WII" Results Flash
"NTSC-U ISO" + "NTSC WII" Results No Flash
"PAL ISO" + "NTSC-U WII" Results Flash

Here 2 ISO'S
WiiXplorer-DWXE-NTSC-U
WiiXplorer-DWXP-PAL
Looks for wiixplorer in:
SD:\apps\WiiXplorer\boot.dol
SD:\WiiXplorer\boot.dol
USB:\apps\WiiXplorer\boot.dol
USB:\WiiXplorer\boot.dol

Test it then you may see what I mean!

(Open The ISO'S with "WIIScrubber" you 'll see ISO's Region)

Btw
IF alle Homebrew ID: "D**A ", which covers would create "3 ISO'S Studio" (PAL or NTSC)(and WITDB have PAL or NTSC covers)

 

[Tristar]

Btw
IF alle Homebrew ID: "D**A ", which covers would create "3 ISO'S Studio" (PAL or NTSC)(and WITDB have PAL or NTSC covers)

Couldn't you make your covers 'All Regions' if the ID is D**A** and region specific in all other cases?

 

[mugotu]

Region code "A" is the official ninty region code for AnyRegion, so the wii SHOULD handle it correctly. The only thing we need to do after that is to pre-set it to use console-default video mode. D..A kind of has its own section in wiitdb. The covers should also be made w/o a region identifier in homebrew case, even though they are stored in the PAL folder on wiitdb mostly so that covers of different languages can be uploaded.


@Tristar, thats the idea. Homebrew simply doesnt have a region.

 

[dwmyke]

Uhh, just tried to download this from here http://code.google.com/p/3isosstudio/downloads/list and AVG came up and said it is infected with a trojan horse..

 

[mugotu]

yeah, avast has been doing that to me too, some idiot got it added to their list of "hacking tools". (wonder if it ninty? o.0)....

Anyway its not a virus, It just uses some tools they consider to be mostly used by hackers because they modify hex automatically and it has an embedded batch file. These are sometimes characteristics of some harmful executables, and they may have flagged it based on heuristics because of that.

 

[tmdaonline]

It's more than just Avast & AVG ... check it out;

http://www.virustotal.com/analisis/aa815e2...b8a8-1271015246

Result: 14/39 (35.90%)