Foire Aux Questions

Que corrige le Patch 3.5.2 ? est-ce le même Patch qui corrige les problémes de DRAM 8mo ?

Rappel: Il y 2 choses distincts, un probléme physique sur le puce de 8mo et un probléme de logiciel sur l'OS 3.5
Probléme sur PDA équipé de 8mo
(Palm IIIxe IIIc Vx VisorDeluxe TRG-Pro
Probléme sur PDA équipé de Palm'OS 3.5

Ce probléme existe sur certaines machine de 8mo (IIIxe IIIc Vx trg-pro et visor deluxe) il n'est pas générale à toutes les machines, le Patch est constitué de 2 programmes, l'un test la machine et si le test est (malheureusement) positif, l'installation du patch correcteur est nécessaire.
Mais ... il s'ait révélé dans mon cas qu'un ami possédant un Vx avait de fréquent bloquage machine sérieux nécessitant un reset hard avec toutes les conséquences de perte de temps et de config non récupéré à 100%. L'ecran du Vx rebootait sans cesse (un vrai flash). Le Passage du programme test n'a rien révélé de particulier. Mais j'ai tout de même installé le patch et à présent plusieures semaines sont passée le bug à disparu. Alors soit le programme de test n'est pas assez pointu - soit le patch corrige aussi ce bug... à voir.

>Est-il vrai que ce patch, corrige effectivement très bien le problème,
>mais fait perdre 10% de la capacité de stockage du Palm ?

Aprés lecture et re-lecture de l'article de TRG concernant ce probléme physique de dram 8mo, il semblerait que le patch ne fasse pas perdre de capacité de stockage donc ma premiere interpretation (secteur defectueux inhibé par le patch) ne tient pas la route alors voilà celle de TRG:

tant que le pda est allumé, la dram est rafraichie par le processeur au niveau stockage et lecture des secteurs. quant le palm se coupe c'est à la dram de faire ce boulot du moins à la partie controleur de la dram or certaines dram n'avaient pas ou plus cette fonctionnalité active resultats aprés extinction de la machine la dram pouvait ecrire aléatoirement dans des zones mémoires qui pouvez:
- avoir rien (ouf!)
- avoir des données (conruption)
- ou avoir du code (bug)
l'astuce de TRG est d'empecher la dram de passer en mode auto-refresh. Je suppose que sur Visor et Palm l'explication est identique et la solution également.

Patch:
=> Version pour Palm
     http://palmsupport.conxion.com/french
=> Version pour TRG-Pro
     http://www.trgpro.com/support/faq_dram.html
=> Version pour Visor Deluxe
     http://www.handspring.com/support/ts_visor_test_download.asp

Le probléme lié à l'OS3.5
Un patch pour faire passer de l'OS 3.5 à l'OS 3.5.2 qui corrige tout les palm de version 3.5 pour récuperer les secteurs orphelins lors du reset et résoudre également préventivement un bug du noyau kernel.
Aprés installation du Patch, le programme " Victor " n'est plus necessaire.

Il est évident que pour installer le Patch il faut déjà avoir l'OS3.5 sur son Palm, le Patch (correctif) n'est qu'un tout petit programme.

Source Palm: http://oasis.palm.com/dev/kb/papers/1846.cfm
"When a soft reset was performed, memory which previously had been allocated with FtrPtrNew() was not being automatically freed, which would result in a memory leak. The same situation existed for memory allocated with DmNewHandle() if the handle was not added to a database before a reset occurred (a.k.a. "orphaned" chunks.)
If the Exchange Manager was instructed to transfer a record database which had zero records in it, it would cause a system error.
A low level system resource in the kernel, used for inter-process synchronization, was not being installed correctly. While we have never seen any adverse effects, nor have we had any reports of this causing trouble, we are correcting it as a precautionary measure. If this were uncorrected, trouble might theoretically be seen intermittently in use of the Network Library, or perhaps when using the Alarm Manager. In practice, however, this has not been found to be a problem, so we are correcting it just to be safe."

Telechargement: http://www.palm.com/support/downloads/update352.html

L'explication de TRG sur le probléme de DRAM 8mo:

Q: What is the problem?
A: A faulty memory chip used in production of TRGpro computers will cause random fatal errors and data corruption. TRG’s upgrade to Palm OS 3.5.1 addresses the issue, and users are encouraged to upgrade. The upgrade can be downloaded from http://www.trgpro.com/support/update.html.

Q: What are the symptoms?
A: The most common symptom is a “Fatal Exception” error after the unit has been powered off for a period of time. Other symptoms include corrupted data in the unit.

Q: If I buy a TRGpro today, will it have this problem?
A: TRGpro computers purchased directly from TRG Products will not have this problem. It is possible that a user could purchase a unit through a distributor that contains the faulty chip. If this happens, the user will need to upgrade to OS 3.5.1. If the unit has OS 3.3, the user is encouraged to upgrade to OS 3.5.1.

Q: How do I determine what OS version my unit has?
A: From the launcher, press the menu icon, and select "System Info..."

Q: What if I don’t see any problem with my unit?
A: TRG still recommends that the user upgrade their operating system. The problem could occur in the future.

Q: Can I swap my unit?
A: The new operating system will completely solve the problem, and there is no need to exchange units.

Q: What if I don’t want to upgrade to OS 3.5.1?
A: TRG recommends that the user upgrade to OS 3.5.1, but a patch for OS 3.3 will be available shortly for those users who do not want to upgrade.

Q: How do I upgrade my unit?
A: Go to TRG’s web site at http://www.trgpro.com/support/update.html. Instructions there will guide you through the process.

Q: What happens to a TRGpro device with an affected DRAM chip?
A: There are three possible outcomes:
(1) Random data could be written to an unused portion of memory, which has no effect on the user.
(2) Random data could be written to a portion of memory storing users' data. This could cause the user's data to be overwritten.
(3) Random data could be written to a portion of memory storing operational code. This could causes the device to fail to wakeup, or even to experience an error requiring a complete reset of the device.

Q: Is this a Palm OS problem?
A: No. This is related to an 8 MB DRAM component supplied to TRG.

Q: How is TRG Products going to resolve this issue for its customers?
A: The latest Palm OS 3.5.1 fixes the problem and can be quickly and easily downloaded from the web site.

Q: Should I stop using my TRGpro?
A: No but you should upgrade your Palm OS to Palm OS 3.5.1

Q: What if my applications fail on Palm OS 3.5.1?
A: Please make sure that the applications are compliant with Palm OS 3.5. If they are not please contact the developer about an upgrade. Staying on Palm OS 3.3 is not a good option. TRG Products and Palm will work with developers to encourage them to upgrade to Palm OS 3.5.

Q: Will the I loose access to certain parts of memory with the fix?
A: The fix simply avoids the use of DRAM self-refresh mode (see bleow). The amount of available memory will not be affected.


Technical Description of the Problem
Q: What causes the DRAM problem?
A: The exiting of self-refresh mode on a certain vendor's DRAM was not implemented correctly. This can cause a portion of memory to become corrupted.

Details: The Palm OS goes to sleep and wakes up once every minute to perform some housekeeping functions. This, in turn, causes the DRAM to enter and exit self-refresh mode once per minute. Since self-refresh mode is flawed in certain vendor's DRAMs, there is a chance for data corruption to occur every time self-refresh mode is exited on units which use that vendor's DRAMs.

Q: What is DRAM self-refresh mode?
A: When your unit is on, the processor is responsible for maintaining the contents of DRAM. When the unit is "off", the processor is shut down and the DRAM is commanded to assume responsibility for its own refresh. This mode is called DRAM self-refresh.

Q: How likely is the failure to occur?
A: If your unit contains the faulty DRAM, it is a statistical certainty given infinite time.
Details: Through testing, TRG has observed that there is about a 1/8000 chance of a row of data (2K) being corrupted every time self-refresh is exited. In a 24 hour period, the TRGpro will wake up 1440 times. In 5.5 days, the unit will experience 8000 wake / sleep cycles. If a corruption occurs in an area of memory that is in use, you will experience the problem. Since the location of the failure in memory is random, your odds of detecting the failure will increase with the amount of memory you use.

Q: How can software fix this problem?
A: TRG developed a work-around which does not put the DRAM into self-refresh mode. If self-refresh mode is not used, the problem will not occur.
Details: TRG refreshes the DRAM using a technique called "burst CBR refresh". This avoids the need to enter/exit self-refresh mode.

Q: How did TRG discover this problem?
A: TRG was testing a change to Palm OS3.5 that required the unit to wake up once every 5 seconds instead once per minute. This increased the chances of the failure occurring by 12x. With the help of TRG's beta testers, the problem was then detected and isolated to a particular vendor's DRAM. TRG then reported the problem to the DRAM manufacturer and developed the fix.

Si vous avez un Palm IIIxe, IIIc, ou Vx avec OS 3.5:
installez les 2 patchs, ils peuvent coabiter et sont complémentaires.