View Single Post
  #1 (permalink)  
Old 02-06-2008, 12:00 PM
blizzard07's Avatar
blizzard07
Lurker
Offline
Location: NY
 
Join Date: Oct 2007
Posts: 19
Reputation: 1
blizzard07 is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
ROM versus RAM, OEM versus .cab

I have been cooking since my vx6700. Lots of fun and lots of kitchens. These devices are awesome with the work that you all do. I wish the carriers would hire you all !!

With my VX6800, I have done all of the ROM. Still having fun.

I have a couple of questions, With all the ROM Choices and I am sure Kitchens soon.

1. What are the advantages of cooking a ROM with all the extra OEMs?

2. Is ROM faster than RAM?

3. Is OEM faster than .cab?

4. Programs that are being updated alot, such as Microsoft Live and S2U2, would I be better loading them into RAM and keeping the tested in ROM. What happens when Microsoft updates Live and I have it in ROM?

5. Is loading the ROM to Capacity with all of the OEMs, say down to less than 10% available memory. Does that slow the phone down?

5. If I just go with a clean ROM, am I just wasting memory in the ROM and using up the RAM?

I do understand that having the ROM saves time on a hard reset. But the only time I do that is for something new and fun from you all

Bottomline, would you all recommend:

1. Clean ROM, and add the .cabs
2. Find a ROM that I like
3. Cook with a kitchen, when readily available?

Sorry for being long. In advance, I really appreciate any responses. This is something bugging me for a while. An explanation will be much appreciated
Reply With Quote