Handspring Hides Flash ROM in Handspring Treo 193
miradu writes: "TreoCentral has just posted an intriguing article about how the Handspring Treo has Flash ROM - something that Handspring claims it doesn't. They've worked with Brayder Technology to create applications to utilize this newly discovered feature. It brings up the question, Why do developers lie about features in a device - especially if they are features that are wanted? Does anyone know any other examples?" Strange -- hardware manufacturers don't often underestimate their products' capabilities, do they?
That one is easy (Score:5, Informative)
Re:That one is easy (Score:1)
Re:That one is easy (Score:2, Funny)
Re:That one is easy (Score:2)
Also now that the information is out, that there are flashable treos available maybe Handspring better rethink their sales-strategy. If they now start producing treos without Flash-ROM a lot of folks will still try to get the flashable versions and pester salespeople about version numbers etc. and in general be dissatisfied with a treo that has this feature removed (and to them it makes no difference if Handspring anounced it as a feature or someone else).
Re:That one is easy (Score:3, Insightful)
Joel
Re:That one is easy (Score:2, Insightful)
I own a Handspring Visor Deluxe now, and I'm quite happy with the machine and with Handspring's service. But I need to upgrade for two reasons: I'm starting to see apps I want that won't run under my current OS, and I read enough on the machine that I want a color version. Were Handsprings flashable, it would be a no-brainer.
But I'm not only stuck with an out-of-date OS, I waste a lot of space with built-in apps I've long since replaced with better versions. So it's likely a Palm for me next time, and all over $5.
Re:That one is easy (Score:2)
But look at it from the company's point of view. On the whole, whether or not they have flash or ROM isn't going to change the sales figures. Sure, a few of us care and won't buy something without flash, but the vast majority of the PDA-buying market neither know nor care about the difference. Net loss, a fraction of a percent of their market share.
However, say the price difference between flash and a masked ROM is $5. (Not sure if this is accurate, but I know that masked ROM is cheap, cheap, CHEAP!) They're not likely to pass the savings onto the customer now, are they? The price is determined by the marketting department at what they think people will pay for the device, not what it costs to build. So the company will pocket the $5. Multiply that by the sale of 100,000 units, and you've made a cool half-million in extra profits. profits. Okay, let's say that 1% of your potential market is lost because they want flash. You've lost 1,000 sales. So your profit from using a masked ROM instead of a flash is only $495,000. Still sounds like using a masked ROM makes better sense.
Okay, so why does the Treo have an unadvertised flash? Could be that they're planning to remove the capability in the next rev. Maybe they were rushing this design to market and didn't have the lead-time to get a masked ROM made. Maybe it was easier to manufacture with a flash instead of an EPROM. Substitutions get made all the time, often because the purchasing department finds a better deal on something.
Case in point -- In a product I worked on, we had to add last-minute support for another manufacturer's flash because purchasing found a slightly better price from them. We had to add new drivers to the firmware, but that's a one-time engineering cost as opposed to a recurring cost on the bill of materials. Now we can manufacture the devices with whichever flash parts are cheapest. I can imagine the same argument holding true for using flash vs. ROM.
(Although one time this sort of cost reduction came back and bit the company in the butt. We released a product with "just enough" RAM, because going to the next larger size chips would have added $1/unit to the bill of materials. The very next firmware release, marketting told us that they wanted all sorts of new features that weren't possible with the amount of RAM in the product. Sorry, you lost.)
And do manufacturers understate the device's capabilities? You better believe it! We had two similar models. The actual advertised difference was that one had a high-quality long-life part, where the other had a cheaper shorter-life part instead. However, that wasn't enough product differentiation for the marketting team. They were afraid too many customers would buy the model with the cheaper part instead of the more expensive (and higher profit margin) model. So, they decided that the model with the cheaper part should run slower. The two units had the exact same CPU board, but we had to put in extra wait-states to slow down the code on the cheaper model. The two units even used the same code; we simply detected whether we found the cheap or expensive part, and programmed the memory wait-states appropriately.
The moral of the story is, companies will do anything they can to make a buck. And the minds of marketting folks are often incomprehensible to us engineers, and vice-versa.
Re:That one is easy - WRONG (Score:2, Insightful)
Re:That one is easy (Score:2, Informative)
(Experience from developing for handheld computers and cellphones is behind the above statement)
Re:That one is easy (Score:2)
And option B... (Score:3, Interesting)
This is like assuming that just because one PC has a paticular motherboard with paticular tweeks that every PC has that.
The Treo is still butt ugly mind.
Every single... (Score:2)
And in terms of butt ugly, sure it beats Palm but does it beat... http://www.symbian.com/news/2002/soneric-p800-2.h
Samsung i300 (Score:5, Informative)
Then FlashPro came out and proved that there was flash in the i300.
Upgrading the OS is still not an option, considering that there are lots of propreitary extensions to the OS.
However, the flash capabilities of the devices were hidden for quite a while.
Jake
long range vision (Score:5, Interesting)
Obviously, they can't be upgraded that way, so in their all knowing marketing minds, they're hoping users will continue to upgrade to newer products from Handspring.
Originally, they claimed that the lack of a flash ROM was a price saving measure, but I tend to think that in some cases, a flash rom would actually be cheaper.
Now that the treo has a flash rom, and they're lying about it, what do they expect? Of course users are going to make use of that 'hidden feature' now!
Handspring, you ought to 'embrace and extend' now that the gig's up.
Re:long range vision (Score:2)
They are lieing about it? Didn't the article cite Handsprings on Knolage Base as saying more or less "sure, we have FLASH now, on some devices, but we don't promise to keep using it".
I think that matches up with the truth.
It may not be a good idea, but that doesn't make it a lie! (it also may be a good idea, if very few people would use the flash, it might be better to make $5 more per unit by switching to MROM and lose some of the people who would have used the flash...of corse if it were my choice I would pay the extra $5 because I would rather patch the OS in ROM then have a RAM patch that a hard reset can take out)
Cost Of Goods drives this (Score:2)
Obviously, they can't be upgraded that way, so in their all knowing marketing minds, they're hoping users will continue to upgrade to newer products from Handspring.
I disagree. Handspring has always had aggressive pricing: for what you get, the price has always been very good.
(And recently they have insane low prices on Visor products... probably because sales took such a big hit after Donna Dubinsky said Handspring would be exiting the organizer market. People don't want to buy an orphan product, so Handspring slashed prices to keep sales moving. Ironically, the Treo 90 makes it clear that Handspring has not, after all, decided to exit the organizer market! But Visor devices with Springboard slots are never going to see any new models.)
I used to work for a manufacturing company. They were obsessed with Cost Of Goods. If a flash chip really costs $5 extra, it would totally make sense for Handspring to want to get rid of it. $5 additional cost of goods is probably worth $15 on the retail price; they can abosorb that now but down the road that's a lot.
I paid $300 for my first Visor Deluxe. You can now get one new for $120.
And, all that said, how many Handspring customers really care? I've never bothered to install an OS update on my Visor Deluxe; I haven't had any problems with it, so who needs it? Once the OS is stable, having it in ROM won't bother very many people.
I, personally, would cheerfully pay $20 or more for a flash chip on my PDA. However, I'm a geek, and most people wouldn't choose to pay that much. And it would cost too much to produce two versions of each PDA (the flash version and the cheaper ROM version) and let customers choose.
I wish they could put the ROM in a socket or something so it would be easy to swap in a flash chip. Alas that isn't going to happen on a tiny PDA device, even if it didn't add to cost and make the device potentially less reliable.
I don't have a problem with what Handspring has done. But I might try to buy one of the "early" model Handsprings now that I know about this.
steveha
All your conspiracy theories are belong to.. (Score:1, Funny)
Back on topic: obviously, they planned to release a newer model at a later date - "Now with flash rom!" - ye ol' upgrade path to hell.
Just another customer support de-feature I suspect (Score:3, Interesting)
Re:Just another customer support de-feature I susp (Score:1)
Support is the answer (Score:2, Interesting)
Re:Support is the answer (Score:2, Interesting)
If it had been widely advertised support would have been a nightmare but they could have probably sold more disk space. But the bottom line was that people understand POP and they don't understand IMAP.
Yet Another Opinion (Score:1)
If it was *designed* to be hacked with (*cough cough xbox cough*), then yes, Flash ROM would be a selling point. But it wasn't....
BTW, for a while, I thought the story was about a kerfuffle between Macromedia and the PDA people. =)
Engines and CPUs (Score:1)
Re:Engines and CPUs (Score:1, Offtopic)
although this is caused by the japanese government placing a hp cap at 276hp, because you would never need more than that, ahem 640k, ahem, aahem. but the japanese gov. trusts the automakers and does no actual testing so twin turbo Supras would roll off the line pushing like 350-400hp.
possible reason (limited run or not) (Score:1, Interesting)
Why? Support (Score:5, Interesting)
Re:Why? Support (Score:1, Redundant)
Classic Example....from Apple (Score:2, Interesting)
Re:Classic Example....from Apple (Score:1)
Re:Classic Example....from Apple (Score:2)
Can you substantiate the charge about Griffin Technologies? It is interesting to read their press release [griffintechnology.com] for a product that they clearly don't ship. What makes you certain that this was withdrawn due to pressure from Apple and not due to a more innocent reason?
Re:Classic Example....from Apple (Score:2)
Re: almost, but not quite (Score:1)
The Voodoo2 card (not Voodoo Banshee) was made by MicroConversions and publicized as much as they could, so Apple "getting wind of it" is a somewhat misleading characterization - this was a product (the iMac GameWizard) sold openly and advertised, not some secretive hack like a blue box that was sold on the QT. Apple didn't kill the product (though they did remove the "mezzanine" slot from iMacs sold from January '99 on); MicroConversions went out of business for a number of reasons (customers sort of rebelled against the company for its high prices and unsatisfactory driver support). IIRC, another company bought up unsold iMac GameWizard inventory and continued to distribute them; I believe they even announced intentions to continue manufacturing them, although I'm not sure whether these plans ever went through. The market for them (gamers with early iMacs) is finite and fairly small, so I wouldn't expect the cards to continue to be manufactured forever anyway.
Re:Classic Example....from Apple (Score:2, Interesting)
Viruses, trojan horses? (Score:1)
I think its not supported by palmOS. (Score:1)
Re:I think its not supported by palmOS. (Score:1)
Read the Article (Score:1)
They probably mananged to get themselves a better deal from the flash rom people so they sticked flash instead.
Another explanation would be that features such as 3G and email alert requires space off the ROM instead of your memory.
Don't get too exicted just yet since non of the PalmOS devices today are OS5 capble, the flash rom is for extra storage for now, before Handspring've decided to use them all for patches and additional features etc.
VW does this with their cars (Score:4, Interesting)
Take a look at the cars with the 1.8 Turbo engine.
By changing the ECU programming, they can add power by adjusting boost pressure, air/fuel/spark maps...
The car can magically gain 10-20hp between model years, all with the click of a mouse.
Aftermarket ECU tuners can get the same results out of the cars that are just a few years older.
But, "15 more HP than last year" is a great selling point for a car.
Re:VW does this with their cars (Score:2, Interesting)
The original 150hp models can be easily and safely modded to 170-180 hp, while the new 170/180 hp models (depending on which car it comes in) can be fairly easily modded to 200-220hp via a new ECU.
The first VW 1.8t (150hp in the Passat ~1998) was rougly the same engine as the 170hp 1.8t in the A4... no sense in having a premium car brand if you don't distinguish it in numerous ways.
Re:VW does this with their cars (Score:2)
I used to drive a 90bhp VW Golf TDI model '97, when there was a 110bhp available as well. It wasn't just the electronics set lower, it was also some parts in the engine that had a higher quality, for example tubes that can sustain more pressure.
Take the latest S3 model from Audi, for example. At 210bhp, it has a 1.8T just as the Audi A3 @ 180bhp has. It's not only the electronics that have been finetuned, as I read somewhere in an advertisement for chiptuning that can bump up the 210bhp to about 235bhp.
And here's another reason:
Car manufacturers make cars for a wide market, especially European car manufacturers. Fuel is not the same quality in all countries as standards are set differently, and they just need to make sure that the car performs almost the same in all countries.
Dave
And then amazingly in 2 years your engine fails! (Score:4, Insightful)
No, they spec the engines out based on a number of factors relating to emissions, fuel economy and reliability. So by tweaking you adjust the compromise. Automakers do refine engines over time to gain more power, but they try do so in ways that don't effect it negatively. By that I mean, decreasing reliability or not allowing the car to meet US regulations regarding emissions and fuel economy.
Re:And then amazingly in 2 years your engine fails (Score:4, Interesting)
>advertise their engine as having only 140 hp if
>with a small software change they could get 160
>hp? I mean come on.
Single brand (Porsche, BMW) companies usually don't - but those who have luxury brands and ordinary brands (Toyota, Honda, VW, Nissan, Ford, GM...) do. They want to share parts to reduce cost, but have to intentionally downtune the cheaper brands to prevent it from competing with its own luxury brands.
Re:And then amazingly in 2 years your engine fails (Score:1)
Re:And then amazingly in 2 years your engine fails (Score:2)
Sometimes they just understate the advertising (Score:2)
Re:VW does this with their cars (Score:1)
That's funny, I don't recall my insurance agency mentioning any restrictions that my car had to be in "stock" condition in order to retain insurance. Although I imagine that if I introduced a problem that resulted in an accident, they'd be happy to not pay any proceeds.
Playing the numbers (Score:2)
Personally though I've never seen the need to use the built-in flash RAM on my TRGpro, since I have a (*gloat*) 128MB CF card.
Programming Flash (Score:1)
My favorite quote (Score:5, Funny)
I ask all these rhetorical questions for a reason: I want to know what you think.
er... you keep using that word. I do not think it means what you think it means.
Re:My favorite quote (Score:1, Informative)
The educational system in America sucks balls.
Re:My favorite quote (Score:1)
I send you this rhetoric in order to have your advice.
Its the history (Score:2, Interesting)
Now, what happens when they reverse their position?
Re:Its the history (Score:1)
If they had Flash ROM in the Visor and the OS could be upgraded then a good chunk of the people would screw it up - the Visor is not a venerable machine. If people screw it up then they will call in and then Visor is on the phone forever with the average end user talking them through flashing the ROM, upgrading the OS, rolling back to the previous version or - worst case scenario - being liable for the data they lose. Handspring doesn't want this so they don't make the ROM flashable and they end it right there. The amount of money they save in potential support gets passed to the consumer.
Plus the Visor was something of a "first step" system - most people want to upgrade to a new hardware unit eventually.
in response to your question (Score:2)
ALWAYS. Ever hear of overclocking?
And not just computer hardware, but pretty much anything built is tested PAST the point that it's good for.
If your car's guages tell you it redlines at 6500 rpm, it probably really redlines at 7000. If an elevator says "20 People Max" it really means 30 or 40. etc.
Re:in response to your question (Score:2)
The specifications manufacturers provide are generally that capacity at which they gaurantee their product to perform. Sure, some product samples may perform beyond those specs, but then others may fail immediatly after they are exceeded. Just because of variations in manufacturing.
Re:in response to your question (Score:1)
It's standard engineering practice to leave a margin of error for safety reasons for things like cars, bridges, elevators etc.
Re:in response to your question (Score:1)
I was always under the impression that elevators were designated this way to account for... um... caloricly challenged people. I would feel much better about getting on an elevator with 20 super models than getting on one with 20 people leaving an overeaters anonymous meeting (ignoring the obvious issue of overlap between these two groups).
Re:in response to your question (Score:1)
Palm OS licensing issue perhaps? (Score:4, Interesting)
Some Earlier Examples (Score:5, Interesting)
It's common for the aspirations of engineers to be lobotomized a little by the larger marketting beast. I've read several articles on the web where a Celeron motherboard could be greatly sped up by placing celophane tape over a single pin of the Celeron's card edge connector. But then we stray into the area of overclockers...
THE EARLIEST EXAMPLE that springs to mind is on Radio Shack's TRS-80 Color Computers. There was some story about doubling the RAM by bending two pins on a socketted IC chip. The story was that the onboard capacity was crippled for the sake of easy in-store upgrades.
Re:Some Earlier Examples (Score:4, Informative)
Mainframes would ship with various disabled features. Remember these were room-size devices (well, multiple large cabinets which would fill up a big room). When the customer wanted an upgrade, an IBM technician would be sent out, he would rearrange some jumpers, enabling a feature, and the customer would receive a bill for e.g. $100,000 for a memory upgrade.
IBM made no apology for this: you were charged for the functionality you received, and the fact that the "upgrades" already existed inside the boxes in your computer room was irrelevant.
So perhaps one can blame IBM for having started the ball rolling on the idea of strong control of "intellectual property" by the vendor... I wonder if anyone back then "hacked" their own mainframes?
Re:Some Earlier Examples (Score:2, Informative)
Re:Some Earlier Examples (Score:2)
Er, "their own mainframes"? Surely you know IBM did not sell mainframes for an extreamly long time, just rent them. Sure it was in your machine room. You had to supply power and cooling, and your own experts to run it...but IBM still owned the machine.
I don't know exactly then the practice stopped (I'm not old enough to have gotten in on more then the tail end of the mainframe's era of supremicy...and Amdahl had been around for a while by the time I knew anything!). I'm guessing very late 70s, but more likely the early 80s.
By the way, I think Sun is currently doing this with their high end machines now. Of corse they advertise it. Interesting policy.
Re:Some Earlier Examples (Score:2)
I have also heard -- from less reputable sources -- that Linux/Sparc will use all of the CPUs on an E10K, regardless of what you've paid for.
Re:Some Earlier Examples (Score:2, Informative)
Hmm. If this is what I think you're referring to, that's not quite true. (You may be referring to soemthing I hadn't heard about, of course.)
What Tandy did do with the early CoCo 2 series was to take 64K memory chips that had tested with one or two bad bits, grab a set of them that were all bad in the same half of memory, then sell the result as a cheap 32K machine. Because of the way the Microsoft BASIC ROMs were mapped into memory, you couldn't use more than 32K of RAM under BASIC anyway.
Side note: because of the way dynamic RAM is arranged with row and column addresses, DRAM chips will always have an even number of address bits. So nobody ever made 32K chips (which would require 15 address bits).
Soon enough 64K chips became dirt cheap anyway, so there was no point in using bad ones; it was still cheaper to use 64K chips than twice as many 16K ones for a 32K computer. And besides, the CoCo 2 motherboard didn't have enough memory sockets to use 16K chips. The 'extra' 32K was only useful if you were running something like Flex09 or OS-9; OS-9 being a real-time multi-tasking operating system written for the 6809 processor, and available for the CoCo back in the early to mid eighties.
So it wasn't a matter of 'easy in-store upgrades'; it was a matter of it being a lot cheaper to build that way.
-- Bryan Feir
Re:Some Earlier Examples - 486 SX/DX (Score:2)
I believe this is still going on with processor speed. They don't set out to make several different speeds of CPU, but rather make the CPU as best they can and sort them out by how fast they can be clocked after the fact.
Everything I know on the issue (Score:1)
There is no space for user apps on the rom by default, the OS takes up all 4MB, but you can delete the foreign language apps to free up space
The rom is a toshiba type
There is 2MB (maybe 3MB, I forget) of flash on the mobile radio too.
Handspring have always admitted to having a flash rom, but do not support any utility which modifies it, the article is in one of their knowledge-base pages.
There probably won't be any major Palm OS upgrades in the foreseeable future, and almost certainly not for the Treo. Palm OS 5 won't run on it.
Now! With! Flash ROM! (Score:1)
Same product, new label; and since they never promised that the old one has a Flash Rom you can't feel cheated when you open the box of your new handspring, only to find it eerily similar to the one you already had.
GPRS upgrade (Score:2)
Answers on post card
Yes the Visors don't have flash ROM's but the treos have. That;s one of the nice things about them.
Re:GPRS upgrade (Score:2)
Hardly unheard off (Score:3, Interesting)
Why do developers lie? (Score:4, Insightful)
The developers of the hardware usually aren't the ones who are lying. I work for a fairly large company [ti.com] and I can safely tell you that the engineers (that's me) don't sit around and plot to hide features. The way it usally goes down is that some guy in marketing gets a hold of technical documentation that is being developed along with the product. Once he gets it, he gives us a call and starts asking if feature so and so should really be documented. One thing is for certain though, marketing seems to get the final say as to what gets published and what doesn't.
The corperate benifit of some of this stuff is fairly easy to see. For instance, say we make a chip called the Wizbang 3900. Now, this chip is going to be released in the 3901, 3903 and 3909 flavors each with different features. Since a run through the fab can cost upwards of $500k, it is much easier to just make one version, then just label them differently. The same thing is true with the development boards. A lot of times the board is only populated with the parts to allow that feature set. By populating more/different parts of the board, different features can be achived with out requiring a different board spin. All of this saves money and development costs, but does lead to some documentation holes.
So in short, blame it not marketing not the engineers. We're the good guys.
Re:Why do developers lie? (Score:3, Informative)
The developers of the hardware usually aren't the ones who are lying.
Agreed! I've seen that happen more than a few times. Thought it might be useful to add another possible reason why some features are hidden.
My expertise is with software (20+ years in QA), not hardware, but I've seen the hiding of features happen several times. In my experience, the develpment cycle starts off with marketing making its pitch for what needs to be in the product release, and development pushes back with what is feasible in the time frame, as well as what they would like to do. There's some negotiation, and then development goes off to "do their thing". And all is happy and good.
Then QA appears and does its thing. Sometimes QA is called in right from the start; other times the product is almost ready for release and someone thinks it might be good to have QA look at it before it is shipped tomorrow. I actually have seen a few projects released on time, under budget, and with the promised capabilities. But, that is sadly the exception rather than the rule. Even with an early participation by QA, there are often far more developers at work than QA people. The number of possibilities goes up exponentially, and there's just not enough time to test everything as it is developed. Design errors and implementation errors are found. Rework is required. Deadlines loom. All is not as happy and good as it once seemed. And then it happens.
Maybe it's a nasty memory leak that builds up over time. Maybe there's a variable that gets corrupted, eventually. And there's not enough time to isolate it and fix it. So, instead of yanking out all the questionable code (which would introduce its own bevy of problems), the common approach is to just remove access to it (e.g. removing a choice from a pull-down menu) and, of course, removing all reference to it in the documentation.
So, there's quite possibly some hidden functionality in a program (or a piece of hardware), but it was hidden for a reason. If you're a bleeding-edge kind of person, go have fun. In light of your particular circumstances, it might well seem to work okay. But, if you need to be able to rely on the application or system, it might be a Really Good Idea(TM) to use only the documented features. You might miss out on some helpful features, but you might also save your butt.
Re:Why do developers lie? (Score:3, Funny)
Darn! You mean I shouldn't be using the hidden "overclocking" option I found on my pacemaker? But I feel so alive with my heart going at a steady 180bpm all the time!
Remember the USR Sportster Incident? (Score:2)
Do hardware manufacturers understate the capabilties of their products? I guess the answer is "All the time, man. All the time."
First of all... (Score:2)
But anyway, they probably lie for the same reasons that Microsoft disabled OS calls necessary for a bootloader to function.
***They don't want you to boot PalmOS, or WinCE, or whatever off the device and install something else.***
I'm not into MSoft bashing, but even I can't deny this one. They did it, plain and simple. And now it appears that Handspring may be using similar tactics.
I know it sucks for those of us who like to install alternative OS's on our PDAs, but on the other hand, I can also understand why it doesn't really fit into their business model.
Just think of it as Ford welding their cars' engines in place, so you couldn't easily swap the engine for a different one.
If you want to easily use an alternative OS on your PDA, here's the best options in no particular order, IMO:
Ipaq
Zaurus
Agenda VR-3
Old WinCE device and NetBSD
THere are probably others, but it's too early to think.
Re:First of all... (Score:1)
> ***They don't want you to boot PalmOS, or WinCE, or whatever off the device and install something else.***
I really doubt it's Handspring being a big meanie and not letting you use the unit any way you wish. It's almost certainly a contractual constraint in their license of Palm's OS.
To identify the bad guys, look to the OS manufacturer.
Re:First of all... (Score:2)
I've never owned a Handspring or Palm, so I can't comment. I was just going by prior experience.
Treo 300.. (Score:1)
Another example: DEC's microVAX (Score:1, Interesting)
duh (Score:2)
Because when they leak it, it will get press (Score:1)
Why developers lie. (Score:2)
If it's not there, I don't have to support it... (Score:2, Informative)
Support is one of the most costly items in a products lifecycle. I remember a statistic (I can't quote the source) that 50% of the cost of software is in the support and maintainance of it after release. I would venture that Handspring has looked at what it would take to support this feature and decided that there is not enough margin in the product to support it even if the capability is provided in the hardware.
A final thought, they may have discovered some sort of performance or reliability problem with the flash ROM and instead of correcting the problem (potentially quite costly), they removed the feature so they did not have to support it.
-tpg.
Old Fogey's (Score:1, Informative)
the 4014 Storage Tube Terminal. To convert it
to a 4015 you paid some big bucks to Techtronics
and a technician came out and clipped a couple
of wires to enable the additional features.
TI's TI-58/59 calculators had undocumented
instructions that were useful in getting
programs smaller (Direct access to processor
stack). (1977?)
Undocumented/Denied features have been going
on for years. Why be surprised ?
"Does anyone know any other examples?" (Score:1)
Hopefully, they'll make this memory usable in a future OS version, but I kinda doubt it.
The original iMac is an example (Score:1)
Apple didn't exactly deny the slot was there, but they weren't too excited to show it off (it's not in the iMac Rev. A's specs page [apple.com]) -- they made a pretty concerted effort to make sure people knew the slot wasn't supported. Wasn't long until the motherboard was changed and the slot was gone completely. Funny to think they were probably only saving a few cents to take the soldered slot off the mobo for Rev. B, but 2 times a million iMacs starts to add up!
Flash! ahhhahhhh saviour of the universe (Score:1)
Maybe this was entirely intentional (Score:2)
If users install applications into this flash space, Handspring can't upgrade or patch the OS using this flash space. Now the number of support calls quintuple, because users flashed applications into this space (violating their warantee, I might add).
I see nothing at all wrong with what they've done, and it happens all the time in electronics.
Maybe true from a certion point of view (Score:2)
PalmOs provides some support for flash rom and no doupt the Handspring units lack that support.
There are some good reasons for not announcing this fact.
I've noticed on my Handspring Visor while I have 2 meg memory it's actually 2 meg total memory.. including the rom. This could be Handspring goofing around and giving less ram to cut costs. But I doupt they could easly do that.
More likely the rom was copied to ram. This is a trick to speed things up a tad done on some PCs.
If Handspring dose this will ALL the devices they sell then the flashrom would automaticly be cut off when it wasn't needed anymore.
It makes sense to me. Handspring provides software updates from defects in PalmOs on older visors. Yet they don't have flash. This suggests to me that the patch is being done in ram and not to the rom itself.
This also suggests that if you hard reset the unit your patch is vaperised. A good thing when you think about it... Viruses? Yeah you remember those. Palm isn't evil like Microsoft but they aren't totally benine. Just as evil as Kelloggs.. (Or do you believe coco puffs are actually a healthy breakfast? I don't.. Never did.. not even as a kid.. Good to expose kids to obveous marketting lies)
So basicly yeah it may be there but just not supported enough to tell the costummer.
The'd expect it to be supported in the usual ways and when it's not they'd be pritty angry.
Re:Because in this case (Score:2, Informative)
Re:Because in this case (Score:1)
Re:Because in this case (Score:1)
And you got +2?
Tom
Re:Because in this case (Score:2)
Re:Because in this case (Score:2)
There are memory chips that are reset by exposing them to light.
Taken from here [netrino.com].
An EPROM (erasable-and-programmable ROM) is programmed in exactly the same manner as a PROM. However, EPROMs can be erased and reprogrammed repeatedly. To erase an EPROM, you simply expose the device to a strong source of ultraviolet light. (A window in the top of the device allows the light to reach the silicon.) By doing this, you essentially reset the entire chip to its initial-unprogrammed-state. Though more expensive than PROMs, their ability to be reprogrammed makes EPROMs an essential part of the software development and testing process.
Re:Because in this case (Score:1)
Re:Because in this case (Score:2, Flamebait)
Every time I see something like this, modded up as if it were fact, I want to cry. Go ahead, mod me down as troll or flamebait, but it's the goddammed truth. PhysicsGenius is anything but.
I believe that, in some trollish way, he refers to the old UV erasable EPROMs that are hardly ever used today. Hello, Brainiac, not only do those always have a sticker over the window to prevent accidental erasure, but they would be inside the case. That's right, aside from the stray 1 in 1 trillionth photon that tunnels through a quarter inch of plastic, any EPROMs would be safe.
If only it were an EPROM, that is. Flashrom is electrically erasable, no light of any wavelength is involved. Nothing short of long-term high dose gamma rays is likely to have any effect whatsoever.
Please, please, if you see this in m2, kick the ass of the moderator that gave this "interesting".
Re:Because in this case (Score:1)
A photoflash does contain a lot of UV though.
You could also (Score:2)
You could also keep it under your tinfoil hat - that should protect it.
"Thin sheet of plastic" protects it? More so than the thick sheet of plastic that the case is composed of?
"Dr. Helmut Pottman?" Surely he's published his "recent study" on the web somewhere? Show me the link - German's ok, I can read that...
C'mon... You can troll better than this! (Though you might want to send your post to ZDNet - they might fall for it...)
Re:Because in this case (Score:2)