Skip to main content

Don't buy a Portege R830

Okay, so this is something of a rant, but given my experiences with the laptop, how can I not?

Backstory:  Corporate IT maintains a list of acceptable portables, all of which are made by Toshiba.  After looking over the list, it looked like the best choice was the Portege R830.  It had the best possible CPU and it wasn't a giant clunker that looked my back-in-the-day 15 pound Inspiron 7000.  As a bonus, it was available with a reasonably priced docking station.

My first conception that something was wrong when, after first boot, I checked free memory.  Physically, 4GB is installed, but windows says that only 2.7GB is available.  The Intel HD3000 video setup is eating the rest (1.3GB!).  Okay, no big deal.  I can reboot and change that in the BIOS.  Oops.  No option.  Well, maybe it's just some old drivers.  Nope.  Drivers are latest from Toshiba.  They're not particularly new, so maybe the generic Intel ones will fix it.  Damn!  Toshiba has crippled the video so that it won't accept the Intel drivers.

Maybe if I install more physical memory.  As an aside, IT installed the 32-bit version of Win7.  I know, I know.  But I've got duty travel coming up, and getting the laptop within 3 months was a major achievement as it is.  Asking for a wipe on day two isn't going to win me any friends.

So, I dropped 8GB into the computer on the assumption that the BIOS would be smart enough to leave the 4GB that Win7 _can_ address to me, and take the rest for video, even if it is overkill.  No dice:  The BIOS reserves nearly 6GB of the 8GB memory for video.  Really?  Really?!

A tech support request to Toshiba hasn't been answered.  I got the obligatory "We'll get back to you within 24 hours" email, but no actual email.

I wouldn't think that being able to specify video memory would be all that big of a deal, but then again, this BIOS is pretty braindead.  I think I've seen more options on locked-down Pentium 1 era computers.  I'm not expecting overclocking options, but at least let me use the damn thing, especially if IT has already f**ked things up by only installing half the memory I asked for and then installing the 32-bit version of Windows.


Popular posts from this blog

I guess Python isn't so bad after all...

Not wanting to hassle with learning OpenCV and fighting with an edit-compile-execute environment, I decided to use my OpenCV project as an excuse to play around with Python.

I'm still a serious beginner, but I'm beginning to understand why it gets the use it does.

Anyhow, it only took a couple of days to integrate Tesseract OCR, PIL, and OpenCV such that I could open multi-frame TIFF images, perform some basic feature detection, and then use the output of feature detection to focus on a specific region for OCR.

I will admit to having a few false starts.  The first was that I used an older (C++) tutorial that was using some deprecated features of OpenCV and ignoring some other features.  For example, the tutorial was using Hough Line detection to find squares on a printed page.  In order to get to that point there was thresholding, dilating, eroding, inversion, flood filling and so on.  Even then I wasn't getting the correct results.

When I started over, I was using the old…

Getting closer

Discovered that the "toucan" config is distinct from the "austin" config and so can dump a bunch of

Unfortunately it looks like I have to merge the Dell board config (board-qsd8x50_austin.c) with the latest generic board config from CodeAurora (board-qsd8x50.c).

Here's where I'm at so far:

corey@patches:~/msm$ git status # On branch gingerbread_rel # Changed but not updated: # (use "git add ..." to update what will be committed) # (use "git checkout -- ..." to discard changes in working directory) # # modified: arch/arm/mach-msm/Kconfig # modified: arch/arm/mach-msm/Makefile # modified: arch/arm/mach-msm/include/mach/board.h # modified: arch/arm/mach-msm/include/mach/camera.h # modified: drivers/input/keyboard/Kconfig # modified: drivers/input/keyboard/Makefile # modified: drivers/input/misc/Makefile # modified: drivers/input/touchscreen/Kconfig # modified: drivers/input/touchscreen/Makefile # modified: dr…

Initial Speech Recognition App

I'm pretty impressed with Microsoft's System.Speech API.  It took less than 3 days to throw together a proof-of-concept application.  The hardest part was probably coming up with the grammar -- documentation for that is pretty thin on the ground.

Anyways, here's the application source code on GitHub if anyone wants a look:
ObserverLengthSampler project

If nothing else, I'd recommend it as a starting point for someone needing a number recognition SRGS grammar in an XML format.