ROM Hack RELEASE EmuTool - Move partition Emu on another SD, Switch Emu type on SXOS and more

  • Thread starter Thread starter TheyKilledKenny
  • Start date Start date
  • Views Views 256,075
  • Replies Replies 473
  • Likes Likes 57
Last edited by impeeza,
Do the files need to be named a certain way under SXOS File and Hekate Backup Files? I backedup my SXOS Sysnand on my PC, then resized it and renamed it... I am trying to convert it to either an Atmosphere File or Atmosphere Hidden Partition, but it is not going very smoothly lol.
 
Do the files need to be named a certain way under SXOS File and Hekate Backup Files? I backedup my SXOS Sysnand on my PC, then resized it and renamed it... I am trying to convert it to either an Atmosphere File or Atmosphere Hidden Partition, but it is not going very smoothly lol.
Emutool doesn’t handle shrinked emunands…
 
  • Like
Reactions: impeeza
ha ha ha, sorry use the attached one this uses the code released on the Second post on this thread, change one line which is causing the overflow and recompiled using VB6, try it and let us know.
OH:wtf:
I really need to find the time to end this work.

Who did this changes?
You can add it to github as pull request and I can accept and recompile the executable.

Let me know.

Ciao.
 
OH:wtf:
I really need to find the time to end this work.

Who did this changes?
You can add it to github as pull request and I can accept and recompile the executable.

Let me know.

Ciao.
Hi. I did sort of quick and dirty compilation. Let me review what I did and go to github. Thanks for your work
 
Hi, I just find the source a did customize.

What I did was:

On the 224 line of clsDrive.cls I did comment:
JavaScript:
'       drvTotalSectors = oInit.TotalSectors

because on my 4TB HardDrive the TotalSectors property is a number bigger than a "Long", and running the program generate a overflow on that line. but for some unknow reason for me, changing the line 46 from:

JavaScript:
Public drvTotalSectors  As Long     '= 384499710

To:


JavaScript:
Public drvTotalSectors  As Double     '= 384499710

give me a error but I think is related to my installation.

By the way, I have to comment the next lines because I never found the "CINIFILE.CLS" class file

Remove EmuTool.vbp, line 8
JavaScript:
Class=cInifile; ..\..\HiBusConfig_Sviluppo\src\CINIFILE.CLS

clsDrive.cls, comment lines 224 & 325 to 346:

JavaScript:
'Dim cini        As cInifile

...


        'Set cini = New cInifile
        'With cini
        '    .Path = drvName & "\emummc\emummc.ini"
        '    .Section = "emummc"
       '
       '     .Key = "sector"
       '     .Default = -1
       '
       '     'Questo "appoggia" il valore a destra, perchè la virgola è fittizia nei currency
       '     drvStartSector = CCur(Replace(.Value, "0x", "&h")) / 10000@
       '
       '
       '     .Key = "path"
       '     .Default = "\emummc"
       '     drvEmuFolder = Replace(.Value, "/", "\")
       '
       '     .Key = "nintendo_path"
       '     .Default = "emuMMC/HPE0/Nintendo"
       '     drvNinFolder = Replace(.Value, "/", "\")
       '
       ' End With
        'Set cini = Nothing

frmMain.frm, line 807:

JavaScript:
'Dim cini                As cInifile       'Classe di gestione dei file INI

If you could give me a link to that class fill I will thank you so much.
 
  • Like
Reactions: TheyKilledKenny
Ok, sorry fot all the mess I created, the long history is:

I have the source on the OP of this thread that is the code o referenced on last post.

Later you share another source which have the CINIFILE.CLS & HugeBinaryFile.cls and few extra lines on clsDrive.cls but have the same overflow on big drives. for that sources I did comment the line "drvTotalSectors = oInit.TotalSectors" on clsDrive.cls and compile it. that is the one I shared.

So I just realize you create the GitHub repository, and make corrections to code, now the released one on GitHub works fine when you have big hard drives.

The one on GitHub works great, the only thing I find is what the file CINIFILE.CLS have the end of lines as LF not CRLF so it is not open by Visual Studio 6.0:
1643304081535.png


I Think the version on GitHub should be raised to avoid conflicts.

Thanks for your great work
 
Ok, sorry fot all the mess I created, the long history is:

I have the source on the OP of this thread that is the code o referenced on last post.

Later you share another source which have the CINIFILE.CLS & HugeBinaryFile.cls and few extra lines on clsDrive.cls but have the same overflow on big drives. for that sources I did comment the line "drvTotalSectors = oInit.TotalSectors" on clsDrive.cls and compile it. that is the one I shared.

So I just realize you create the GitHub repository, and make corrections to code, now the released one on GitHub works fine when you have big hard drives.

The one on GitHub works great, the only thing I find is what the file CINIFILE.CLS have the end of lines as LF not CRLF so it is not open by Visual Studio 6.0:
View attachment 295523

I Think the version on GitHub should be raised to avoid conflicts.

Thanks for your great work
Here is a Zip with the 2 cls files.
Tell me if they're ok for you so I can upload them, on github.
CIniFile.cls was coded by Steve McMahon in Feb 1997 :D

If you remove cinifile Emutool will not be able to create the emummc.ini file.

Ciao.
 

Attachments

  • Like
Reactions: impeeza
Here is a Zip with the 2 cls files.
Tell me if they're ok for you so I can upload them, on github.
CIniFile.cls was coded by Steve McMahon in Feb 1997 :D

If you remove cinifile Emutool will not be able to create the emummc.ini file.

Ciao.
Hello, Thanks a lot for your help, sorry the late response yes the files on the zip are correct, the allow me to compile using Visual Basic 6.0, thanks a lot.

I recommend you to upgrade the GitHub version to something like 2.9.1 to avoid confusions with the old uncorrected versions.

Again thanks a lot for all your help. "Ciao" from Colombia
 
What you are describing is the same configuration I am currently using. I moved an sx files emunand to a new sd on hidden partitions and I can start it with both sx and fusee-primary.
My emunand is still on fw 9.20.

If the emunand works with sxos, then the copy is ok and the problem isn't the backup/restore process.

I'm very sorry, but it's really difficult for me to try to guess what's wrong with your installation. A lot of small or big things that can be wrong in loading the emunand.
I can assure you (and everybody) that Emutool does nothing within the emunand, it is a simple binary copy tool (a copy machine)
There are no keys so Emutool is unable to decrypt Emunand (and there is no code inside that attempts to do so), therefore no operations can be performed inside the Emu

Check if you have themes or HBs that are not compatible with Atmosphere, remove any game cards from the cartdrige reader.
Recheck the Atmosphere files, specially sept and atmosphere folders, the sigpatches and try again.

I'm sorry for not giving you a definitive solution.

Ciao!
I'm trying to use XSOS and atmosphere in the same time, I have a problem how to find emutendo folder and move it on emummc
 
I used emutool to make a backup of my atmosphere hidden partition to Atmosphere SD File on my PC.

My current switch sdcard is partitioned. I want to use a bigger sdcard but this time, I do not want a partitioned card but instead i want a cfw on SD File (for easier backup of emunand [by copy pasting] in between fw updates)

Now, how do I restore the backup to the new sdcard as Atmospher (sd) file instead of Atmosphere Hidden Partition?
 
I used emutool to make a backup of my atmosphere hidden partition to Atmosphere SD File on my PC.

My current switch sdcard is partitioned. I want to use a bigger sdcard but this time, I do not want a partitioned card but instead i want a cfw on SD File (for easier backup of emunand [by copy pasting] in between fw updates)

Now, how do I restore the backup to the new sdcard as Atmospher (sd) file instead of Atmosphere Hidden Partition?

Three ways to do it here: https://rentry.org/EmuNANDNewSDcard

su-ER easy if you can plug both cards in at the same time using USB adaptors.
 
Sticking with the same tool…Select the source as you PC’s drive and “Files” and the target will be your new sd card (also files).
Yes, but the option for Atmosphere (SD) File is greyed out in the target sdcard.

The options available are Atmosphere Hidden Partition, SXOS hidden partition and SXOS (SD) File.

I guess it really is not worth to convert to SD File emummc in Atmosphere?
 
Yes, but the option for Atmosphere (SD) File is greyed out in the target sdcard.

The options available are Atmosphere Hidden Partition, SXOS hidden partition and SXOS (SD) File.

I guess it really is not worth to convert to SD File emummc in Atmosphere?
Well, you can just copy them by hand. They are files after all. Yiu will need to modify you emummc.ini to be files based and that’s it.

here’s a step by step: https://gbatemp.net/threads/how-to-make-a-file-based-emunand-for-atmosphere.541810/

I personally don’t mix my emunand and files because a corrupted file system will take out everything and there’s a lot more writing going on in the fat32 partition. Just my personal opinion…ymmv. Read the comments in the link and form your own opinion about files based emmunand.
 
Last edited by binkinator,
Well, you can just copy them by hand. They are files after all. Yiu will need to modify you emummc.ini to be files based and that’s it.

here’s a step by step: https://gbatemp.net/threads/how-to-make-a-file-based-emunand-for-atmosphere.541810/

I personally don’t mix my emunand and files because a corrupted file system will take out everything and there’s a lot more writing going on in the fat32 partition. Just my personal opinion…ymmv. Read the comments in the link and form your own opinion about files based emmunand.
Thank you.

Is the performance issues (being slow, gets corrupted, etc.) on SD file emunand still true to this day? Haven't the kinks been ironed out already?
 
Thank you.

Is the performance issues (being slow, gets corrupted, etc.) on SD file emunand still true to this day? Haven't the kinks been ironed out already?
Well, on its own partition all the files are together. With files on FAT32 they have to be split into 4G files. You could put it on exfat and have a contiguous file but exfat drivers on Switch aren’t the most up to date. The way I understand it, it‘s not so much ironing out the bugs as much as it’s simply trying to fit a square peg in a round hole.
 

Site & Scene News

Popular threads in this forum