Sanity check on my Jasper R-Jtag install (Can't get a consistent boot)

[MTWallet]

Console Type: Jasper
NAND size: 16
Dashboard version: ?.?.16537
CB version: 6723
Screenshot of NAND details from J-Runner: See below
Was the console working before you started: Yes
J-Runner logs (from rater):

This one stuck at LOAD_XAM, nothing ever displayed on the screen.
Resistor:470, AUD_CLAMP ON, Bottom CPU_RST, Voltage Select: OPEN, DIPS 7,8 & 3

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post F7 
Post D7 - RC4_INITIALIZE_CB_B 
Post 17 - VERIFY_HEADER 
Post 15 - FETCH_OFFSET 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 10 - Payload/1BL started 
Post 01 
Post 81 - Panic - MACHINE_CHECK 
Post 01 
Post 01 
Post 81 - Panic - MACHINE_CHECK 
Post 83 - Panic - DATA_SEGMENT 
Post 81 - Panic - MACHINE_CHECK 
Post 01 
Post 01 
Post 03 
Post 83 - Panic - DATA_SEGMENT 
Post 03 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 70 - INIT_VIDEO_DRIVER 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post 22 - INIT_SECENG 
Post 2F - RELOCATE 
Post 2E - HWINIT 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 70 - INIT_VIDEO_DRIVER 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 70 - INIT_VIDEO_DRIVER 
Post 1A - RC4_INITIALIZE 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 70 - INIT_VIDEO_DRIVER 
Post 19 - HMACSHA_COMPUTE 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 1A - RC4_INITIALIZE 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post 22 - INIT_SECENG 
Post 2F - RELOCATE 
Post 2E - HWINIT 
Post 31 - FETCH_HEADER_4BL_CD 
Post 33 - FETCH_CONTENTS_4BL_CD 
Post 34 - HMACSHA_COMPUTE_4BL_CD 
Post 35 - RC4_INITIALIZE_4BL_CD 
Post 36 - RC4_DECRYPT_4BL_CD 
Post 37 - SHA_COMPUTE_4BL_CD 
Post 3A - BRANCH 
Post 40 - Entrypoint of CD reached 
Post 42 - FETCH_HEADER 
Post 44 - FETCH_CONTENTS 
Post 45 - HMACSHA_COMPUTE 
Post 46 - RC4_INITIALIZE 
Post 47 - RC4_DECRYPT 
Post 48 - SHA_COMPUTE 
Post 4B - LZX_EXPAND 
Post 4E - FETCH_OFFSET_6BL_CF 
Post 50 - LOAD_UPDATE_1 
Post 52 - BRANCH 
Post 6C - INIT_SECURITY 
Post 79 - LOAD_XAM 
Most Fails(cumulative): 0xA0
Shutdown

This one ended in RROD.
Resistor:330, AUD_CLAMP ON, Bottom CPU_RST, Voltage Select: OPEN, DIPS 7,8 & 5

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 80 
Post 80 
Post 80 
Post C0 
Post 80 
Post 40 - Entrypoint of CD reached 
Post C0 
Post 40 - Entrypoint of CD reached 
Post 40 - Entrypoint of CD reached 
Post C0 
Post 40 - Entrypoint of CD reached 
Post 40 - Entrypoint of CD reached 
Post C0 
Post E0 
Post C0 
Post 40 - Entrypoint of CD reached 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 70 - INIT_VIDEO_DRIVER 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 70 - INIT_VIDEO_DRIVER 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 70 - INIT_VIDEO_DRIVER 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 70 - INIT_VIDEO_DRIVER 
Post 30 - VERIFY_OFFSET_4BL_CD 
Most Fails(cumulative): 0xA0
Shutdown

updflash.bin log (if applicable): Not yet available
Image of R-JTAG board: See below

Description of problem:
First of all, thanks to all the contributors of all the threads that I have read over the last week. And thanks for any assistance that may come from this post.

I have not been able to get this console to boot consistently and am about to pull my hair out trying to figure out what is going on. NAND read and write went fine, the console has booted Xell about 3 times out of maybe 100 tries over the last 3 days of messing with it. (And I was able to get the CPU key) Most often lots of "Post A0 - Panic - VERIFY_SECOTP_6", but maybe 20 out of the 100 have ended in a hang at "Post 79 - LOAD_XAM". I'm just trying to figure out if I am on the right path to getting this thing to work, or does anybody see something in these POST logs that indicates a wiring issue or something else? Is there a systematic approach to working the DIPs, resistor values, etc. if the standard ones don't work right out of the gate?

Other questions:
1) I am doing all this with the motherboard out of the case, does it all need to be installed & buttoned up for this to work properly?
2) Do I need to unplug the power brick before I change DIP settings and then replug? (This is what I have been doing)
3) Can someone point me to the FAQ/info on how to get the CPU key info via network boot from Xell.
4) I am also having a problem with J Runner, in that when I try to select a dash, it never shows up in the drop down list, but I will try on a different computer before going further into detail on that.

The sordid details, for anyone who wants to know what I have tried so far...
Installed ultimate kit, verified continuity from back of motherboard to top of QSB on the NAND-X & JRP/NANDX/CR QSB's (Both on top-side of MB). Verified continuity through the trace at the end of the JRP/NANDX/CR QSB from the solder point on the QSB to the end of the resistor on the other side of the trace. On bottom of MB, POST QSB install looks good, but I don't know if there is any way to test it with a voltmeter, JTAG QSB continuity check through board for the fat solder points, desoldered the small via point and resoldered, and checked continuity through the resistor at the end of the board. I'm fairly certain soldering and wiring is all good, but will post pictures this evening.

Points 1-3 are bridged on JTAG QSB, and wire run from AUD_CLAMP pad to the correct point on Q2N1. Using bottom MB point for CPU_RST currently, although I have tried the top one as well. Resistor setting is currently 470, but have tried 330, 0 & off.

Voltage select on the R-JTAG board is currently open, but have tried both 1.2 & 1.8 volt settings.

 

[Martin C]

You need to post images and screenshots.

 

[MTWallet]

You need to post images and screenshots.

Yes, they are forthcoming. Camera battery pooped out charging flash for the first shot last night. Just thought I'd get started on the thread in case there was anything obvious in the logs.

Here is screenshot of NAND info.



FWIW, I tried J Runner here at the office and it acts differently that the one at home. I'm guessing the filechecking and downloading is turned off at home, although I never changed it, just did the default install from the mediafire link from the J-Runner v0.2 Beta Build 233 Core Pack message under the downloads section and allowed the update to the newest version. I wonder if not having .net installed at home before I tried to run it the first time made a difference? Or not running it as Admin the first time after installing .net? Very weird.

 

[MTWallet]

Pictures as requested:

R-Jtag board


NANDX


JRP/NANDX/CR & A/V shell ground


MB Bottom (Ribbon cable removed for photo), CPU_RST & AUD_CLAMP


POST


JTAG ALT


And if I may re-iterate the following questions:
1) I am doing all this with the motherboard out of the case, does it all need to be installed & buttoned up for this to work properly?
2) Do I need to unplug the power brick before I change DIP settings and then replug? (This is what I have been doing)
3) Can someone point me to the FAQ/info on how to get the CPU key info via network boot from Xell.

 

[keil423]

Clean up the voltage jumpers on the R-Jtag chip. In the picture it looks like you have all three points slightly bridged.

You should put the mobo back in the cage and hook everything up while tuning.

You dont need to unplug the power to change dips. Just turn the console off.

To get your key via network just plug the console into your router via ethernet. Once the console boots xell and displays the key info you can hit scan IP and it should pop up.
If the console was configured to your wireless network prior to your install you can just plug your wifi in and boot xell. If it wasn't previously configured then it wont work.

 

[MTWallet]

Clean up the voltage jumpers on the R-Jtag chip. In the picture it looks like you have all three points slightly bridged.

Thank you for the advice, I checked the pads with a voltmeter and there was no bridge. (I did clean them up though, a bit of late night de-soldering had them looking pretty [email protected])

Now for the continuing saga...

Since I was able to boot Xell previously a couple of times and get the CPU key, and since I figured out that file checks and downloads were turned off in J-Runner which was what was causing me not to be able to load a dash, I went ahead and built an updflash.bin file for the nand to boot and uploaded that to the console. I can boot 9 of 10 times to the dashboard. The other time out of ten it RROD's right after the power switch.

Since I can run XeXMenu, I'm assuming that the hack is working? You can't run that on a standard console can you?

So, if that is true, now I want to run Rater to tweak the boots and minimize RROD, right? The problem is, Rater doesn't sense the boot, it always hangs on "Post 79 - LOAD_XAM" So I am thinking there is still something strange afoot at the Circle K.

 

[jsinger47]

Definitely try the alt cpu-rst point.

In the case of a spelling error, I blame Tapatalk.

 

[gavin_darkglide]

does it only act this way when using the rater? also the rater wont shut down the console if the nand wires are disconnected. also put everything back in the case, HDD, ODD, kinect, usb drive, wifi, then use the rater to test boot times. the stuff that is plugged in changes the shape of the pulse, which is why you want them all hooked up when tuning, so it is tuned for the optimum boot time when all of your devices are plugged in.

 

[MTWallet]

does it only act this way when using the rater? also the rater wont shut down the console if the nand wires are disconnected. also put everything back in the case, HDD, ODD, kinect, usb drive, wifi, then use the rater to test boot times. the stuff that is plugged in changes the shape of the pulse, which is why you want them all hooked up when tuning, so it is tuned for the optimum boot time when all of your devices are plugged in.

It boots about 9 out of 10 times using 470 ohm resistor setting, AUD_CLAMP installed, Bottom CPU_RST point, open voltage selector and DIPs 7,8 & 3 in the ON position. The other time out of 10 it immediately RROD after pushing the power button. This is with or without the JR Programmer attached.

As to rater.
When all wires are plugged up (both from the MB to the JR Programmer and from the JTAG board to the JR Programmer), rater will start the console and log information, but stops logging at LOAD_XAM although the console continues to boot into the hacked firmware. And it will not log glitch count or turn off the console. This information is also what shows up in the dialog window when using monitor POST in J-Runner without the rater window open.

I was hoping to tune enough to not get RROD without having to have everything buttoned up as it would be a pain to change the resistor setting after everything is loaded back in the case. Or is occasional RROD on boot just something to expect with a hacked console?

 

[FJB66]

On my Jasper I had to use 1.2v to not get the occasional rrod.

 

[MTWallet]

On my Jasper I had to use 1.2v to not get the occasional rrod.

Thank you, will give that a try. Now if I could just get rater to log properly and re-boot the console to get a score...

 

[keil423]

When your running rater do you have the nand wires hooked up as well? You should have the nand wires plugged in as well as rater uses one of them (green) to turn off the console.

 

[MTWallet]

When your running rater do you have the nand wires hooked up as well? You should have the nand wires plugged in as well as rater uses one of them (green) to turn off the console.

I believe this is the one paired with the blue wire as seen here?

If this is correct, then yes, that wire is hooked up during the running of rater.

So, it looks like that traces to J2C3.5. I'll have a look at that solder joint on the QSB.

Does anyone know which POST code rater uses to interpret a successful boot and send the shutdown signal? Is it supposed to be LOAD_XAM?

 

[AllyNerd]

Im no post expert but load xam is the furthest i ever see. Should be no rrod did you try alt cpu as jsinger suggested. And your nand wire is fine as long as you have the wire connected to your jrp

 

[jsinger47]

Post 79 is a full boot. ........

In the case of a spelling error, I blame Tapatalk.

 

[chronic1553]

if your having issues with rater shutting the console down just doing it the old fashioned way, when you see it say shutdown, press the button

 

[MTWallet]

<snip> Should be no rrod did you try alt cpu as jsinger suggested.<snip>

I will be trying that tonight as part of a thorough effort to find the proper settings using all of the DIP settings, CPU_RST wire placement, voltage select, etc.

Post 79 is a full boot. ........

Thanks for verification on that. That's what I thought, just wanted to hear from someone else with more experience.

if your having issues with rater shutting the console down just doing it the old fashioned way, when you see it say shutdown, press the button

That is the problem, rater never says shutdown or starts the timers unless I click Stop or Nudge. It doesn't seem to understand that the console has booted, even though it shows LOAD_XAM in the POST log.

Maybe I am doing something wrong trying to run rater. Here is what I do, is this correct?

Click CR3 Pro Rater
Select Phat (as it is a Jasper)
Change cooldown to 60 (I'm not really "tuning" yet, just trying to get consistent boots.)
Change No. of Boots to 10 (Again see above)
Then click Start
Stuff shows up in the POST Output window (See my first post that stuck at LOAD_XAM)
And then it just sits there until I click Stop or Nudge (Meanwhile the console has fully booted to the dash)
When I click Stop or Nudge "Shutdown" shows up in the POST Output and it does turn off the console.

The first time Xell booted and actually displayed on the screen I was using rater ('cause I didn't know about the monitor POST option yet), and after Xell came up the shutdown delay timer started and turned off the console (before I could write down the CPU key of course!) and then the cooldown timer started. I say this to infer that I think I know what is supposed to happen when rater is running, but could someone confirm.

Maybe I still have a corrupt install of J-Runner. Does anyone know where the settings are stored on the hard drive? I did an un-install previously and deleted the directory it was in, but when I re-installed, it still had the setting for File Checks/Downloads turned off, so I think there is a settings file somewhere else than the install directory.

 

[chronic1553]

I will be trying that tonight as part of a thorough effort to find the proper settings using all of the DIP settings, CPU_RST wire placement, voltage select, etc.



Thanks for verification on that. That's what I thought, just wanted to hear from someone else with more experience.



That is the problem, rater never says shutdown or starts the timers unless I click Stop or Nudge. It doesn't seem to understand that the console has booted, even though it shows LOAD_XAM in the POST log.

Maybe I am doing something wrong trying to run rater. Here is what I do, is this correct?

Click CR3 Pro Rater
Select Phat (as it is a Jasper)
Change cooldown to 60 (I'm not really "tuning" yet, just trying to get consistent boots.)
Change No. of Boots to 10 (Again see above)
Then click Start
Stuff shows up in the POST Output window (See my first post that stuck at LOAD_XAM)
And then it just sits there until I click Stop or Nudge (Meanwhile the console has fully booted to the dash)
When I click Stop or Nudge "Shutdown" shows up in the POST Output and it does turn off the console.

The first time Xell booted and actually displayed on the screen I was using rater ('cause I didn't know about the monitor POST option yet), and after Xell came up the shutdown delay timer started and turned off the console (before I could write down the CPU key of course!) and then the cooldown timer started. I say this to infer that I think I know what is supposed to happen when rater is running, but could someone confirm.

Maybe I still have a corrupt install of J-Runner. Does anyone know where the settings are stored on the hard drive? I did an un-install previously and deleted the directory it was in, but when I re-installed, it still had the setting for File Checks/Downloads turned off, so I think there is a settings file somewhere else than the install directory.

sometimes my rater will do that on occasion. you said you removed, also you should have file checks/downloads enabled.

 

[MTWallet]

sometimes my rater will do that on occasion. you said you removed, also you should have file checks/downloads enabled.

Yes, I figured out the file checks thing and turned it back on. But I don't know if there is something else turned off that shouldn't be that could be causing this behavior. I would like to find the settings file and just delete it, in addition to the program directory, and just start over with a clean install of J-Runner.

I see from the changelog that in v280 "- Changed Use of registry for settings (values are stored elsewhere)". Anyone know where "elsewhere" is?

Nevermind the settings question. I found it. C:\Users\USER\AppData\Local\Mama's_Little_Bakery\settings.xml

 

[chronic1553]

make sure you download the latest version of jrunner also.

if i were you i would remove the nand-x qsb's and just do a wire install, i never use the nand-x ones and SB jaspers are my favorite to do, they almost always a breeze. this is just what i would do, im not saying it will fix it, but worth a shot.