VisorCentral.com - deleting rom based app.

Show 20 posts from this thread on one page

VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- deleting rom based app. (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=14168)

Posted by vaj123 on 04-18-2001 02:29 PM:

I am trying to delete a reference guide but Filez says "the file is rom based and cannot be deleted or modified" Is there any other way to get rid of it?
Thanks
Vicki

Posted by BobRus on 04-18-2001 03:17 PM:

Well there is one solution, but it requires voiding the warranty:

Open your visor, locate the ROM chip, remove it using a soldering iron, copy the apps you want to keep and the OS on a new ROM, solder the new ROM in place of the old one, close your visor and pray for it to work

No seriously there is no way of deleting a ROM based app (ROM means Read Only Memory), it is a static memory burnt (written) once for all.

BobRus.

Posted by PDAENVY on 04-18-2001 03:30 PM:

You can stick it in a category you don't look at. At least it won't clutter up your launcher.

__________________
Jeff

Posted by vaj123 on 04-18-2001 04:12 PM:

Ok Thank you BUT how and why did it end up there? Any ideas....I downloaded it from Reader express and tried to move it to my 8mb flash module.... obviously i'm technologically challenged so any help or suggestions would be appreciated.
Thanks
Vicki

Posted by Rob on 04-18-2001 04:40 PM:

quote:
Originally posted by vaj123
Ok Thank you BUT how and why did it end up there? Any ideas....I downloaded it from Reader express and tried to move it to my 8mb flash module.... obviously i'm technologically challenged so any help or suggestions would be appreciated.
Thanks
Vicki

If it's on your flash module, I don't know if you can delete it using the built-in PalmOS delete menu option. I think you have to use the filemover to delete it.

Posted by MarkEagle on 04-18-2001 11:08 PM:

quote:
Originally posted by Rob
If it's on your flash module, I don't know if you can delete it using the built-in PalmOS delete menu option. I think you have to use the filemover to delete it.

I think the problem here is that Filez won't delete from the module. I'm not sure about the standard Delete function myself but FileMover should definitely be able to delete it.

__________________

God bless America, my home sweet home...

Posted by na2rboy on 04-19-2001 02:38 PM:

datebk4 faq

The following is from the Datebk4 FAQ:

quote:
At this time, there is an application, EditRom, which apparently has the capability of removing built-in applications while leaving a small stub to maintain the CreatorID of the original database so that hotsyncing proceeds normally. As of 20-mar-2001, it is not known if this application is out of beta, or whether it has been officially released. You can check the various Palm Software archives to see what the current status is for it.

Has anybody seen this program or tried it?

Posted by BobRus on 04-19-2001 03:16 PM:

Sorry to insist folks but you can NOT erase what is written in a ROM.

What the Datebook 4 faq talks about is FLASH ROM which is used in Palm products. Handspring products use ROM not FLASH ROM.

HereAfter the full text from the FAQ:

Now that I've loaded DateBk4, can I get rid of the regular Datebook application?

No. The built-in datebook application is stored in ROM (Read Only Memory) and cannot therefore be removed. The only downside is that when you do a Find, the built-in datebook application will also insist on searching the same database, but no harm is done by that. Note that if you start the search while DateBk4 is running, DateBk4 will ALWAYS search the Datebook database before the built-in datebook application. Warning: If you have a flash ROM, you might think that you can remove the Datebook application, but if you do that, the Datebook database will NOT be HotSync'd, so we suggest you do not do this. It would also crash your system if you unchecked the option to have DateBk4 handle alarms (since the Rom code would try and launch the Datebook application that no longer exists). Note that unless there is a way of actually freeing up memory (FlashBuilder merely masks the built-in application - it does not remove it), there is little advantage in doing this. At this time, there is an application, EditRom, which apparently has the capability of removing built-in applications while leaving a small stub to maintain the CreatorID of the original database so that hotsyncing proceeds normally. As of 20-mar-2001, it is not known if this application is out of beta, or whether it has been officially released. You can check the various Palm Software archives to see what the current status is for it.

BobRus

Posted by K. Cannon on 04-19-2001 04:56 PM:

She says "I downloaded it from Reader express and tried to move it to my 8mb flash module" so it's not a built in program.

Posted by creole on 04-19-2001 05:20 PM:

related to the DateBk issue...

my question is this:
My Prism is brand new, I have not downloaded any additiona datebook software, yet I have both versions on my VPR. Why would Handspring give me duplicates straight from the factory? Wouldn't it have made sense to delete the standard datebk?

Posted by Rob on 04-19-2001 06:21 PM:

quote:
Originally posted by creole
related to the DateBk issue...

my question is this:
My Prism is brand new, I have not downloaded any additiona datebook software, yet I have both versions on my VPR. Why would Handspring give me duplicates straight from the factory? Wouldn't it have made sense to delete the standard datebk?

I believe that the Palm licensing agreement forbids licensees from removing or modifying the built-in apps. They can add their own custom/enhanced apps, but can't remove the built-in ones. The idea being to provide a consistent base-line of functionality across all PalmOS devices.

Posted by vaj123 on 04-19-2001 06:36 PM:

As always, thank you all very much for your help and advice, I was able to delete the application with the File mover....I thought I had tried that initially but obviously I was wrong.....
I don't know what I would do without this forum, I am learning so much and have found solutions to so many of my {self induced} visor problems.... I'm learning LOL slowly but i'm coming along.
I do have another question, It seems as though I have so much less free space on my internal system now that I have purchased the flash module and I can't quite understand that. it sort of seems as though i'm defeating my purpose.
when I try to move an application that says that I should copy it????what does that actually mean?does it really stay on the visor or what, I guess I just don't understand the point of it....
Thanks again
Vicki

Posted by Rob on 04-19-2001 07:26 PM:

quote:
Originally posted by vaj123
I do have another question, It seems as though I have so much less free space on my internal system now that I have purchased the flash module and I can't quite understand that. it sort of seems as though i'm defeating my purpose. when I try to move an application that says that I should copy it????what does that actually mean?does it really stay on the visor or what, I guess I just don't understand the point of it....

vaj,

There are two kinds of files you can put on your visor: applications (.prc files) and databases (.pdb files) (actually, there are more than two, but these are the main ones). Applications can be moved to the flash module and will be accessed directly from the module when you run the application. Databases can be read from the flash module, but not written to. The warning you are getting when you try to move a database to the flash module is telling you that if an application tries to write to the database while its on the module, then you will get errors and may crash. What this means is that you should only put databases that won't be modified on your module: dictionaries and other references, peanut reader books or other docs you won't modify, etc. Many games have databases that also don't get modified, but this takes some trial and error to figure out which ones work. To be safe, just keep other databases on your visor, and mainly keep applications on your module. There's really no reason to 'copy' a file (and have it exist on both your visor and module) unless you are doing it to backup that specific file (but I think it makes more sense to just get a backup module and back everything up)

Posted by dalamar70 on 04-19-2001 07:34 PM:

quote:
Originally posted by creole
I have not downloaded any additiona datebook software, yet I have both versions on my VPR. Why would Handspring give me duplicates straight from the factory? Wouldn't it have made sense to delete the standard datebk?

Another strange difference is that apparently DateBook+ (the Handspring modified one) does not have the Beam Event option, whereas the original Palm OS Datebook does.

Posted by PDAENVY on 04-19-2001 08:23 PM:

quote:
Originally posted by dalamar70

Another strange difference is that apparently DateBook+ (the Handspring modified one) does not have the Beam Event option, whereas the original Palm OS Datebook does.

Maybe this is part of the reason they left both on.

__________________
Jeff

All times are GMT. The time now is 02:46 AM.

Show 20 posts from this thread on one page