Author: claimsbot

1. A method for preserving mobile device user settings, comprising:
initiating an enterprise application on a mobile device, and reading a client properties file from a device memory of the mobile device into an application memory;
receiving an updated properties file from a server in the device memory;
comparing time values of the updated properties file to time values of the client properties file in the application memory;
reconciling, based on the comparison, the client properties file and the updated properties file to yield a reconciled properties file; and
writing the reconciled properties file to the device memory.
2. The method of claim 1, further comprising modifying the client properties file prior to receiving the updated properties file, wherein time values of the updated properties file are compared to time values of the modified client properties file, and wherein the modified client properties file is reconciled with the updated properties file to yield the reconciled properties file.
3. The method of claim 1, further comprising requesting the updated properties file from the server prior to the receiving step.
4. The method of claim 1, wherein the device memory is selected from the group consisting of a disk, a memory stick and random access memory.
5. The method of claim 1, wherein the client properties file and the updated properties file each contain a configuration of the enterprise application, and wherein the client properties file further contains the mobile device user settings.
6. The method of claim 1, wherein the comparing step comprises comparing a date of the updated properties file to a date of the client properties file.
7. The method of claim 1, wherein the reconciling step comprises reconciling the updated properties file and the client properties file to yield the reconciled properties file if the time values of the updated properties file are different than the time values of the client properties file.
8. A method for preserving mobile device user settings, comprising:
initiating an enterprise application on a mobile device, and reading a client properties file from a client database of the mobile device into an application memory;
receiving an updated properties file from a server database to a device memory of the mobile device;
reconciling the updated properties file with the client properties file in the client database to yield a reconciled properties file;
replacing the client properties file in the client database with the reconciled properties file; and
synchronizing the reconciled properties file to the server database.
9. The method of claim 8, further comprising modifying mobile device user settings of the reconciled properties file on the mobile device, wherein the synchronizing step comprises synchronizing the modified reconciled properties file to the server database.
10. The method of claim 8, wherein the reading step comprises:
determining if the client properties file is in the client database;
reading the client properties file from the device memory if the client properties file is not in the client database;
copying the client properties file to the client database; and
deleting the client properties file from the device memory after the copying step.
11. The method of claim 8, wherein the updated properties file is reconciled with another properties file prior to being received on the mobile device.
12. The method of claim 8, wherein the device memory is selected from the group consisting of a disk, a memory stick and random access memory.
13. The method of claim 8, further comprising requesting the updated properties file from the server database prior to the receiving step.
14. The method of claim 8, wherein the client database and the server database are DB2 databases.
15. A system for preserving mobile device user settings, comprising:
a file reading system for reading a properties file corresponding to an enterprise application initiated on a mobile device into an application memory;
a file request system for requesting and receiving an updated properties file from a server to a device memory of the mobile device;
a time value system for comparing time values of the updated properties file to time values of the client properties file;
a reconciliation system for reconciling the updated properties file with the client properties file to yield a reconciled properties file based on the comparison; and
a file write system for writing the reconciled properties file to the device memory.
16. The system of claim 15, further comprising a configuration system for modifying the client properties file, wherein time values of the updated properties file are compared to time values of the modified client properties file, and wherein the modified client properties file is reconciled with the updated properties file to yield the reconciled properties file.
17. The system of claim 15, wherein the device memory is selected from the group consisting of a disk, a memory stick and random access memory.
18. The system claim 15, wherein the client properties file and the updated properties file each contain a configuration of the enterprise application, and wherein the client properties file further contains the mobile device user settings.
19. The system of claim 15, wherein the time value system compares a date of the updated properties file to a date of the client properties file.
20. The system of claim 15, wherein the reconciliation system reconciles the updated properties file and the client properties file in the application memory to yield a reconciled properties file if the time values of the updated properties file are different than the time values of the client properties file.
21. The system of claim 15, wherein the file write system replaces the updated client file in the device memory with the reconciled properties file.
22. A system for preserving mobile device user settings, comprising:
a file reading system for reading a properties file corresponding to an enterprise application initiated on a mobile device from a client database into an application memory;
a file request system for requesting and receiving an updated properties file from a server database to a device memory of the mobile device;
a reconciliation system for reconciling the updated properties file with the client properties file in the client database to yield a reconciled properties file;
a file write system for replacing the client properties file in the client database with the reconciled properties file; and
a synchronization system for synchronizing the reconciled properties file to the server database.
23. The system of claim 22, further comprising a configuration system for modifying mobile device user settings of the reconciled properties file on the mobile device, wherein the synchronization system synchronizes the modified reconciled properties file to the server database.
24. The system of claim 22, wherein the file reading system:
determines if the client properties file is in the client database;
reads the client properties file from the device memory if the client properties file is not in the client database;
copies the client properties file to the client database; and
deletes the client properties file from the device memory after the copying step.
25. The system of claim 22, wherein the updated properties file is reconciled with another properties file prior to being received on the mobile device.
26. The system of claim 22, wherein the device memory is selected from the group consisting of a disk, a memory stick and random access memory.
27. The system of claim 22, wherein the client database and the server database are DB2 databases.
28. A program product stored on a recordable medium for preserving mobile device user settings, which when executed, comprises:
program code for reading a properties file corresponding to an enterprise application initiated on a mobile device into an application memory;
program code for requesting and receiving an updated properties file from a server to a device memory of the mobile device;
program code for comparing time values of the updated properties file to time values of the client properties file;
program code for reconciling the updated properties file with the client properties file to yield a reconciled properties file based on the comparison; and
program code for writing the reconciled properties file to the device memory.
29. The program product of claim 28, further comprising program code for modifying the client properties file, wherein time values of the updated properties file are compared to time values of the modified client properties file, and wherein the modified client properties file is reconciled with the updated properties file to yield the reconciled properties file.
30. The program product of claim 28, wherein the device memory is selected from the group consisting of a disk, a memory stick and random access memory.
31. The program product claim 28, wherein the client properties file and the updated properties file each contain a configuration of the enterprise application, and wherein the client properties file further contains the mobile device user settings.
32. The program product of claim 28, wherein the program code for comparing time values compares a date of the updated properties file to a date of the client properties file.
33. The program product of claim 28, wherein the program code for reconciling reconciles the updated properties file and the client properties file in the application memory to yield a reconciled properties file if the time values of the updated properties file are different than the time values of the client properties file.
34. The program product of claim 28, wherein the program code for writing replaces the updated client file in the device memory with the reconciled properties file.
35. A program product stored on a recordable medium for preserving mobile device user settings, which when executed, comprises:
program code for reading a properties file corresponding to an enterprise application initiated on a mobile device from a client database into an application memory;
program code for requesting and receiving an updated properties file from a server database to a device memory of the mobile device;
program code for reconciling the updated properties file with the client properties file in the client database to yield a reconciled properties file;
program code for replacing the client properties file in the client database with the reconciled properties file; and
program code for synchronizing the reconciled properties file to the server database.
36. The program product of claim 35, further comprising program code for modifying mobile device user settings of the reconciled properties file on the mobile device, wherein the program code for synchronizing synchronizes the modified reconciled properties file to the server database.
37. The program product of claim 35, wherein the program code for reading:
determines if the client properties file is in the client database;
reads the client properties file from the device memory if the client properties file is not in the client database;
copies the client properties file to the client database; and
deletes the client properties file from the device memory after the copying step.
38. The program product of claim 35, wherein the updated properties file is reconciled with another properties file prior to being received on the mobile device.
39. The program product of claim 35, wherein the device memory is selected from the group consisting of a disk, a memory stick and random access memory.
40. The program product of claim 35, wherein the client database and the server database are DB2 databases.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A method of controlling a power inverter, comprising:
sensing a power factor of a capacitance associated with a cold cathode fluorescent lamp (CCFL) coupled to an output of a power inverter;
based on at least the sensed power factor, determining at least one desired output characteristic for an alternating current to be generated by the power inverter, wherein the at least one desired output characteristic comprises at least one of: (a) an amplitude of a voltage of the alternating current, (b) a frequency of the voltage of the alternating current, and (c) a peak amplitude of the alternating current; and
generating the alternating current comprising the desired output characteristic at the output of the power inverter.
2. A method according to claim 1, wherein the power inverter comprises a full bridge inverter.
3. A system for converting a direct current into an alternating current comprising:
a switching module having an input and an output, the switching module operable to receive a direct current at the input and to generate at the output a corresponding alternating current having at least one desired output characteristic, wherein the at least one desired output characteristic comprises at least one of: (a) an amplitude of a voltage of the alternating current, (b) a frequency of the voltage of the alternating current, and (c) a peak amplitude of the alternating current;
a sensing module coupled to the switching module output, the sensing module operable to sense a power factor associated with a capacitance associated with a cold cathode fluorescent lamp (CCFL) coupled to the switching module output; and
a control module coupled to the power inverter and the sensing module, the control module operable to control the desired output characteristic based at least on the sensed power factor.
4. A system according to claim 3, wherein the switching module comprises a full bridge inverter.
5. An information handling system comprising:
a processor;
a memory communicatively coupled to the processor;
a display device coupled to the processor, the display device including a cold cathode fluorescent lamp (CCFL) that illuminates the display device; and
a power inverter coupled to the CCFL, the power inverter providing an alternating current to the CCFL, wherein an output characteristic of the alternating current is based at least on a power factor associated with the a capacitance of the CCFL, and, wherein the at least one desired output characteristic comprises at least one of: (a) an amplitude of a voltage of the alternating current, (b) a frequency of the voltage of the alternating current, and (c) a peak amplitude of the alternating current.
6. An information handling system according to claim 5, the power inverter comprising:
a switching module having an input and an output, the switching module operable to receive a direct current at the input and to generate at the output a corresponding alternating current with the desired output characteristic;
a sensing module coupled to the switching module output, the sensing module operable to sense the power factor; and
a control module coupled to the power inverter and the sensing module, the control module operable to control the desired output characteristic based at least on the sensed power factor.
7. An information handling system according to claim 6, further comprising a direct current power source coupled to the input of the power inverter.
8. An information handling system according to claim 6, wherein the switching module comprises a full bridge inverter.

1. A beverage maker comprising:
a pump;
a noise attenuator housing with an inlet port, in communication with the pump, and an outlet port;
an inlet chamber in the noise attenuator housing, the inlet chamber receiving flow from the inlet port, the inlet chamber having compliant walls permitting volumetric expansion of the inlet chamber;
an outlet chamber in the noise attenuator housing, the outlet chamber having spheroidal walls, wherein flow from the outlet chamber passes to the outlet port; and
a flow-restrictor disposed between the inlet and outlet chambers and restricting flow from the inlet chamber to the outlet chamber.
2. The beverage maker of claim 1 wherein
the compliant walls of the inlet chamber include an insert of resilient material, and a cavity in the insert defining the inlet chamber, and
a void extends about the insert, between an outer surface of the insert and an inner surface of the noise attenuator housing, for expansion of the inlet chamber.
3. The beverage maker of claim 2 wherein the flow-restrictor comprises at least one passage extending through the insert.
4. The beverage maker of claim 2 wherein at least part of the spheroidal walls of the outlet chamber comprise a concavity in the insert.
5. The beverage maker of claim 1 wherein at least part of the spheroidal walls of the outlet chamber comprise a recess in the housing.
6. The beverage maker of claim 3 wherein the at least one passage extending through the insert comprises a plurality of passages extending through the insert.
7. The beverage maker of claim 5 wherein an axis of each of the at least one passage extending through the insert is aligned with a concave face of the recess in the housing.
8. The beverage maker of claim 2 wherein the insert has axially opposing ends, each end having a transverse face abutting the noise attenuator housing, and a circumferential face abutting the housing and adjacent each transverse face.
9. The beverage maker of claim 8 wherein the transverse faces and circumferential faces are annular, and prevent axial movement of the insert, and radial movement of the insert at the ends, and seal the inlet and outlet chambers from the void.
10. The beverage maker of claim 2 wherein the insert is an elastomer.
11. The beverage maker of claim 10 wherein the elastomer is a silicone elastomer.
12. The beverage maker of claim 1 wherein the pump is a positive-displacement pump.
13. A beverage maker comprising:
a positive-displacement pump;
a noise attenuator housing with an inlet port, in communication with the pump, an outlet port, and a recess with a concave face;
an elastomeric insert in the housing;
an inlet chamber in the noise attenuator housing defined partially by a cavity in the insert, the inlet chamber receiving flow from the inlet port, the cavity having compliant walls permitting volumetric expansion of the inlet chamber;
a void extending about the insert, between an outer surface of the insert and an inner surface of the housing for expansion of the inlet;
an outlet chamber in the noise attenuator housing, the outlet chamber having spheroidal walls defined partially by a concavity in the insert, wherein flow from the outlet chamber passes to the outlet port, and
at least one passage extending through the insert as a flow restrictor, restricting flow from the inlet chamber to the outlet chamber wherein an axis of the at least one passage extending through the insert is aligned with the concave face of the recess in the noise attenuator housing
14. The beverage maker of claim 15 wherein the insert has axially opposing ends, each of the ends having a transverse face abutting the noise attenuator housing, and a circumferential face abutting the housing and adjacent each transverse face.
15. The beverage maker of claim 8 wherein the transverse faces are annular and prevent axial movement of the insert, the circumferential faces are annular and prevent radial movement of ends of the insert, and seal the inlet and outlet chambers from the void.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1-4. (canceled)
5. A hammer drill comprising:
a motor;
a spindle rotatingly driven by the motor and holding an output bit;
a motion conversion member for converting rotational movement of the motor to reciprocating movement;
a striker reciprocatingly driven by the motion conversion member for applying an axial striking force to the output bit;
a striking-notion-releasing mechanism for releasing the striking force applying action exercised by the striker;
a tightening-torque adjusting clutch for interrupting the transfer of the rotational force to the output bit by increasing a load torque; and
a clutch handle for adjusting a fastening torque of the tightening-torque adjusting clutch,
wherein the striking-motion-releasing mechanism is adapted to convert a releasing operation of the striking force applying action to a non-releasing operation and vice versa in response to the actuation of the clutch handle.
6-8. (canceled)
9. The hammer drill of claim 5, wherein the tightening-torque adjusting clutch is adapted to directly couple a driving side to a driven side at the time when the striking force applying action is not released.