Changes between Version 3 and Version 4 of Requirements
- Timestamp:
- Jun 23, 2012, 7:46:00 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Requirements
v3 v4 29 29 30 30 == JFS boot disks == 31 Because of the way that the JFS boot loader works, booting from a JFS boot disk may be slower than booting from an HPFS boot disk. We are investigating a way to improve the performance of the JFS boot loader. If you have a JFS boot disk and the slow booting is a problem for you, you can try one or more of these suggestions to improve your booting performance:31 Because of the way that the JFS boot loader works, booting from a JFS boot disk may be slower than booting from an HPFS boot disk. This is not a defect in the PSD, but rather a characteristic of the way the JFS boot loader works. We are investigating a way to improve the performance of the JFS boot loader. If you have a JFS boot disk and the slow booting is a problem for you, you can try one or more of these suggestions to improve your booting performance: 32 32 * Make sure you are using the retail version of the PSD, not the debug version. 33 33 * Make sure you are using a retail kernel, not a debug kernel. … … 69 69 Some systems enter suspend immediately after !AcpiDaemon is started. This is due to a misbehaving SLPB device which generates repeating suspend requests. 70 70 71 NOTE: In version 3.19.16 and later, a workaround was implemented to ignore SLPB events if one occurs within 10 seconds of starting !AcpiDaemon.exe. The SLPB events are still generated by the hardware every 2 seconds, but they are simply ignored. If !AcpiDaemon logging is enabled, the log file could grow very large logging these events. An actual fix is still being investigated. 71 NOTE: In version 3.19.16 and later, a workaround was implemented to ignore SLPB events if one occurs within 10 seconds of starting !AcpiDaemon.exe. The SLPB events are still generated by the hardware every 2 seconds, but they are simply ignored. If !AcpiDaemon logging is enabled, the log file could grow very large logging these events. An actual fix is still being investigated. You cannot use the suspend button on systems with this problem. 72 72 73 73 = Collecting Logs =