VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- Build Week, Update Patch and an Update on mine... (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=3131)

UPDATE 7/26:
I just exchanged the one I had bought over the weekend for a new one. The orig. had a week 15 build date via the serial number, the new one had week 24 (pretty current as we are in week 30 right now)
The patch I just installed on the new one did not apply the memory portion. This simply confirms the problem is affecting the Jan-May 2000 VDX's.

I take issue with HS's notice, to wit:
"Only a limited number of Visor Deluxe handhelds shipped between the period of January 2000 to June 2000 may be affected with this faulty chip."

Either we are all unlucky here or ALL such units have the problem. Comments?

quote:

---

Originally posted by dequardo:
I take issue with HS's notice, to wit:
"Only a limited number of Visor Deluxe handhelds shipped between the period of January 2000 to June 2000 may be affected with this faulty chip."

Either we are all unlucky here or ALL such units have the problem. Comments?

---

Built prior to Jan.00??!!

I got my BVD on 11/24/99. The DRAM test says mine is fine.



------------------
Joe V. - Simi Valley, CA

Thanks folks. The point I was trying to make is that I believe ALL VDX's built from 1/00 through 5/00 exhibit the DRAM fault-not only a 'limited' number.

I got my BVD 3/2000 and i'm one of those who "DOES NOT" have the DRAM problem.

Not all of the units made between those dates HAVE to have the flaw.

Here's the process:
1) A single batch of RAM chips apparently made it through testing at the manufacturer, and into distribution channels.
2) This batch was split into multiple packages and shipped to various manufacturers of hardware that uses said chips.
3) These manufacturers order MANY chips at a time, and likely get some from several different batches in each shippment recieved.
4) All the chips from each shippment are put into devices as they are pulled from boxes.
5) The devices, passing standard QC testing (just like the RAM did at it's manufacturer) are boxed up and shipped out, some with the faulty RAM, some with good RAM.

Thanks Theo. Good point and understood. My point was/is; is there any device BUILT (not delivered) from 1/00 through 5/00 w/o the problem??

This would be S/N's from xxxxx0100nnnn through xxxxx21(or22)00nnnn

Mike

quote:

---

Originally posted by dequardo:
Thanks Theo. Good point and understood. My point was/is; is there any device BUILT (not delivered) from 1/00 through 5/00 w/o the problem??

This would be S/N's from xxxxx0100nnnn through xxxxx21(or22)00nnnn

Mike

---

That's correct. Yours was made in week 5x of 1999. NOT affected by problem.

Mike

Ok, so according to the above message, my Visor falls in the range of units affected by the problem:

S/N: xxxxx1600nnnn

Indicating week 16?

However... this Visor was just shipped to me direct from Handspring about a week ago, and when I ran the Visor Test on it, it did not show any problems. Nor did the Handspring Update program report the problem. So I'm guessing mine isn't affected. Why would they ship me a not-so-recently manufactured model?

[This message has been edited by linuxppcguy (edited 07-26-2000).]

Well that's correct. You received in July a model made in April. UNLESS they substituted and fixed the DRAM module for a new one on existing stock!?

Mike

Well that's correct though I can't answer the last question.

You received,in July, a model made in April. Either all the VDX stock was NOT affected OR they substituted and fixed the DRAM module for a new one on existing stock!?

Mike



[This message has been edited by dequardo (edited 07-26-2000).]

I would guess that Handspring is replacing the faulty chips with good ones at the factory. Why would they ship out bad units. That is a very poor way of doing business and I expect alot more from Handspring.
BEN

I got my replacement VDx in March or April. The middle 4 numbers of the serial number are 0300, and it doesn't have the DRAM problem via the test application.

[QUOTE]Originally posted by dequardo:
[B]UPDATE 7/26:

I take issue with HS's notice, to wit:
"Only a limited number of Visor Deluxe handhelds shipped between the period of January 2000 to June 2000 may be affected with this faulty chip."

Well, in fairness to Handspring, they merely represent that not all of the handhelds SHIPPED in that period are affected. They did not claim that not all handhelds built in that period are affected.

Hmm...confused. According to my serial number, mine must have been made in Week 4 of 1999. However, mine fails the DRAM test. Also, I didn't buy mine direct through Handspring, but off someone and got it almost a year after it was built if that is correct. AND looking at the press releases on the Handspring site, they released it around September 1999. Had they been hoarding them for months? That doesn't make sense either since they ran out so quickly. Explanation?

g'day :-)

Are you certain of the S/N? Is it perhaps week 40 vs 4?

Mike

Although I'm late on this thread I'm agreeing with a lot of the issues that desquardo brings up. The following leave me with a bitter taste in my mouth.
<UL TYPE=SQUARE>
<LI>1st: The test that comes with the update is a way of not admitting how big this problem may be. The test just seems to check your serial number and if it falls within a certain build date it just says "you may have a problem." It didn't tell me that I did or didn't have a memory problem just that I might.
<LI>2nd: I've registered with handspring and I didn't get an email from them about this problem? I've been thinking all along my Visor crahses, forcing a hard reset, all too frequently. This is painful when traveling and my desktop is not close by for a hotsync. I found out about the update only because I was looking for an answer to another question in this forum.
</UL>
My 2 cents, justin

My replacement Visor Deluxe also has the serial number xxxx0300nnnn (so built between January and May). However, it passed the DRAM test.