I’m working on my DNS 323 to update everything so Debian will take over all control. This includes upgrading Samba. Now installing Samba using the apt-get call to the Debian package library proved unsuccessful, not that it didn’t install it just didn’t run afterwards. The package in the Debian repository is a bit behind in revisions so I figured I’d grab the source from the Samba SVN and compile it. Well after like an hour of compiling it errors out (bah!) with an error basically indicating it can’t find the main() function in one of the script files. Guess it’ll be a work in progress for now.

Previous ArticleNext Article
T.

Toshiba M200 and Dual Displays

Like me, most of you who have the infamous Toshiba M200 tablet have probably upgraded that outdated XP installation to either Windows Vista or Windows 7. And you probably upgraded the video drivers from the old 64 Forceware to the 97 or 98 Forceware off of LaptopVideo2Go. But you’ve probably also noticed a few things in regards to the display no longer work, such as Dual Displays. Fortunately there’s a solution for enabling Dual Displays in the BIOS.

Reboot your computer and hold down the ESC key before the TOSHIBA logo appears. The laptop will prompt you with an error message “Check system. Then press [F1] key.”  Press the F1 key. Once in the BIOS setup, navigate using the directional keys to get all the way over to the right side where it says Power On Display in the DISPLAY box. Press the Space key until it changes to LCD+Analog RGB. Press the End key followed by the Y key to save your changes.

And that’s it! You can now plug in your monitor to the VGA output of the tablet and enable dual displays in Windows using the mobility center. I was actually quite surprised when I could run my main monitor at 1920×1080 and the laptop LCD at 1400×1050 with out any issues.

T.

Toshiba M200 + Vista Aero = Awesome

So I’ve done the pain staking (very worth it) process of installing Vista on my epic Toshiba M200 Tablet but for the longest time I couldn’t use Aero. Now as my last statement suggests, yes I found a way to run Aero… semi stable (see the list of things that I’ve noticed crash Aero).

To do so I needed:

So first up, I uninstalled my current drivers using the Control Panel, restarted and then ran Nasty File Remover (see below for how I had mine setup)

as you can tell, Aero is running... taken after I did this
as you can tell, Aero is running... taken after I did this

After I did that I downloaded and extracted the nVIDIA ForceWare 98.16 drivers from above to my desktop and copied the modded nvgm.inf to the folder (had to overwrite the existing one). Once it was copied I ran the setup.exe in the folder and restarted my computer. Once my computer was back up and running I started the Desktop Window Manager Session Manager in the Windows Services and applied the Aero effect in the Window Color and Appearance option in Personalize.

I decided to run a Windows Experience Index test to see how my stats improved and I was quite pleased, Gaming Graphics went from 1.0 to 2.3 although Graphics stayed at 1.0.

Windows Experience Index

Things I’ve noticed that crash Aero:

  • Opening some programs in full screen
  • Opening Windows Media Player
  • Opening Paint (yes… mspaint)
  • Going to My Pictures (probably due to thumbnails)

I’ve noticed it flickers sometimes on and off when opening some things, but if it ever crashes I can minimize all my windows then go into the Windows Services and restart the Desktop Window Manager Session Manager. To help improve its stability I went to the Performace under Advanced system settings and toggled Adjust for best performance then checked off Use visual styles on windows and buttons. I had to minimize all my windows and restart the Desktop Window Manager Session Manager to get Aero back but it’s now running fairly well.

Here’s a screenshot of Aero Glass running at 1400 x 1050 @ 32bit color on the Toshiba M200

M200 Aero Demo

As a side note, one may ask why I’m not using the latest 179.xx Forceware drivers and well the answer to that is simple: they don’t work (I tried them). What I may try next are the ~100.xx  Forceware drivers to see if they can add more stability, but for now I’m pleasde with what I have at the moment.