This item does not appear to have any files that can be experienced on Archive. Please download files in this item to interact with them on your computer. Show all files. Uploaded by shermanzuki on November 3, Internet Archive's 25th Anniversary Logo.
Search icon An illustration of a magnifying glass. User icon An illustration of a person's head and chest. Sign up Log in. Web icon An illustration of a computer application window Wayback Machine Texts icon An illustration of an open book. Books Video icon An illustration of two cells of a film strip.
I have changed this to and it usually shortens shutdown to around 30 seconds. Occasionally not - and I haven't figured out why yet. If you fiddle with this, beware. You risk hosing the registry. Making it too short could force terminate services that were still legitimately shutting down. Other keys that affect shutdown timeouts but seem sane on the T16 are:.
With the 7 cell battery - the largest available in this screen size - I can get hours. Closer to 2 with the DVD drive running. The all had the available discrete graphics option, so that's no excuse for the T61's poor battery life. Lenovo ships these laptops with a hidden partition that contains rescue and recovery tools as well as a full image of the factory drive configuration. On my machine it used about 5G of drive space. It is bootable, and has utilities that can hopefully access an un-bootable Windows partition.
It can access the network for downloading repair files and uploading salvaged files. It can also access USB devices for those purposes. It can save the entire drive as a backup image; that can also be done from within Windows.
All that is wonderful, but it is rather fragile. In order to maintain the service partition's bootability via the ThinkVantage button one must not touch the MBR boot code. There is some kind of magic here that doesn't tolerate fiddling. If the MBR is replaced, even with a "vanilla" Microsoft-style boot record, the ThinkVantage button won't boot the service partion. It will still be bootable from other boot loaders - grub for instance.
This gets difficult when arranging a multi-boot machine. There are techinques for multibooting using the Microsoft boot mechanism in the Windows partition. Here's one. I haven't tried it. I'm more comfortable with grub, the open-source "Grand Unified Boot Loader" so I fiddled with using that. What does work is to install grub in a primary partition and set that partition active so BIOS boots it in the default case. This is easy when installing Linux - you can specify that grub goes only in the Linux partition's boot sector.
With a Solaris install, it is necessary to set the Solaris partition active before the installation, or the Solaris installer will replace the MBR with a vanilla one. Solaris grub will boot OK, but the ThinkVantage service boot is lost. After many re-images back to factory state, I figured out the Solaris trick above, and had a multiboot machine that could still bring up the service partition via the ThinkVantage button.
The Windows rescue and recovery utility couldn't find it any more. I couldn't make restore images of XP from within XP. Braindead indeed.
Presumably it was confused by the additional partitions. Losing the ThinkVantage service boot ability wasn't a big deal, but losing the ability to make ongoing backup images of XP was. Some notes about that here: T61 VMWare. Using the Lenovo utility in XP to make bootable backup images of the running system - to an external USB drive - is really useful.
It's fairly quick to save and restore around 30 min each when around 50G of the drive is in use and encourages good backup habits. I let the updater download and install it and it seemed to find the service partition correctly. I also made a full drive backup to an external USB drive that included my current running XP configuration and the service partiton - or so I thought.
See below. I have had occastion to do a full restore from the image I saved to USB drive. Both to recover from my experiments, and to move to another hard drive. It doens't contain the factory restore image any more. That's the bad news. The good news is that it's now less than 1G. I don't know where I lost the factory image part of the service partition in my saved image.
It could have been during the update I don't think so - I believe the new set of factory media burned after the update contain the factory image , I might have fat-fingered something in the image creation, or it could just be a bug triggered by my partion fiddling. I observed a quirk when moving a restored service partition using Gparted.
After restoring from the factory recovery media. Gparted reports an error when moving the service partition. In my case, the move was fine. The error is reported by the post-move partition check. For some reason, the service partition image has a back-up boot sector that is different from the primary boot sector. They are both valid but they have different text labels. It's harmless. Notes here.
0コメント