New and Revised SprintOEM??
 

I see that there is a new SprintExtendedOEM folder in the Kitchen dated 2/19. I may have missed it, but I don't recall a post about it.

It differs slightly from schettj's sprintextendedoem_199.zip:

SprintExtendedOEM\07f55440-b239-11db-abbd-0800200c9a66.dsm

starting at hex 36A is now:

5F 00 32 00 30 00 33 00

it was in the zip:

32 00 30 00 33 00 5F 00

Can I ask who made the change and what does the change do?

TIA!

Thank you very much!
I was not adding all the needed info.

Worked like a charm, except if I want to copy more then one shortcut:

; ===== Wisbar Advance 2 =====
Directory("\Windows\Start Menu"):-File("Wisbar Settings.lnk","\Windows\WisbarSettings.lnk")
Directory("\Windows\Start Menu"):-File("Wisbar.lnk","\Windows\Wisbar.lnk")
;

That is the actual text I used and it only copies the second shortcut, and not the first. I even swapped them and still only the second.

Thanks for your help, I am finally on my way to getting a perfect device!

One of your other initflashfiles.txt isn't correct. All initflashfiles.txt need to be in Unicode AND have an blank line at the end. Basically, there should be another line below your semi-colon. To find out which initflashfiles.txt is messing you up, after running CreateOS.exe, go to the Temp/dump directory and open up initflashfiles.dat in Notepad. Scroll down and look at the various lines. If you see two shortcuts on one line, like below

Directory("\Windows\Start Menu"):-File("Blah.lnk","\Windows\Blah.lnk")Directory("\Wi ndows\Start Menu"):-File("Wisbar.lnk","\Windows\Wisbar.lnk")

go find the first one's initflashfiles.txt and fix it. The above happens when the initflashfiles.txt doesn't have a empty EOL at the end (the files are appended to each other, so if there's no empty EOL at the end, it just takes the last line of the previous initflashfiles.txt and appends the next one right to the end of the previous line)

Just as another example of hardcoding, Batti 2.1 has code in it that looks for BattiConfig in the Program Files folder regardless of how you install it. This is not the biggest setback, but still will give users errors.

I've e-mailed David (author) to let him know about this, so maybe he will fix it. I think probably just the ability to set a path to batticfg.exe in batti's registry should make it work.

Re: New and Revised SprintOEM??
 

That change should be immaterial. I took schett's zip and used it to build a rom then when i noticed it wasn't yet in the kitchen folder i copied it up there so more people could find it. the .dsm file is automatically modified by the kitchen sometimes when building a ROM so i wouldn't worry. It looks like it's even the same contents, just moved a little.

Re: New and Revised SprintOEM??
 

Thanks for the explanation!

Anyone know how to figure out how much space a rom is taking up after (or before) you build it? I just want to get an idea of what I can and cannot put in the rom before it goes over the size limit (128 right? or is it 64?)

64. I figured that out the hard way last night building my own ROM (coming soon!) and getting no further than the green Welcome screen. There just ain't enough room in a ROM for .NET 2, Pocket Plus, Spb Diary and SpbWeather, even if you take out stuff like Transcriber and Powerpoint. Feh.

When you're building your ROM, you can see the overall size of it between running CreateOS and CreateROM. After running CreateOS, select boot.hv, boot.rgu and the dump folder and right click, then Properties. Ignore the Size: line. You're looking for the Size on disk: line because that shows how much space the files really take up including file system overhead. That number has to be 64.0 MB or smaller for the ROM to boot. If you're over, don't even bother running CreateROM.bat. You need to pare down first.

Note that you can shave off about 1MB from the dump folder just by deleting the T9 language DLLs (if you've already removed IntelliPad, and why wouldn't you) and unneeded gif and jpg files.

Actually, you can get a lot more than that in a rom. Right now, I have a dump folder that is about 120MB. Perhaps you had issues because of some other error.