Difference between revisions of "APM setup on a type 2379 ThinkPad T40"
m (Change to T40 Category (my bad on the earlier addition)) |
JustinMason (Talk | contribs) m (→APM Setup on a Type 2379 Thinkpad T40: link to BIOS upgrade data) |
||
| Line 13: | Line 13: | ||
In order to upgrade the BIOS, I needed to install a version of Windows earlier than Windows XP to run the BIOS upgrade application successfully. It wouldn't complete from IBM's default XP installation, or from any version of DOS (it's a Win32 application). I used Windows 98. | In order to upgrade the BIOS, I needed to install a version of Windows earlier than Windows XP to run the BIOS upgrade application successfully. It wouldn't complete from IBM's default XP installation, or from any version of DOS (it's a Win32 application). I used Windows 98. | ||
| − | Once I did that, however, I could boot the IBM hibernation-file creation utility diskette and run the tool, and it created the SAVE2DSK.BIN file successfully. See [[How to make use of Power Management features#using a hibernation file on a dos partition]] for details on sizing. | + | Once I did that, however, I could boot the IBM hibernation-file creation utility diskette and run the tool, and it created the SAVE2DSK.BIN file successfully. See [[How to make use of Power Management features#using a hibernation file on a dos partition|this page]] for details on sizing. |
| − | Also worth noting that I did have to use a FAT32 volume -- using a file on a FAT16 volume is no longer an option with today's large RAM installations, since neither [[tphdisk]] nor IBM's utility could create working 512MB SAVE2DSK.BIN files in a FAT16 filesystem. | + | Also worth noting that I did have to use a FAT32 volume -- using a file on a FAT16 volume is no longer an option with today's large RAM installations, since neither [[tphdisk]] nor IBM's utility could create working 512MB SAVE2DSK.BIN files in a FAT16 filesystem due to size limits in that filesystem. |
| − | Another glitch I ran into is that I had no floppy drive; however, during this process I discovered that one can burn a floppy disk image as an ISO image to a CD-ROM, | + | Another glitch I ran into is that I had no floppy drive; however, during this process I discovered that one can burn a floppy disk image as an ISO image to a CD-ROM, as described on [[BIOS_Upgrade#Creating_a_Bootable_CD_from_a_Floppy_Image|this page]]. |
| + | |||
| + | Justin Mason, jm at jmason dot org | ||
[[Category:T40]] | [[Category:T40]] | ||
Revision as of 20:02, 23 March 2005
APM Setup on a Type 2379 Thinkpad T40
There have been varying reports of success or lack thereof using tphdisk; my experience, as noted in this and this mail to the linux-thinkpad list, is that a pure-Linux fix on a T40 using tphdisk and a hibernate file or partition, was not possible.
My Thinkpad is a T40, type 2379, bought in the US.
(My theory is that this is because tphdisk just creates a file in the right format, but does not twiddle a bit in the BIOS to indicate that APM hibernation is now possible. In earlier Thinkpads, this bit would have been set during the factory setup of the default Windows install with APM hibernation file; but in modern Thinkpads, Windows XP is installed with ACPI software-suspend instead.)
I did manage to get it working after some trial and error. Here's how.
First off, the BIOS had to be at least 3.00c to support APM hibernation on my 2379 T40. Using an earlier BIOS, the SAVE2DSK.BIN file was supposedly created successfully by both tphdisk and IBM's utility, but hibernation failed.
In order to upgrade the BIOS, I needed to install a version of Windows earlier than Windows XP to run the BIOS upgrade application successfully. It wouldn't complete from IBM's default XP installation, or from any version of DOS (it's a Win32 application). I used Windows 98.
Once I did that, however, I could boot the IBM hibernation-file creation utility diskette and run the tool, and it created the SAVE2DSK.BIN file successfully. See this page for details on sizing.
Also worth noting that I did have to use a FAT32 volume -- using a file on a FAT16 volume is no longer an option with today's large RAM installations, since neither tphdisk nor IBM's utility could create working 512MB SAVE2DSK.BIN files in a FAT16 filesystem due to size limits in that filesystem.
Another glitch I ran into is that I had no floppy drive; however, during this process I discovered that one can burn a floppy disk image as an ISO image to a CD-ROM, as described on this page.
Justin Mason, jm at jmason dot org
