Great news about Windows CE 4.0

[Matt Keys]

Chuck watch your mouth, what may be appropriate for some people(you) may not be for others. You are starting to get out of hand. <br><br>Also, If my memory serves me correctly back in my E-100 days Casio offered an upgrade to the PocketPC operating system for 150, or it might have even been 200 dollars. Anyways it was a rip.   <br>Last modification: Matt Keys - 04/13/01 at 07:13:37

[Chris Edwards]

Dan, I don't know if you did this on purpose, but I thought it was pretty funny .<br><br>"I still have Windows CE 1.0 devices. They are slow (33 mhz), have a 4 greyscale screen, 4 MB RAM, and...."<br><br>That sort of reminds me of a Palm. <br>

[SonicSilicon]

[Moose or Chuck]

[Dan East]

Casio could easily make the ROM upgradable, even if it requires a physical modification. That CE 1.0 device I was talking about (an HP 320) has a little panel in the front that pops off. You can pop it off and remove a small circuit board containing the ROM. Actually, I did upgrade the 320 from Windows CE 1.0 to 2.0 (HP released a free ROM upgrade in early 1998 ). I guess Casio just goofed by not making the ROM that accessable. Compaq has done a similar thing with the iPaq's battery. The device would have to be sent in to replace the battery.<br><br>I studied as little as possible! If it wasn't directly related to CS I avoided it at all costs. Even the Computer Science courses I took benefit me very, very seldom these days. Actually, linked lists are about the only thing I can think of that I was actually taught at college that I use today. I taught myself C and C++ (we spent a couple days covering C++ in "Survey of Programming languages", but that was mainly discussing OOP - Object Oriented Programming - and the C++ Class). Okay, we covered socket (TCP/IP) programming in a class too.<br>Looking back, the single greatest thing that helped me was working for YSU as a grader. I graded Pascal programming assignments. Basically I would build the student's project and see if it behaved per the assignment's requirements. Next came the part that helped me, which was critiquing their source code. Seeing how dozens of people went about solving particular coding problems was very helpful. In the vast majority of the cases they went about their coding poorly, using only the handful of pieces of the Pascal language that they knew. But on occasion I would see something and realize "that was a cool, optimum way to implement that". So I would try integrate that into my coding technique.<br>Things have changed greatly since then (it's been 5 years since I was at YSU). Then we programmed Pascal and Assembly on an IBM Mainframe, C and C++ on Sun Unix workstations, and some C++ (and VB) on Windows PCs. Today I'm sure much more time is spent in Windows specific programming.<br>I'm going to make myself stop typing now.<br><br>Dan East<br><br>Last modification: Dan East - 04/13/01 at 18:21:12

[Creacher]

Hmmm...<br><br>what id like to know is if u can download an upgrade...<br><br>cause i hate being outdated<br><br>i juss traded in my jornada today for a Ipaq... time to play some Quake!

[Dan East]

Yes, Compaq has already made available ROM upgrades which are downloadable.<br><br>Dan East

[Jason S.]

Great.  So let me get this straight.  Whistler MS's next OS won't support Bluetooth but their next OS for the Pocket PC will.  [sigh]<br>The hell with the hand not knowing what the foot is doing.  I think the foot has wonder off into the forest and has gotten lost. Geesh.  Once again MS leads us into a brave new world of confusion.<br><br>How much you want to bet the Pocket PC team in Redmond were on their hands and knees begging the Whistler team not to nix Bluetooth.<br><br>Please imagine this.  Your iPaq 2 has a Bluetooth module in it.  Your PC has a Bluetooth basestation on it.  Activesync 4 supports Bluetooth syncing and whenever you come into range of your PC it automatically syncs.  Nice pipe dream.  Might have actually happened if not for Whistler.  Here's hoping for 3rd party drivers<br>

[Moose or Chuck]

sorry, the language is natural i can't stop it, but i'lll try to tone it down.  Also the reason they discontinued the Rom upgrades is because in some systems it would work, but in other for no explainable system it wouldn't. I'm claiming user error but thats just my opinion.

[Moose or Chuck]

That was the iPaq ROM upgrade, not the chip that Casio would send you that you had to install.

[Moose or Chuck]

NO i'm talking about the Casio rom CHIP upgrade. I saw an article about it at bluetooth, o heres the link

[Moose or Chuck]

----------------------------------------------<br>I spoke with sources at Casio on several ocassions during that time period and never walked away with a clear understanding of the specific issue that prevented the E-100 and E-105 from being upgraded. From what I gathered in those conversations, Casio had indeed produced some Pocket PC ROM chips for the devices. However, they quickly discovered that they worked in some units and not in others. The reason? It seemed that subtle changes within the device had been introduced during 1999. Casio was hesitant to discuss the specifics of the problem, so as not to blame anyone. It never became clear whether this situation was caused by the processor manufacturer (NEC), the operating system developer (Microsoft), or the device manufacturer (Casio).<br>----------------------------------------------<br>straight from the article.

[Dan East]

I guess I'm a little bit confused. Bluetooth is basically a network card (or it can be directly built into the device). Um, aren't there these neat little things called drivers that allow the OS to access hardware? If an OEM wanted to include bluetooth onboard the device, or if someone wanted to release Pocket PC drivers for a CF / PCMCIA bluetooth card, then what's that got to do with Windows CE x.x?<br><br>Dan East

[Moose or Chuck]

He meant Brighthand not Bluetooth.

[Moose or Chuck]

too many b letter things in my vocab now they are all gettin mixed up. bluetooth, brighthand, wince 4.0 utter bullcrap.