Archive for May 20th, 2011
In order to ignore a Windows XP update, you have to make sure Automatic Updates is NOT set to Automatic. Rather, set it to one of the following two settings (in Control Panel > Automatic Updates):
- Download updates for me, but let me choose when to install them.
- Notify me but don’t automatically download or install them.
Windows will, upon finding updates, prompt you that updates are available but will not install them. This will give you a chance to ignore your selected update. If you want to force Windows to check for updates immediately, open a command prompt and type:
Next, once the update is available and you’re prompted to begin the installation, select Advanced. This will show your list of potential updates in a checkbox-list format.
Uncheck the update you do not want to install and click Next.
You will then be prompted if you want to ignore the update. Confirm.
Questions, comments, and feedback are welcome.
Windows XP is not officially supported by Toshiba, and they offer very limited software downloads. This guide will attempt to give you the best installation instructions and driver download locations that apply to this model. Also, you may find the detailed spec sheet handy when looking for drivers.
Before installing Windows XP, go into the BIOS and change the SATA Operation mode to “Compatibility.” Read why here.
Insert your Windows XP disc. Immediately after powering on the system, tap F12 repeatedly to enter the boot device selection menu. Manually pick “boot from cd/dvd drive” and follow the on-screen directions.
The following attempts to list the device IDs and driver download locations for Windows XP drivers. You may want to check your device IDs to verify same hardware.
Required Windows Components
The following Windows components are required for some drivers to successfully install:
- Windows Imaging Component
- Windows Installer 3.1 Redistributable (v2)
- Microsoft .NET Framework 4 (Standalone Installer)
Ethernet (10ec:8136) – Realtek PCIe FE Family Controller
WinXP, Win2K, Win2003 Auto Installation Program (SID:1453654) [link]
Wireless (Unknown Device ID) – Realtek RTL8187SE
Windows driver auto installation program [link] may or may not work.
This is the device that’s installed according to the spec sheet. However, several of these have the below Atheros chipset device.
Wireless (168c:001c) – Atheros Communications AR5BXB63 (AR5006X) /
WLL3141 (Toshiba PA3613U-1MPC) 802.11bg Wireless Adapter
Driver is here [link], but you will have to use the inf installation method, as there is no exe. Point to the netathwx.inf file in the download.
Video Controller (8086:2A43) and (8086:2A42) – Intel Graphics 4500M
Intel Graphics 4500M [link]
PCI data aquisition + signal processing controller (8086:2932) – 82801I (ICH9 Family) Thermal Subsystem
Seems to be satisfied by installing this driver [link] – Feedback is appreciated.
Sound (8086:293E) – Intel Corporation 82801I (ICH9 Family) HD Audio Controller
Intel® HD Audio Controller – Realtek [link] (partially working – reportedly needs SMbus driver to work)
SM Bus controller (8086:2930) – 82801I (ICH9 Family) SMBus Controller
Satisfied by [link] Note: It seems after running this driver (even though it uninstalled the above Intel HD Audio driver) then running the Intel Driver Update Utility (below) appears to completely satisfy audio drivers.
Modem (11C1:1040) – Modem device on High Definition Audio Bus / Agere Systems HDA Modem
Audio device on High Definition Audio Bus (10EC:0268) – Realtek Audio
Windows 2000, Windows XP/2003(32/64 bits) Driver only (Executable file) [link]
Intel Driver Update Utility
Available at [link] – May detect some drivers but not all.
It appears that this Toshiba has hardware similar to the Dell Vostro V13 [link] and the Dell Studio 1555 [link]. You may be able to find some drivers to fill the missing pieces by checking the links above. Please let me know what works for you so that I can update information.
If you own or use this model Toshiba laptop and have different hardware, or have a link to a driver not listed above, or even an alternate driver download location, please feel free to leave a comment below. I will be updating this article as I find applicable drivers. If anything here has helped you, please let me know by leaving a kudos!
For about a week now I’ve been wrestling with implementing a system where CrashPlan would backup to my network drive. I ran into a really bit problem: When you mount a network location in Gnome using the GUI (gvfs), root can’t access it. Since the CrashPlan engine runs at root, it makes the network location unusable as a backup destination.
After a while of working on different ways to solve this rather large hurdle, I came up with the idea of simply mounting the network location using smbmount (mount.cifs). After some testing and tweaking, I was able to get it successfully working and added an entry to fstab to have it mount at boot time. I chose /mnt/mynas as the mount point.
See Synology DiskStation and Samba mount permissions for my method of getting it mounted with the correct file permissions.
Once it was set to mount at boot-time, I can now open the CrashPlan client and set /mnt/mynas as a destination folder, and now I have both local and off-site backups!
Feel free to share your thoughts and/or feedback in the comments below!
So today I was using smbmount to mount a network share from my Synology DiskStation to my Linux PC when I noticed a rather annoying file permissions issue that I couldn’t seem to fix. Why am I using smbmount and not Gnome’s GUI to mount? Because I need root to have access to the file system as well so that CrashPlan can back up to it.
Here’s what happened:
First, I mounted the share (as root):
smbmount //diskstation/mike /mnt/mynas -o credentials=/home/mike/mike.cred,uid=mike,gid=mike
(For more information on the smbmount or the mount.cifs credentials file, see the Ubuntu manpage for mount.cifs)
That worked great, except for when I do this (as root)…
ls -ld /mnt/mynas
… I get the following output:
drwxrwxrwx 17 mike mike 0 2011-05-20 09:25 mynas
I sure didn’t want the directory world-writable. So I tried specifying
dir_mode as both
0755 using the following (as root):
smbmount //diskstation/mike /mnt/mynas -o credentials=/home/mike/mike.cred,uid=mike,gid=mike,file_mode=0755,dir_mode=0755
Then I checked it:
ls -ld /mnt/mynas
… and got:
drwxrwxrwx 17 mike mike 0 2011-05-20 09:25 mynas
That didn’t do anything at all to help. Why? Because as it turns out the DiskStation is using a Samba server with CIFS extensions and is passing the permissions to smbmount (mount.cifs). The
dir_mode options are ignored if the remote server is using CIFS extensions.
If the server does not support the CIFS Unix extensions this overrides the default file mode.
If the server does not support the CIFS Unix extensions this overrides the default mode for directories.
Source: Ubuntu manpages.
So there’s a couple of options here. First, I could set it to mount somewhere inside /home/mike, which would generally protect it. But I’d really like to know what’s up with the file permissions. So I did a little more Google-fu.
As it turns out, the CIFS extensions on the DiskStation can be disabled, all it takes is to edit a file. Lepoulpe posted on the Synology forums the following edit:
you can disable “unix extensions” in the ds106’s samba server. To achieve this, you need to add the folowing line in the [global] section of /usr/syno/etc/smb.conf :
So, I SSH’d into my DiskStation as root (should be the same password as ‘admin’ if you’re having trouble) and used the vi editor to make the edit. Afterwards, I restarted samba on the DiskStation by doing this:
Then I remounted the Samba share as root…
smbmount //diskstation/mike /mnt/mynas -o credentials=/home/mike/mike.cred,uid=mike,gid=mike,file_mode=0750,dir_mode=0750
… and checked the permissions:
ls -ld /mnt/mynas
… and got the following output:
drwxr-x--- 17 mike mike 0 2011-05-20 09:25 mynas
So now I have /mnt/mynas mounted to my share on the DiskStation. If I wanted it to mount on boot, I could add something like the following to /etc/fstab:
//diskstation/mike /mnt/mynas smbfs auto,credentials=/home/mike/mike.cred,uid=mike,gid=mike,dir_mode=0750,file_mode=0750,user 0 0
Questions about my method? Have any feedback or alternate methods to share? Please feel free to do so in the comments below. Thank you!