I am unable to replicate your issues (the original one about the .net file and this one). If you're not using the latest kitchens, download them and try again. While you can't click on items in the buildstatus window, if you push the "Save to File" button at the top of the window, it will create a logfile with the current date in the filename in your installation directory that contains the buildstatus log.

I got it now thanks for the help. 60 Hours in 3 days taking its toll on my mind.

I tried this with the new version (just downloaded) and got the same result. See attached images (note: the splash image was a screen dump from the .nb converter program -- could not figure out how to save it as a .bmp).

same result for me as well... but it does have less green dots i think :)

No change. I don't know if this helps isolate the problem, I accidentally choose Qwest.nb and it looked ok in the BuildOS\temp folder. Rebuilt with HTC.NB and it again had the green artifacts in the BuildOS\temp folder.

I'm guessing this only affects certain colors, which is why the mostly grayscale or white screens come out okay and photos get totally messed up.

Ok, turns out it was broken for both converters, and I had only fixed one before. New build has been posted.

For the curious, it's actually a bug based on the low order Red color bits. Windows manipulated the pixel value on my behalf in order to distribute accumulated error when moving from a low color depth to a higher color depth. My logic assumed the pixel value I put in would be the pixel value I got out (sounds reasonable, doesn't it?), so when it wasn't things went awry. You see the artifact as green because the low order red bits were writing on top of the high order green bits. By pure chance, green does not write on blue because of an election I took in the code. Blue doesn't have a color after it to overwrite. So, the only color getting messed up is green, which explains why all the artifacts were green.

Fixed!

Thanks gguru.

For the record, I AM "the curious"... ;-)

Excellent work on this program by the way. =D>

So a hard reset, of course, restores from serious system problems, but also can remove issues that could be left after a ROM flash.

What about, say its been a long time since a hard reset, making a full Spb backup, then hard reset, then full Spb backup restore? Advantages? Waste of time? If you correct any issues with a hard reset, does a backup restore also restore the issues?

I am looking for a better understanding of what a full or system backup does and how that relates to benefits gained by a hard reset. My assumption has been that the hard reset could serve a maintenance or "oil change" function, but don't want to turn around and pour the old oil right back in.

Problem Solved !!!, thanks Guru !!!