Print

[DDRLord]

Alright, so I happily picked up size 10 and 20 torx screwdrivers, along with a conductive pen (I left all my old stuff back at home, and my dorm was somewhat bare) and flashed my TSOP with a copy of iND-Bios 5003 with a bundled ind-config.cfg (since the boot time was killing me.) So far I am exceptionally happy, though I have been having one annoying problem.

When I try and do an in game reboot, or just plain quit an application, I get a kernel panic 21 error. It's not a huge problem, I can just get up and flip it off and back on, but it kind of kills the beauty of the whole "exiting" thing. I heard it had something to do with iND blocking the MS Dash, but I'm using XBMC, so that shouldn't be a problem. I also heard there was an option you could toggle to prevent such a blocking, but I couldn't find it. Does anyone have any idea what could be causing it, and what I could do to solve it?
If even Xbox-Scene's greatest minds are baffled... then which would they suggest, M8+ or Xecuter2 4983? (The only things I care about are customizability and stability, the former of which iND is incredible for, and the latter not so much at the moment.)

Also, does anyone know of any good sources where one could get some .x files for iND? I know there's a few on AllXboxSkins.com, but I'm looking for something more. The site that's in the .nfo seems long gone by now, seeing as how I jumped on the Bios train a wee bit late.

This post has been edited by DDRLord: Nov 4 2006, 07:27 AM

[DDRLord]

See, this is the exact reason why I'm so reluctant to post in forums. Five seconds after I post this (which was after two hours of nonstop searching and Googling) I find the solution. So, in hopes of no one else making the same mistake I did, I'm going to post a whole lot of keywords so that my fellow search engine surfers will find this out more easily than I did...

If you are getting a kernel panic 21 error when exiting (or quiting) an application or emulator or game or during an In Game Reset (or IGR) using iNDBios (typically spelled iND-Bios) 5003 (or who knows, maybe 5001 or 5002 as well) you can fix it by just keeping a copy of ind-config.cfg (which you probably have injected into your bios anyway) on your hardrive. I kept it on my C drive, but you should put it on whatever drive your copy of iND searched on (be it D or E or F.)
This fixed it up on my 1.0 Xbox (flashes to TSOP) but I'm sure it'll work for 1.1, 1.2, 1.3, 1.4, 1.5, or 1.6 (1.6a or 1.6b) modchip or no.
(Not so wordy solution: keep ind-config.cfg on your hardrive, even if you injected it. It'll stop the errors.)

There, that ought to keep all of the not-quite-scenesters like me at bay (at least once Google spiders it.)

Still looking for .x files, though... any good suggestions?