Windows 7 on 2+

[Ronc]

I installed the 90-day trial of Win 7 on the 2+ using the blank 64 GB SSD which was swapped with the original 120 GB HDD. I ran WU and got all the updates including the offered drivers (Atheros, Realtek, Intel Display) so that Wi-fi, ethernet, and the display work as well as they can w/o OQO Manager. I've been trying to use Win 7 Bluetooth (KB, Mouse, Headphones) when docked but it's been very frustrating, audio-wise. I guess the next step is to decide which Vista (or XP) drivers should be installed and in which order, followed by the OQO manager. Any advice would be appreciated. The desired functions are:

A convenient way to zoom-out the screen (in portable use) so I can use the mouse to reach those places unreachable in 800 x 480.

Use the dock's audio out jack and be able to switch from BT headphones to audio jack conveniently. (I sure miss the Vista/Toshiba BT setup and never thought I'd say that.) Also, the line-in function requires a special driver such as the IDT Vista driver.

Use the Gobi WWAN with Sprint (ideally with the Wireless Dashboard).

Although it would be nice if everything worked as in Vista, I'm not especially interested in touch, rotate, or zoom-in. Anyway, those are the main issues. Some minor points: It would be nice to get rid of the boot-up weed and the libraries.

[Ronc]

After using the 90-Day trial for nearly two years, and installing it on both 2+ OQOs, I'm ready to share my solutions.

Atheros, Realtek, Intel GMA500:

As mentioned above, I used Windows Update for the Atheros, Realtek, and Intel drivers. (I have noticed that Windows Update still offers the original Intel driver that I used in 2009, version 8.14.10.2011). This driver works ok with the OQO display and the dock's VGA connector. It usually does not interfere with the normal sleep/wake fucntionality of Windows, although on occasion after waking from sleep when transfering from the dock to portable use, the display has poor vertical resolution requiring a reboot to fix.

Bluetooth:

Windows 7 also provides a default Bluetooth stack, which I was unable or improve upon. (It still has an unresolved skype/headset issue: can't get BT headset/handsfree function to work, but stereo BT does.) What I have learned is that OQOs use a CSR chip which is compatible with the Microsoft and Toshiba Bluetooth Stacks but not with the Broadcom stack. The Microsoft stack supports these protocols natively: PAN, SPP, DUN, HID, HCRP and also vendor-supplied additional profiles which Windows calls "drivers". So for audio products Windows Update seeks out these CSR protocols/drivers: HFP, HSP, AVRCP, and A2DP. On my OQOs the Microsoft and Toshiba stacks were unable to provide functioning headset drivers/protocols and the Broadcom stacks won't install. Wikipedia provides a list of other stacks that I have not yet tried. [EDIT: I finally tried the Bluesoleil stack which doesn't work either.]

OQO Manager:

I have discovered that for zooming out the screen when needed it's hard to replace the OQOManager. Although the UMPC scroll bar is a useful addition, there are some windows that are just too big to fit and don't offer a scrolling option at all so it's either necessary to wait until you're docked or just install the OQOManager. An additional reason for installing the OQOManager is to obtain its "display sense" feature that switches the display to the external monitor when docked. (I've used this only with VGA since I don't have an HDMI monitor.) Another important feature of the OQOManager is the ability to set the fan to quiet. One of my 2+ OQOs had been in use for several months w/o the OQOManager and the fan always ran at high speed until it became extra noisy and soon failed completely. The fan/speaker housings are different from the Model 02's so they are hard to come by and may require soldering wires to replace. (I broke the motherboard connector trying to unplug the old fan so I wound up having to solder the new fan's wires.)

I installed the OQOManager version provided by OQO Software Engineer in the OQOTalk forum. However the OQOManager immediately creates two problems that it turns out can be easily fixed. The first problem is that with every reboot you are told several times "no touchscreen found" and the second is a compatibility problem with the OQO Wireless Dashboard and the Gobi WWAN such that the modem keeps turning off. The simple solution is to delete the two OQO "Plugins" called "touchscreen.oqo" and "wireless.oqo". (This removes the Wireless Dashboard, but if all the radios you need are not on, you can turn them on in the bios, or, if not visible because of an ill-advised BIOS or EC update, just restore the BIOS settings to default and they should come on.) After first installing the modem-related items (discussed below), I installed the OQOManager in compatibility mode for Vista SP2 but I'm not sure it's necessary to do that.

IDT Audio:

The Vista driver for IDT Audio is also needed in order to switch the audio jack between the input and output modes and to make the audio switch properly to the docking station jack. (Once again, I used compatibility mode on the installation file.)

Gobi:

I was able to get the Gobi WWAN to switch among the three US carriers (Sprint, Verizon, and AT&T) however Verizon won't work for internet access since none of the Gobi cdma ids (MEIDs) I tried is currently on their list of approved MEIDs. Fortunately, the same MEIDs are listed with Sprint which is preferred anyway due to its lower cost. But it would have been nice to be able to use Verizon as a short term pre-paid backup option as I can do with AT&T. Since AT&T authorizes the SIM card and not the modem, it does not have the problem of "approving" the modem. Note that when dealing with new modems on cdma carriers, they use MEIDs vs. the old style ESNs. When dealing with UMTS carriers the corresponding ID is the IMEI number. Both numbers are printed on the modem but only the IMEI is visible in Device Manager (when in UMTS mode). To view the MEID, you must use a cdma carrier's connection manager (like the Verizon Access Manager or the Sprint Smart View) when in cdma mode since Device Manager only shows the corresponding pseudo-ESN. As a final note regarding installations, I followed OQO's original installation order of Gobi drivers, carrier connection managers, and finally the OQOManager. In my case there were two Gobi driver files (Drivers and Images) and three carrier connection files (Sprint, Verizon, and Option for AT&T). The Option Manager also needs the phrase "isp.cingular" entered into its APN box.

Also, in regard to the Gobi modem, it's important to use a reliable procedure to switch between the two available carriers, AT&T and Sprint, especially since the newer Gobi drivers available through this website are not compatible with the OQO Settings' WWAN tab. That tab was intended to make it easier to switch the firmware among several carriers, whether cdma (Verizon or Sprint) or umts (North America or Europe). To accomplish this the 4 WWAN options on the tab change a number in an installed Gobi driver file called "options.txt" to 1, 3, 5, or 6. This method worked with the original Vista Gobi driver files but none of these 4 choices work for AT&T-US with the newer posted Gobi drivers. If one chooses UMTS-NA for AT&T-US the OQOManager sets the value to "5" which turns off the modem completely. The value required for AT&T-US is "0" or "2". So the simple and reliable procedure for changing carriers is to edit the options.txt file using Notepad (1=Verizon, 2=AT&T-US, 3=Sprint). Also, it's important to follow this edit by stopping and restarting the Qualcomm Gobi Download Service, shutting down the computer, removing the battery for a few seconds, reinstalling the battery, and booting up. (I kid you not!) After a while this procedure will become second nature to you just like heading for the "start" button to shut down the PC. It helps to have a desktop shortcut pointing to the folder containing the options.txt file (c:/Program Data/Qualcomm/QDLService) and to add to this folder both a text file describing the carrier switching procedure and a shortcut to "Services" for convenience.

GobiQuickNotes.txt

[ArchiMark]

Great info, Ron!

Especially, since I got my 'new OQO' yesterday, a 1.33GHz, 32GB SSD, no WWAN, touchscreen 2+.....

I have an external USB WWAN modem that I use once in a while, so, don't need it built-in, usually use WiFi or ethernet....

Debating whether to stick with XP or update it to Win7...been using Win7 almost entirely on other Windows devices the past year....

My understanding is that no one has gotten touchscreen working in Win7, correct?

Sounds like other than that and any issue you describe above, Win7 should work fine, right?

Thanks!

[Ronc]

...Sounds like other than that and any issue you describe above, Win7 should work fine, right?

I've never used XP on any computer. (Switched from Win 98 to my first OQO with Vista.) But since XP came out around 2001, it was designed to run "snappy" on the PC's of that era. That's why it's quite popular on OQOs which are underpowered compared to most Vista computers. So I would guess you may notice Windows 7 is less "snappy" on any computer compared to XP. Since many OQO forum posters seem to be happy with Windows 7 on a Model 02 it should perform even better on a 2+, except for the issues already discussed.

[ArchiMark]

I've never used XP on any computer. (Switched from Win 98 to my first OQO with Vista.) But since XP came out around 2001, it was designed to run "snappy" on the PC's of that era. That's why it's quite popular on OQOs which are underpowered compared to most Vista computers. So I would guess you may notice Windows 7 is less "snappy" on any computer compared to XP. Since many OQO forum posters seem to be happy with Windows 7 on a Model 02 it should perform even better on a 2+, except for the issues already discussed.

Thanks again for your input....

Well, took the plunge the other day and installed Win7HP...went very smoothly...as noted, everything works well, except touchscreen...would be great if it could work, but not that big of a deal either....overall, very pleased with Win7 on 2+.....



Now, I wonder whether to keep my 02 or not.....