- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
ChokeD said:My di.bin was 44kb on 111 and now that I'm on 114 it has changed to 33kb. Both tested and worked.
EDIT: I might add my 111 di.bin was patch, 114 di.bin is not.
I try to be as thorough as possible.Cyan said:thanks for updating it, and took the time to make screenshots too
Digital1980 said:hmm, the di.bin is 33kb as well but now I swapped out Wii's with a 1.0.6 HBC and now I'm getting a series of flashes.
Are there solutions to the blinking codes?
-added slot blinking on fatal errors
1 short flash : The TMD of the requested title is missing
2 short flashes: The TMD of the IOS the current title uses is missing
3 short flashes: The kernel.bin is not found on sd and or usb
ChokeD said:I wish I could help with that, but all I would do is redo what is behind the the diagnoses, in other words I don't know oop:
I'm new to this as well... But, after using IOS80 instead of IOS70 mine started booting.NReale3370 said:I'm voting a cross between armboot.bin problems and/or usb drive incompatibilities (since I'm getting that on any usb related sneek)Digital1980 said:twig123 said:This info was added as of R112. It would be nice to have in the Troubleshooting/Error section:
-added slot blinking on fatal errors
1 short flash : The TMD of the requested title is missing
2 short flashes: The TMD of the IOS the current title uses is missing
3 short flashes: The kernel.bin is not found on sd and or usb
4 short flashes: Failed to load the requested IOS (missing IOS, missing
TMD/Ticket/content)
how about "hang at a black screen"
Is there a troubleshooting explanation for that?
twig123 said:I'm new to this as well... But, after using IOS80 instead of IOS70 mine started booting.NReale3370 said:I'm voting a cross between armboot.bin problems and/or usb drive incompatibilities (since I'm getting that on any usb related sneek)Digital1980 said:twig123 said:This info was added as of R112. It would be nice to have in the Troubleshooting/Error section:
-added slot blinking on fatal errors
1 short flash : The TMD of the requested title is missing
2 short flashes: The TMD of the IOS the current title uses is missing
3 short flashes: The kernel.bin is not found on sd and or usb
4 short flashes: Failed to load the requested IOS (missing IOS, missing
TMD/Ticket/content)
how about "hang at a black screen"
Is there a troubleshooting explanation for that?
Another thing that I missed was that you need at least 1 game dumped to USB:\games in order to boot
(Dumped with DiscEx from SNEEK google code site)
What I did was start off with just SNEEK (no DI, no UNEEK) and make sure it booted.
I was also very impatient. Per the guide it takes about 5min to start the first time.
This is not an understatement as mine took ~10min to boot (with no signs of activity. no USB flashing or anything).
I gave up waiting and just let it sit at the black screen and went and took a shower. When I came back, it had booted!
I like window7 but everything has to be right clicked and ran as an Administrator. Did you make sure the python was registered in the Environment Variables as per guide ?? W7 definitely sucks for running multi-process apps.Digital1980 said:HMM, interesting. I've used it before but never had to wait that long. I'll definitely give that a try though.
I just reinstalled the tools. Still a no go. The only other thing I can think of is that I"m using Windows 7 which might make a difference because I got an error while compiling for the msvcr100.dll which I went out and found and put in there. It seemed to go work after that.
That's it! Virtual XP time. Windows 7 will lose my support if this is the problem....
ChokeD said:I like window7 but everything has to be right clicked and ran as an Administrator. Did you make sure the python was registered in the Environment Variables as per guide ?? W7 definitely sucks for running multi-process apps.
Yes, please do that cause I have a W7 machine but I've been avoiding it for fear of a major hassle.Digital1980 said:ChokeD said:I like window7 but everything has to be right clicked and ran as an Administrator. Did you make sure the python was registered in the Environment Variables as per guide ?? W7 definitely sucks for running multi-process apps.
I didn't right click and run anything as administrator but it all seemed to run without error. Am I supposed to run the command prompt as Admin in Win7?
I did have to go back and read the guide a few times because I had Python 2.7 installed and and needed 2.6.5 for armboot.bin to be created for the exact guide instructions. The Virtual machine is almost set up. I'll let you guys know know if Win7 was the culprit.
I had the msvcr100.dll problem as well. I assume you have Win7 64bit (x64)? yes? me to.Digital1980 said:HMM, interesting. I've used it before but never had to wait that long. I'll definitely give that a try though.
I just reinstalled the tools. Still a no go. The only other thing I can think of is that I"m using Windows 7 which might make a difference because I got an error while compiling for the msvcr100.dll which I went out and found and put in there. It seemed to go work after that.
That's it! Virtual XP time. Windows 7 will lose my support if this is the problem....
concerning msvcr100.dll,twig123 said:I had the msvcr100.dll problem as well. I assume you have Win7 64bit (x64)? yes? me to.Digital1980 said:HMM, interesting. I've used it before but never had to wait that long. I'll definitely give that a try though.
I just reinstalled the tools. Still a no go. The only other thing I can think of is that I"m using Windows 7 which might make a difference because I got an error while compiling for the msvcr100.dll which I went out and found and put in there. It seemed to go work after that.
That's it! Virtual XP time. Windows 7 will lose my support if this is the problem....
I had to download the 32bit! (x86) version of Visual Studio Runtime 2010 to fix mine.
http://www.microsoft.com/downloads/details...;displaylang=en
I think MS has a bug with the 64bit installer or something
(Test it, if it works... we got another thing to add to the guide)
I have my Win7 always running as admin...Digital1980 said:great, getting the same error in virtualization mode. I guess I'll have to try logging on Administrator. I'll still need the missing .dll though? Should I install visual studio 2010? Seems like a waste of download and install considering i'll never use it and I can easily get the needed .dll from elsewhere.
here is a screen shot of the error.
Windows 7 .,grrrr
Ok, thanks for the knowledge.twig123 said:I have my Win7 always running as admin...
I also already had the x64 version of the runtime installed and STILL had the problem. even after reinstalling the x64 runtime.
To fix the problem, I uninstalled the x64 runtime and installed the x86 runtime in my previous post. all is well now.
Well it would make sense considering the command prompt wants to run as 32bit. ????
@ChokeD - No, there should be no additional variable needed, as the .dll in question is already in the system32 folder (which is already a system variable by default. If that variable didn't work, you would likely have all sorts of issues with your windows install and not just this app)
Not really, 64bit dll's are added to the SysWOW folder... if you checked, when you install the x64 version of the runtime it installs the dll into the System32 folder instead. I tested copying the x64 dll from System32 to SysWOW and still got the error.ChokeD said:Well it would make sense considering the command prompt wants to run as 32bit. ????
Yeah, I always seen the files put in the x86 folder for 32bit but never knew that they were added to a SysWOW for use with 64bit. I'm still learning. Thanks for humoring my intellect.twig123 said:Not really, 64bit dll's are added to the SysWOW folder... if you checked, when you install the x64 version of the runtime it installs the dll into the System32 folder instead. I tested copying the x64 dll from System32 to SysWOW and still got the error.ChokeD said:Well it would make sense considering the command prompt wants to run as 32bit. ????
In essence, I still believe this is a problem that MS should have addressed before the release of the new runtime set..