Homebrew Is using DBI 658 fine for functionality?

  • Thread starter Thread starter Forger
  • Start date Start date
  • Views Views 17,692
  • Replies Replies 81
You always can create a issue on the github of the tinwoo and for sure you will receive an answer.

Someone already kinda did that. The actual reported issue was solved, but the time outs were not and the dev chalked it up to the users cable and usb ports. Which is honestly a load of bs. https://github.com/mrdude2478/Tinwoo-Release/issues/2

However, it could very well be a fault of NS-USBloader and not Awoo, Tinwoo,etc. as mentioned both in the above git and also on the git for the AtmoXL installer. https://github.com/dezem/AtmoXL-Titel-Installer/issues/15

The problem was also reported several times in the past on the NS-USBloader git, but seems like the devs answer was always basically "I don't know."

I find it odd that after all this time no one has been able to fix this and no one seems to care or even know how to go about fixing it. It's one of two things, the Awoo/Tinwoo family of installers... or NS-USBloader.
 
  • Like
Reactions: Blythe93
Someone already kinda did that. The actual reported issue was solved, but the time outs were not and the dev chalked it up to the users cable and usb ports. Which is honestly a load of bs. https://github.com/mrdude2478/Tinwoo-Release/issues/2

However, it could very well be a fault of NS-USBloader and not Awoo, Tinwoo,etc. as mentioned both in the above git and also on the git for the AtmoXL installer. https://github.com/dezem/AtmoXL-Titel-Installer/issues/15

The problem was also reported several times in the past on the NS-USBloader git, but seems like the devs answer was always basically "I don't know."

I find it odd that after all this time no one has been able to fix this and no one seems to care or even know how to go about fixing it. It's one of two things, the Awoo/Tinwoo family of installers... or NS-USBloader.
you always can take a IDE and start to code and repair or create new code.
 
you always can take a IDE and start to code and repair or create new code.

Or, the people that are already capable and developed these apps can fix their broken shit. I mean if the people that have years of experience writing code can't fix their own code, how does one expect a person that has never developed a line of code in their life to just suddenly pick it up and fix other peoples work? They wrote the code, they should be able to figure out where and why it's going on. It's like anything else. Let's say my tv has a glitch in the menu. It's up to the devs that wrote the code to fix it, not my job to learn how to code from scratch and try to fix it myself.

Anyhoo. At this point I'm kinda leaning towards it being an NS-USBloader issue and not the Awoo family of installers. But I honestly don't know.
 
  • Like
Reactions: Blythe93
The only benefit to me of continuing to use dbi is that the title manager is so much easier to use.
 
  • Like
Reactions: Blythe93
Has never happened to me once.

And? That doesn't mean it doesn't exist. There are enough reports from different people in several places, that span several years, for it to be a confirmed issue. If you're only installing one file at a time you're unlikely to have a problem, especially if using USB 2.0.
 
And? That doesn't mean it doesn't exist. There are enough reports from different people in several places, that span several years, for it to be a confirmed issue. If you're only installing one file at a time you're unlikely to have a problem, especially if using USB 2.0.
I mean I've been following the scene for many years before you and this is the first that I'm hearing of this issue so I think you might just be over-exaggerating.
 
Or, the people that are already capable and developed these apps can fix their broken shit. I mean if the people that have years of experience writing code can't fix their own code, how does one expect a person that has never developed a line of code in their life to just suddenly pick it up and fix other peoples work? They wrote the code, they should be able to figure out where and why it's going on. It's like anything else. Let's say my tv has a glitch in the menu. It's up to the devs that wrote the code to fix it, not my job to learn how to code from scratch and try to fix it myself.

Anyhoo. At this point I'm kinda leaning towards it being an NS-USBloader issue and not the Awoo family of installers. But I honestly don't know.
All open source title installers are based on tinfoil by addubz, and so it's not really their (the current active maintainers of tinfoil) code. And so it's understandable why it's quite a hard problem for any of the maintainers to fix, as they may not properly understand what the code actually does.

This isnt a dig against them btw, just explaining why these issues may not have been fixed. Especially if they can't reproduce the bug themselves.

Most developers who are capable of making / fixing a title installer have no intention to dable with piracy stuff, understandably so.

I do agree with impeeza with the idea that maybe you could look into try fixing this issue yourself. You could learn a lot by how something works by building the code yourself and messing around with stuff, that's how most us got started in the first place ;)
 
Last edited by Deleted member 413168,
I can confirm that bug does exist. It is very very simple and can be easily fixed. Root cause is how app reads from usb, using libnx usb comms.

This is described on switchbrew.org site: when app reads some data from usb input buffer and that buffer has more data, than app reads that extra data is discarded. Inproper handling of this causes hangs or crashes. That's why this happened more on usb3: PC can push more data at the same time frame.
 
Been using DBI forever, also reset my Switch recently and installed everything using DBI, very few problems so far.

Some times MTP transfer can hang and you have to reconnect that's the worse I've got.
 
I realized that DBI's last English release was 658, which was released year and a half ago. I just set up CFW on my Switch, so all of my software is up-to-date (Hekate 6.2.2, Atmosphere 1.8.0); will the DBI 658 be functional still if I were to install it on my Switch? I currently have DBI 749 installed and of course everything is Russian that it's incomprehensible :gun:
I would not use DBI at all. The creator had added brick code and can remote brick every console that uses DBI. For any purposes I would need DBI for I use Awoo Installer.
 
More than half of this thread has been wiped... What happened here :wtf:
Basically, it went way off into left field, and was so bad that the admins wiped the posts that were probably ToS violations.

I have been using the latest english version of DBI since ~2022, with fewer issues than its competition. I have used many alternatives over the years, and I have found that DBI is the most reliable, generally speaking. I have found certain game backups that were only installable with DBI; I could not get them to install with Tinfoil, Awoo, or whatever other programs I have tried and cannot remember anymore.

Are there any new features that I am missing out on, that would actually be worth using the Russian version for?
 

Site & Scene News

Popular threads in this forum