U110 user guide - Profile your machine

Profile your machine at http://consumersupport.lenovo.com to keep up
to date with current drivers and revisions.
This is from the User Guide. What does it mean? And how to do it?
I am used to my thinkpad being updated with driver updates and such automatically, how does this work with the U110, if at all?
thanks

*bookmarked for desection*
I already see flaws, like turning off remote registry for example. Remote registry only has very limited access, and you can change the access, but why would you? You can see what it has access to by going into Control Panel > Administative Tools > Local Security Policy > > Local Polices > Security Options, then scroll a little more than half-way, and it's under the Network access box.
There are so many crack pot guides out there, that the only good advice is to look where they looked, and if you don't get it, and don't go though all of it, LEAVE IT ALONE! It only makes servicing the box at a later time a HUGE pain, and if it's in a business, it'll just be reimaged.
Keep this guy's disclaimer in mind at all times. Just do the easy ones to start, like run CCleaner, it basically does everything for you, and doesn't cause any errors (or as far as I know, and I use it just about every other day)
Currently Just passed the CompTIA A+ 601 with flying colours! =D
Owner of an SL500 running Vista Business with 4GB of PC2 6400 RAM

Similar Messages

Can I use FCX for multiple users on the same machine?

I have one mac pro, and two video cmpanies. I have two users on my machine and would like to set up two different final cut x workplatforms. Is that possible?

Of course, you can use FCP X from two different user accounts on your machine. The question here, I believe, is how to separate the content that each user accesses.
One obvious way to achieve that would be to store the content in the system disk - that would put events and projects in each user's Movies folder. But that is a bad option, for performance reasons, and more.
You could have separate external disks for each user to store his content.
Also, you could use different disk images which could, say, be all stored in the same internal (but not system) drive.

Where is the ibooks chapter in the iPad user guide?

This statement was on the web page Apple - Support - iOS apps - iBooks.
Download the User Guide
Download the User Guide for your device and view the iBooks chapter to learn more about iBooks and the iBooks Store. Select your device below:
I could not find a chapter for iBooks in the ipad user guide(iOS 7).

Strangely enough there is no iBooks chapter in the user guide for iOS7. It is there however, in the user guide for iOS 6.
Chapter 23.
You can find it here:
http://manuals.info.apple.com/MANUALS/1000/MA1659/en_US/ipad_ios6_user_guide.pdf

Viewing user guide offline

I wanted to be able to view the ipod touch User Guide offline (instead of depending on a wireless connection to view the page in Safari). I was going crazy, because I thought I had seen somewhere when I first got the iPod a couple months ago how to do it, but could not remember.
I still have yet to find any instructions on how to do this online. But finally, I think I figured out how:
Open the User Guide in Safari (while connected to wifi)
Click the + at the bottom of the screen
Choose Add to Home Screen
Then click the icon for the User Guide on your home screen (you can turn off Wi-Fi under settings first if you care to try)
It seems to work! Feel free to reply if it seems like I got anything wrong

Some thots:
1 -Open the User Guide in Safari (while connected to wifi)
2 -Click the + at the bottom of the screen
3 -Choose Add to Home Screen
Omit steps 2 and 3. Try this:
0 -turn off wifi
1 -Open the User Guide in Safari
Does that work for you, 'cause it works for me. Here's yet another way I thought of, but someone else answered it nicely already:
http://discussions.apple.com/thread.jspa?threadID=2316358&tstart=60
Pay attention to Dave Sawyer (referencing luvlabs):
"it should be readable any time you wish to reference it"
even offline...

Copy users guide to dvd?

Does anyone know if it is possible to burn the guide to a dvd? Windows can't read it.

The User Guide for your model is a simple .PDF file. Just download the User Guide and then burn the .PDF file to a DVD. You will need to have Adobe Acrobat Reader installed on your computer in order to view the file. As long as you are downloading I would recommend downloading the Hardware Maintenance Manual. That manual contains a lot of useful information as well.
If you do not have Adobe Acrobat Reader installed, it can be downloaded at the link below.....
http://www.adobe.com/products/reader.html
Owner & Operator of the following:
● Lenovo Ideapad Z570 w/ Win 7 & Win 8.1 Dual Boot ● Lenovo Yoga 3 Pro w/ Windows 8.1 ● Toshiba A75-S206 w/ Win 7
● IBM Thinkpad T-23 w/ Win XP ● IBM Thinkpad T-22 w/ Win XP • As well as multiple desktops dual/triple booting XP, Vista and Win 7.
★ Find a post helpful? Thank that member by clicking on the ☆Star☆ to the left awarding them a Kudo.
★ Posting a problem and a reply is helpful and it answers your question, please mark it as an "Accepted Solution"
★ I'm not a Lenovo employee, just a volunteer geek who likes to help folks. Enjoy your time here, pay it forward by helping others !
★ Sorry, I don't answer questions via Private Messages. Posting in the appropriate forum is the best way to get assistance.

User guide: MSI HQ USB BIOS Flash Tool

Guide based on USB tool v1.17c
HOW TO properly use the MSI Forum HQ USB Flashing Tool to update your BIOS
This user guide provides a step-by-step explanation for properly using the >>MSI Forum HQ USB Flashing Tool<< to prepare a USB Flash Drive for a safe BIOS-Flash in a pure DOS Environment. The tool itself will not perform the actual flashing operation. It will "only" help you to get your USB Stick set up for an automated DOS flashing procedure which requires final confirmation. (If you should run into any problems before you are prompted for final confirmation in DOS, no attempt to flash has been made yet and there is no danger of a bad flash.)
NOTE: If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect. You can do that by pickup option "Fix My USB key" from the Tool or by using >>> THIS <<< tool here! For future usage you can skip this step, it need to be done only once if your stick need adjustment.
Symptoms that your USB key need a fix after booting from the USB key:
* Error: "No bootable partition in table"
* Blinking cursor in a top left corner and nothing happens
* "RIVER2 MSI"
* "Error loading operating system"
* "Missing operating system"
* "Disk in drive is not a bootable"
* Booting from selected USB key is IGNORED, the other/typical OS continue to load as usual
If still no change after using "Fix My USB key" Tool's option or HP Formatter Tool as alternative.
Then try with different USB key, the issue is there.
Note: Those USB keys who support "U3 Smart", this "feature" must be removed before proceed.
Refer to followed link: http://u3.sandisk.com/launchpadremoval.htm
Read the three notes that follow first before you move on:
1. Note: Before you even think about flashing a different BIOS, be sure that your system is stable. If it is not stable, make it stable first. (Read >>here<<.)
2. Note: Make sure your system meets the preconditions and system requirements mentioned below before you attempt to use the tool.
3. Note: Do know that flashing your BIOS, be it with the help of the tool or otherwise, is done at your own risk.
Contents of the Guide:
0. Preconditions & System Requirements
1. Basic Description of Functionality
2. Installing/Starting the tool.
3. Choosing a Preparation Method
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
3.2. Method 2: Processing a BIOS File Directly
3.3. Method 3: SureHands Live Update
3.4. Method 4: Geometry Change
4. Selecting the USB Flash Drive for preparation
5. BIOS Settings, Booting & Flashing
5.1. BIOS Settings to Check
5.2. Booting from USB Flash Drive
5.3. Flashing Procedure/Running MemTest86+ & CMOS-Clear
6. FAQ: Common Problems & Solutions
7. Version History
0. Preconditions & System Requirements
The main precondition for using the tool is a working & healthy Windows installation on the system that needs the BIOS flash. The Tool is designed to work with MSI Retail Boards & Laptops only.
Please note mainboards of other brands and OEM boards that are manufactured by MSI but sold by Medion, HP, NEC and others are not supported. If you have an OEM board that needs a BIOS update read this topic: >>OEM boards manufactured by MSI<<
Supported Operating Systems: All current Windows Versions (32bit & 64bit, any service pack (SP)): Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, and Windows 7.
The second requirement is that you have a fully functional USB Flash Drive that uses the FAT file system (FAT/FAT32). NTFS is not supported. If your USB Flash Drive is using the NTFS File System, reformat it to FAT or FAT32.
As the tool also provides a Live Update Option ("SureHands"), you'll need a working internet connection if you want to choose this method. Not all boards are supported at this point.*
* Check section 3.3 of this guide to see if your board is currently supported by the SureHands feature.
1. Basic Description of Functionality
The MSI Forum HQ USB Flashing Tool will help you to easily prepare an USB flash drive for an automated BIOS flash in a pure DOS environment, which is the safest way to perform such a procedure. The tool will also allow you to run MemTest86+ in a pure DOS environment. However, the preparation of your USB Stick is done in Windows and basically includes two steps:
(1) The device will be made bootable.
(2) All necessary files (incl. BIOS file, actual flasher and MemTest86+ executable) and all DOS commands that are needed to flash/test memory will automatically be implemented.
Because the tool does not reformat your USB Flash Drive*, no files that may currently be on the stick will be lost during the procedure. Just make sure that there is still some free drive space, otherwise there will not be enough room for the files that are needed for BIOS Flashing.
* Excluding the Geometry Change method which will destroy all data on the USB storage device.
2. Installing/Starting the tool
Treat the forum's USB Flashing Tool like a regular application. Download it to and run it from your hard drive, there is no need to copy & start it from the USB Flash Drive that you want to use for flashing. Both, the installer version and the stand-alone version, do precisely the same job. Which of the two versions you use, is solely up to you and your preferences. The stand-alone version can be started directly by clicking on the executable file. The installer version will perform an installation and provide you with an entry in your start menu and a desktop shortcut to start the tool.
When you start the tool a DOS box should open up to provide you with status messages and prompts. Do not close that box unless you want to abort the preparation procedure!
Please ensure that you connect the USB flash drive you wish to use before starting the Tool!
NOTE: If you do not connect your USB storage device before starting the tool, or the tool doesn't detect it. You can still insert the drive letter, as the tool will continue as normal.
The tool will first check, if an MSI mainboard is installed in your system and show you its model name and PCB Version in a message box. Click >OK< to continue to choose the tool's preparation method that you want to use to prepare your USB Flash Drive.
3. Choosing a Preparation Method
If your MSI Retail Board is properly detected and you have pressed the >OK< button in the message box, an option box will pop up that allows you to choose between three different operating modes. The options you can choose from are more or less self-explanatory, however, read the detailed description if you are unsure how to proceed at this point:
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
Official MSI BIOS-Updates that can be downloaded from the product site of your board model do usually come as .ZIP or .RAR archives that contain the actual BIOS File and the corresponding AWARD or AMI flashing utility (depending on the BIOS Type of your board). If you have downloaded such an archive, you should choose the first method from the option box.
You do not need to extract the files from the BIOS archive. The tool will ask you to point it to the archive you downloaded and automatically extract the BIOS File and the AMI or AWARD flashing utility and put it them on your USB Flash Drive. You don't have to worry about anything else. All you have to do is to remember where you saved the ZIP or RAR file you downloaded:
3.2. Method 2: Processing a BIOS File Directly
If you do not have a ZIP or RAR archive that already contains a BIOS File and the proper flashing utitility, but only the plain unpacked BIOS File, choose the second Method from the option box. In most cases BETA BIOS Files supplied by MSI Support or shared here in the Forum do not come with the proper flashing utility. If the MSI Forum HQ USB Flashing Tool is told to process a plain BIOS File, it will automatically check the type of BIOS File (AMI or AWARD) and then select the proper flashing utility that needs to be used. All you need to do is point the tool to the BIOS-File that is supposed to be flashed:
3.3. Method 3: SureHands Live Update
"SureHands Live Update" is the third operation method you can choose from the option box. It provides a much safer and more reliable alternative to MSI Live Update as the actual BIOS Flash is performed in a pure DOS environment as well. If you decide to use this option, you do not to supply the tool with a BIOS-Archive or a BIOS-File.
Not all MSI Retail Boards are currently supported. With every update of the USB Flashing Tool more boards will be added. At present, you can use the "SureHands" Live Update method with the following boards only (the list will be updated regularly):
AMD based boards:
K8N Neo4-F (MS-7125, PCB 3.0)
K8NGM2-FID (MS-7207, PCB 2.0)
K8N Diamond Plus (MS-7220, PCB 1.0)
K8N Neo3 (MS-7135, PCB 1.0 & 2.0)
K9A Platinum (MS-7280, PCB 1.0)
K9A2 Platinum (MS-7376, PCB 1.0)
K9A2 CF-F (MS-7388, PCB 1.0)
K9N Neo-F (MS-7260, PCB 1.0 & 2.0)
K9VGM-V (MS-7253, PCB1.0)
K9N2GM-F V2 (MS-7509, PCB 1.0)
K9N Neo V2 / V3 (MS-7369, PCB 1.1)
K9N Platinum & K9N SLI Platinum (MS-7250, PCB1.0)
K9N2 Diamond (MS-7375, PCB 1.1)
K9N2 SLI Platinum (MS-7374, PCB 1.1)
K9N2 Zilent (MS-7374, PCB 1.1)
K9N2 Neo-F (MS-7511, PCB 1.1)
DKA790GX Platinum (MS-7550, PCB 1.1)
790FX-GD70 (MS-7577, PCB 1.0)
790GX-G65 (MS-7576, PCB 1.0)
Intel based boards
HydroGenX48C & X48C Platinum (MS-7353, PCB 3.0)
X48 Platinum (MS-7353, PCB 1.0)
X38 Diamond Plus
X38 Diamond (MS-7353, PCB 1.0)
X38 Platinum (MS-7353, PCB 1.0)
EFINITY-FP (MS-7395(E), PCB 1.0)
P35 Neo Combo-F (MS-7365, PCB 1.0)
P35 Neo2 Series (MS-7345, PCB 1.1)
P35 Platinum (MS-7345, PCB 1.1)
P35 Neo-F (MS-7360, PCB 1.0)
G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2)
P965 Platinum (MS-7238, PCB 1.1)
975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
P7N SLI Platinum (MS-7380, PCB 1.0)
P7N2 Diamond (MS-7523 PCB 1.0)
P7N Diamond (MS-7510, PCB 1.0)
P7N SLI Platinum (MS-7380, PCB 1.0)
P6N Diamond (MS-7320, PCB 1.0)
P6N SLI Platinum (MS-7350, PCB 1.0)
P6N SLI-FI (MS-7350 PCB 2.0)
P6N SLI V2 (MS-7346 PCB 1.0)
ECLIPSE SLI (MS-7520, PCB 1.0)
ECLIPSE Plus (MS-7566, PCB 1.0)
P35 Neo3-F (MS-7395, PCB 1.0)
After selecting "SureHands" from the option box, the tool will automatically check for all available official BIOS-Versions for your mainboard. It will also look for the latest available BETA BIOS Version for you board and save that information in a TXT-File on your Desktop:
Note: The SureHands option will not provide you with the latest BETA BIOS, it will only provide the information.
When the tool is done scanning for official BIOS releases for your board, it will give you the possibility to manually choose the BIOS Version you want to flash. SureHands Live Update will not automatically select the latest version and use it for flashing, it will give you the chance of choosing between all available official BIOS releases that are available:
Note that the "May not exist" comment that appears behind some versions does not mean that the BIOS does not exist. If you know the latest BIOS for your board is e.g. v1.8, SureHands will retrieve it even though there may be such a comment. That message is part of a prediction feature that tries to determine future BIOS Releases. If a BIOS version that was predicted by the SureHands feature is not available yet, the tool will tell you if it cannot retrieve the files and ask you to select an earlier version.
3.4 Geometry Change
If the tool fails to make your USB storage device bootable then you will need to use this mode. It will make your drive bootable, select it:
Select your drive then let the tool do it's business.
Once the process is complete, run the tool again via method 1, 2 or 3, restart your computer and try booting from the USB storage device again.
NOTE: This method will destroy ALL data on the USB storage device!
NOTE: This method is available in v1.17 and beyond.
4. Selecting the USB Flash Drive for preparation
When you have chosen one of the three methods from the option list and pointed the tool at the corresponding archive, BIOS File or selected the desired BIOS Version from the list in case you chose to use SureHands Live Update, the MSI Forum HQ USB Flashing Tool will prompt you to enter the drive letter of the USB Flash Drive you want to use for flashing:
Note that certain drive letters are reserved and will therefore not be accepted by the tool (currently A:, B: and C:). If you are sure you have connected an USB Flash Drive to the system that works properly but it does not appear in the table that appears in the DOS box, enter the corresponding drive letter anyway and see if the tool accepts it. This can happen in rare cases, but it is usually no problem.
The tool will check the selected drive and will provide you with status messages. If everything is okay, the message should look like this:
The tool will attempt to make the device bootable and automatically write all files that are needed for flashing to the drive to prepare it for flashing. If the procedure was successful, you will get the following message in the DOS box:
5. BIOS-Settings, Booting & Flashing
If the Tool has prepared your drive for booting & flashing, no BIOS flash attempt has been made yet. Only the preparation process. In order to initiate the flashing procedure, you have to restart your system and make it boot from the USB Flash drive. Before you move on to do that, enter the BIOS Setup and check a few options:
5.1. BIOS Settings to Check
Check USB-related Options in BIOS:
- USB Controller
- USB 2.0 Controller
- USB Legacy Support
- USB Storage Support
- Boot from other devices
- etc.
Not all of these options may be found in BIOS and the precise name may vary as well. Just make sure you checked for such options and that they are enabled (if present).
Another option you should check for is "Boot Sector Protection". If such an option is present in your BIOS, make sure it is disabled because it may make a BIOS Flash impossible.
@all Overclockers: In case your system is currently overclocked, make sure you roll back to default clock and voltage settings before you attempt to start the flashing procedure. Otherwise you increase the risk of an unsuccesful flash, and you most probably don't want something like that to happen.
5.2. Booting from USB Flash Drive
To boot from your USB drive you can either change the boot sequence in BIOS accordingly or just press F11 during POST* to get access to the BIOS Boot Menu. From here, you can select you drive directly without having to adjust the boot sequence in BIOS. Note that your USB Flash Drive may be listed as a hard drive (if you choose that entry you will get another list to choose from).
* Not all mainboards use F11, for the boot menu. If F11 fails for you, please consult your manual for the correct key.
Note: If you have problems booting from your drive, look at the FAQ-Section of this guide and see if any of the tips resolve the issue.
5.3. Flashing Procedure/Running MemTest86+
As soon as the system boots from the drive, DOS will be loaded and you will be displayed with two options. One option will start MemTest86+, the other will begin the flashing procedure. If no choice is made, MemTest86+ will automatically start.
The flashing procedure will automatically be initiated from there. You will see status messages on the screen that will supply you with information and also prompt you for final confirmation for the actual BIOS-Flash. A backup of you current BIOS will automatically be saved to a file on the drive (backup.bin) before the flashing actually starts. You do not need to enter any commands in DOS. All you have to do is acknowledge the information on the screen by pressing a key.
The flash itself will only take a couple of seconds (20-30s at the most). If the flashing is successfully completed, shutdown the system and clear CMOS with main A/C power cable removed from PSU. Read the >>Clear CMOS Guide<< for further information.
After clearing CMOS you have completed the BIOS-Flash.
Guide created by Jack The Newbie and the forum team

Version updated to 1.18x:
* Mode 3 Sure Hands, Live Update:
- Removed beta BIOS query check[global]
- Fixed issue K9N2 Diamond unable to be detected as supported unit if onboard is installed BIOS version 2.4,
add dynamic detection for future versions.
- Fixed issue 790FX-GD70 unable to be detected as supported unit and add dynamic detection for future versions.
- Fixed issue 790GX-G65 unable to be detected as supported unit and add dynamic detection for future versions.
- Add support for 785G-E65, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 785G-E53, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 790GX-G65 Winki ED, prediction BIOS range 2.1 - 2.A
- Fixed issue P7N Diamond unable to be detected as supported unit if onboard BIOS installed is 1.3 and above,
add dynamic detection for future versions.
- Add support for K9A2 Neo2, prediction BIOS range 7.4 - 7.D
- Add support for 790XT-G45, prediction BIOS range 2.2 - 2.B
- Add support for 770T-C45, prediction BIOS range 8.4 - 8.D
- Add support for 770T-C35, prediction BIOS range 8.4 - 8.D
- Fixed issue K9A2 Platinum[V1,V2] unable to be detected as supported unit if onboard BIOS installed is 1.9,
add dynamic detection for future versions, prediction BIOS range extended to 1.F0
- 790GX-G65 board prediction BIOS range extended to ver: 1.D0
- 790GX-G65 board update bios base ver from 1.xx to 4.xx [following new msi rule for this board jumping from 1.xx to 4.xx]
- Add support for 770-C35|C45 boards [p1] BIOS range 1.40 - 1.D0
- Add support for 770-G45 board [p2] BIOS range A10 - AA0
* Add "Exit" option to navigation screen
* Update version info related to boot part
* Update boot part to handle newest features
* Modify Self update sequence of Installer version
* Update internal version check ID
* Mode 4 minor update
* Build and add new Tool's module for newest features
* W32 Tool's exit time part decreased by 10 seconds
* On received OS reboot user request, time delay before execution decreased by 15 seconds
* Update EC decoder
* Update start-up information screen
* Auto store start-up detected information to user's desktop ==> [MSIHQ_INFO.TXT]
Details:
Easy to show machine information on request, instead write down from the screen manually, now just copy/paste can be used from MSIHQ_INFO.TXT
User can check and compare information before and after the BIOS update
Also usefull if didn't remember what was his original BIOS or EC versions before the update, Tool will auto store it there.
And easy can be checked if needs. E.g Tool's log file of each Tool's execution, each report will include date and time as well.
F.A.Q example:
Q: I flashed BIOS on my notebook and now it doesn't work properly.. And i don't remember what was my old BIOS version.. What can i do?
A: Take a look in MSIHQ_INFO.TXT at your desktop, there is auto recorded your detailed information about your notebook before the BIOS update.
So you can easy find what was your original BIOS & EC versions.
Is it OEM one or not, and the exact original BIOS & EC versions.
So you can roll back easy or if crossflashing were done to reflash to correct versions.
Example question:[this board now use 4.xx bios, but don't have time to make a new images.]
It's just example, do not mean that this BIOS used in the example is bad. But generally often can need to roll back to older version.
Or to use Sure Hands because[The BIOS is N/A for manual download, By SureHands no need to browse/search/download and point to the BIOS version, also eliminate any chances to pickup the wrong BIOS, and not at last its more quickly[save a time]]
Q: I flashed my BIOS via MSI Live Update, but the new BIOS has an issues.
How i can roll back to my old BIOS version?
The MSI LiveUpdate can only update to the latest BIOS version, which is not good for me.
And i can't download my old BIOS version manually... Because "This BIOS can only update via Live Update function"
http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1739
How i can re-flash to my original BIOS version and from where can i get it?
A: Run >>Use the MSI HQ Forum USB flasher<<,
then choose Mode 3 [Live Update{aka SureHands}]:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:09:45,15
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.3
BIOS Date: 05/08/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:22:38,42
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.6
BIOS Date: 11/30/2009
Then choose your old BIOS version from the list:
The followed image used below is a sample from Eclipse board,[no time to make accurate image] but will look similar for others boards too:
In a list will be noticed that there is a future BIOS versions.
Some of them will be not released yet. If you pick some of those the Tool will note you:
It's a part of Tool's BIOS prediction system called "Crystal Ball", when MSI release a future BIOSes for your board,
Tool can find them immediately. By that way the Tool no need to be updated to be actual in each moment
* Add new feature "True BIOS Version Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
Q: What "True BIOS Version Ready" means? Does the Tool show the wrong BIOS version until now?
A: Of course not, the Tool always show accurate info.
The same as CPU-Z/Everest of whatever other Tool.
However Tool also detect EC-FW versions for notebooks:
The "True BIOS Version Ready" Tool's feature is aimed to eliminate user's mass confusion about MSI BIOS versions.
And not only users are confused, but MSI's Live Update is confused too... which confuse users even more..
Few typical real examples of confusion:
"K9A2 CF wont flash to Bios v. 1.A !!!"
Quote from: Fingon on 25-October-09, 16:53:15
Hi MSI,
I have a problem. I have bought a new processor: AMD Phenom II x545. I looked on the support page of my MB (MSI K9A2 CF) and there the CPU is supported from the bios version 1.A. So I wanted to flash the Bios the the newest version (1.A). I used the MSI live update 4 program to flash it via windows mode. But everytime it boots it writes "CMOS checksum BAD", then I hit F1 to Bios and I see the version of my BIOS fell to the oldest version 1.1. Then I tried to flash it thru Flash disc (with boot files) and dos mod. The result is the same. I can flash my MB to version 1.8 but when I try the 1.A it wont flash it and my Bios fell to the oldest version (1.1). I realised that the exe files in version 1.1-1.8 are the same (afud412.exe) but the exe file in 1.A is different (afud4310.exe).
My questions are:
1) How to flash my MB to the version 1.A ?
2) Is version 1.A really needed for AMD Phenom II x545? I guess yes, because CPU was avaible in July 2009 and the bios 1.A went out in June 2009. I am able to flash it only to version 1.8 (december 2008).
Thank you for any help!!
EDIT: After reading this topic: https://forum-en.msi.com/index.php?topic=129204.0 I realised I have the VERSION 1 of this board (I purchased it right after the launch of the MB (November 2007). It means it doesnt support CPU over 95W, but my Phenpom II x545 has only 80W. I still cant update Bios to the 1.A version.
So my third question is:
3) Is the Bios update 1.A only for version 2 of this MB?
Thx for replies!
Quote from: Jack t.N. on 25-October-09, 17:16:16
A CMOS Checksum error is normal and expected after a BIOS Flash and/or a CMOS Clear. The fact that this message appears, shows, that there was actually something programmed to the chip.
If you haven't done that yet, please clear CMOS with the main A/C power cable removed from your PSU and load "Optimized Defaults" in BIOS Setup.
The BIOS Version should be shown on the POST Status Screen and there should be a date behind it. Please check the BIOS Date and write it down:
Are you absolutely and entirely sure that what you see is "1.1" and not "1.10"? Because v1.A0 is actually just the hexadecimal notation for v1."10" (one dot ten). The hexadecimal notation is only used in the BIOS File Ending. Once flashed, the BIOS will not identify itself in hexadecimal notation but in decimal code (which means you will never see "v1.A0" after the flash but "v1.10" instead.
Here is a piece of well-meant advice for now and the future: MSI Live Update should be avoided under all circumstances when it comes to BIOS Updates and/or information retrieval regarding your current BIOS Version. Why? Because this tool is stupid and one of there most risky applications for performing a BIOS Flash. Please uninstall it completely.
Why do I call it stupid? I call it stupid because it does not differentiate between hexadecimal notation and decimal notation. It will show you that "v1.A0" is available. The it will flash it, if you allow it to do so. Of course, a v1.A0 Version will always come out as "v1.10" (one dot ten). When you re-run MSI Live Update it will not recognize that v1.A0=v1.10 and tell you again that there is a newer version available (1.A0, which, again, is the same as v1.10, which was just properly flashed).
I believe that the update went just fine, that you are currently using v1.A0=v1.10 and that MSI Live Update is actually just creating a pseudo-problem which is currently confusing you. The pseudo-problem will immediately be out of the world, if you uninstall MSI Live Update and rely on the BIOS ID String as it appears on the POST Status Screen (this includes the date shown there).
If a BIOS Update should ever be necessary again, please make sure that you won't use MSI Live Update but >>Use the MSI HQ Forum USB flasher<< instead.
Quote from: Fingon on 25-October-09, 18:03:44
Thank you for the quick reply!!
Thats exactly what I have JUST found in this post by Svet: https://forum-en.msi.com/index.php?topic=127672.msg974800#msg974800
Yes it is 1.10 of course!! I didnt know that 1.10 = 1.A0 ! Thank you for the reply. Then the MSI live update 4 program is dump that he wanted from me another update of Bios.
So thank you! Problem is solved.
Edit: Yes, because of MSI live update I learned how to flash bios via flash disc. :-) But I was still confused by that 1.10 and of course by program saying me I should update again.. :-P
Quote from: Lostsoul777 on 14-August-09, 05:46:25
I had the same problem with 1.90 bios, so i updated to 1A, i just want to know why Bios Version says: v.1.10 instead v.1A?
Quote from: LinuxGuy on 29-December-09, 01:17:45
My computer does not have a floppy drive. How do I update the BIOS? (I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults. So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around). So either the BIOS is getting updated, but the online tool is not recognizing this or it's not getting updated. Either way, I would like to manually flash it in DOS. Is it safe to burn the setup files to CD and boot from CD into DOS?
That's the same BIOS version... Just the "MSI Live Updater" is not very smart...
H.A=H.10=17.A=17.10 [A=10, H=17], the last "0" suffix in H.A0 means its official version.
Quote
I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.
So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).
So ignore this MSI Live Updater's no sense, and stop flashing your BIOS. You already have the latest version installed.
The Tool now will detect and shows BIOS versions alias when the MSI BIOS version is known with more than one name.
So no more flashing and flashing and flashing to the same version because of MSI LiveUpdate suggest again BIOS update...
Also no more confusion:
"What's my BIOS version?" -> I flashed my BIOS to 1.A0 [A7520IMS.1A0], but BIOS says its 1.10
And MSI Live Update also says that i have 1.10 and 1.A0 is available and i should update it. I flashed it again, but its still 1.10?
What's going on?
Just run the MSIHQ USB Flash Tool and will show you all that you need to know
Examples[with real/accurate info]:
MSI Eclipse:
BIOS version 1.9:
BIOS version 1.10:[Tool now shows both BIOS versions alias]
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:30:55,34
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.9
BIOS Date: 09/22/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:37:25,66
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.A (aka Version: V1.10)
BIOS Date: 10/27/2009
More examples =>K9N6SGM-V / K9N6PGM-FI / K9N6PGM-F :
More examples =>945GCM5-F V2 (FSB 1333) :
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:47:34,35
Mainboard: MS-7267
PCB Version: 4.0
BIOS Version: VH.9 (aka Version: V17.9)
BIOS Date: 11/20/2008
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:52:46,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VH.A (aka Version: V17.10)
BIOS Date: 06/02/2009
More examples =>780GT-E63 [N/A at MSI web yet] :
For MSI Notebooks such decoding isn't need, examples:
* Add new feature "Triple BIOS flash Recovery Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
The feature include 3 auto prepared BIOS backups for followed purpose:
* Internal BIOS recovery:
- In a failure case Tool perform auto flash recovery [3 attempts, check for success after each and stop flashing if successful] before give control to BK_IO2, notice users about results and give control for manual attempts[if need]. [This a case if system isn't lockup/reboot, if bad flash occur]
- This mode also have own store up to 5 backups[+1, the last saved copy is always backup.bin, if there was older one they become backup1.bin .. till 5]
* BIOS backup stored as AMIBOOT.ROM [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
* BIOS backup detected and stored for M-Flash style boot/recovery [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
Performing test simulations with random generated BIOS versions[including betas] for M-Flash boot/recovery style, some examples:
Copy/paste Tool log file:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:00:53,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VD.XB2 (aka Version: V13.33B2)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.DX2
Where:
* V13.33B2 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VD.XB2 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.DX2 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:12:23,95
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VK.VB7 (aka Version: V20.31B7)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.KV7
Where:
* V20.31B7 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VK.VB7 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.KV7 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:18:34,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V3.9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.390
Where:
* V3.9 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.390 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:22:24,04
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V8.1B9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.819
Where:
* V8.1B9==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.819 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:25:38,51
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V4.E (aka Version: V4.14)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.4E0
Where:
* V4.14 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V4.E ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.4E0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:28:16,62
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V1.BB1 (aka Version: V1.11B1)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.1B1
Where:
* V1.11B1 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V1.BB1 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.1B1 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:31:57,78
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VI.FB5 (aka Version: V18.15B5)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.IF5
Where:
* V18.15B5 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VI.FB5 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.IF5 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:36:02,40
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V7.O (aka Version: V7.24)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.7O0
Where:
* V7.24 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V7.O ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.7O0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:39:11,84
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VC.8B6 (aka Version: V12.8B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.C86
Where:
* V12.8B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VC.8B6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.C86 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:49:38,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VG.PB6 (aka Version: V16.25B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.GP6
Where:
* V16.25B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VG.PB6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.GP6 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:53:17,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VU.H (aka Version: V30.17)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.UH0
Where:
* V30.17 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VU.H ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.UH0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]

How Can I Determine the Size of the 'My Documents' Folder for every user on a local machine using VBScript?

Hello,
I am at my wits end into this. Either I am doing it the wrong way or it is not possible.
Let me explain. I need a vb script for the following scenario:
1. The script is to run on multiple Windows 7 machines (32-Bit & 64-Bit alike).
2. These are shared workstation i.e. different users login to these machines from time to time.
3. The objective of this script is to traverse through each User Profile folder and get the size of the 'My Documents' folder within each User Profile folder. This information is to be written to a
.CSV file located at C:\Temp directory on the machine.
4. This script would be pushed to all workstations from SCCM. It would be configured to execute with
System Rights
I tried the script detailed at:
http://blogs.technet.com/b/heyscriptingguy/archive/2005/03/31/how-can-i-determine-the-size-of-the-my-documents-folder.aspx
Const MY_DOCUMENTS = &H5&
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objShell = CreateObject("Shell.Application")
Set objFolder = objShell.Namespace(MY_DOCUMENTS)
Set objFolderItem = objFolder.Self
strPath = objFolderItem.Path
Set objFolder = objFSO.GetFolder(strPath)
Wscript.Echo objFolder.Size
The Wscript.Echo objFolder.Size command in the script at the above mentioned link returned the value as
'0' (zero) for the current logged on user. Although the actual size was like 30 MB or so.
I then tried the script at:
http://www.experts-exchange.com/Programming/Languages/Visual_Basic/VB_Script/Q_27869829.html
This script returns the correct value but only for the current logged-on user.
Const blnShowErrors = False
' Set up filesystem object for usage
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objShell = CreateObject("WScript.Shell")
' Display desired folder sizes
Wscript.Echo "MyDocuments : " & FormatSize(FindFiles(objFSO.GetFolder(objShell.SpecialFolders("MyDocuments"))))
' Recursively tally the size of all files under a folder
' Protect against folders or files that are not accessible
Function FindFiles(objFolder)
On Error Resume Next
' List files
For Each objFile In objFolder.Files
On Error Resume Next
If Err.Number <> 0 Then ShowError "FindFiles:01", objFolder.Path
On Error Resume Next
FindFiles = FindFiles + objFile.Size
If Err.Number <> 0 Then ShowError "FindFiles:02", objFile.Path
Next
If Err.Number = 0 Then
' Recursively drill down into subfolder
For Each objSubFolder In objFolder.SubFolders
On Error Resume Next
If Err.Number <> 0 Then ShowError "FindFiles:04", objFolder.Path
FindFiles = FindFiles + FindFiles(objSubFolder)
If Err.Number <> 0 Then ShowError "FindFiles:05", objSubFolder.Path
Next
Else
ShowError "FindFiles:03", objFolder.Path
End If
End Function
' Function to format a number into typical size scales
Function FormatSize(iSize)
aLabel = Array("bytes", "KB", "MB", "GB", "TB")
For i = 0 to 4
If iSize > 1024 Then iSize = iSize / 1024 Else Exit For End If
Next
FormatSize = Round(iSize, 2) & " " & aLabel(i)
End Function
Sub ShowError(strLocation, strMessage)
If blnShowErrors Then
WScript.StdErr.WriteLine "==> ERROR at [" & strLocation & "]"
WScript.StdErr.WriteLine " Number:[" & Err.Number & "], Source:[" & Err.Source & "], Desc:[" & Err.Description & "]"
WScript.StdErr.WriteLine " " & strMessage
Err.Clear
End If
End Sub
The only part pending, is to achieve this for the 'My Documents' folder within each User Profile folder.
Is this possible?
Please help.

Here are a bunch of scripts to get folder size under all circumstances. Take your pick.
https://gallery.technet.microsoft.com/scriptcenter/site/search?query=get%20folder%20size&f%5B0%5D.Value=get%20folder%20size&f%5B0%5D.Type=SearchText&ac=2
¯\_(ツ)_/¯

Windows cannot load the user's profile but has logged you on with the default profile for the system.

My Windows 7 crashed a couple days ago after a windows update, I got this message.
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.
I restarted the machine and got this message
Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights.
DETAIL - The process cannot access the file because it is being used by another process. for C:\Users\TEMP\ntuser.dat
I checked the event Log I found these .
Windows cannot load the user's profile but has logged you on with the default profile for the system.
DETAIL - Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
Windows has backed up this user profile. Windows will automatically try to use the backup profile the next time this user logs on.
Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile.
DETAIL - The process cannot access the file because it is being used by another process.
This is the first error in the event viewer after a successful logon
The description for Event ID 34 from source ccSvcHst cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
ccSetMgr
Windows cannot load the user's profile but has logged you on with the default profile for the system.
DETAIL - Access is denied.
Looking at the Logs all I can tell is that after the Desktop Window Manager started if caused this error.
The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.
then this one
The Desktop Window Manager has exited with code (0x40010004)
Then this before it shutdown.
The User Profile Service has stopped.
I started up the PC and the first message I got was
How can I get access to my user profile? do I need to createa new Administrator account? Please help
The EventSystem sub system is suppressing duplicate event log entries for a duration of 86400 seconds. The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\EventSystem\EventLog.

hi do the following
1. In Search programs and files (Windows 7) area, type in regedit, and press Enter.
2. If prompted click yes,
3. expand the following HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
4. click the sid that related to your admin profile (if you not sure, click each sid and in turn look to the right hand side of registry editor it will show who that sid is related to one of the registry files should hae in description localhost\admin or
something similair)
5. right click the sid and press delete.
6. restart your machine and log back on with the admin account, this will then rebuild the admin profile... dont worry when it loads and none of your personal settings are saved or files or folders... go to c:\users
in here you will see two folders for the admin account, one will be just admin and the other most likely admin.localhost
i cant remember which one is which but just check both, one will still have all your files and folders in it.
i suggest making a backup of your data before doing this incase something does go wrong, but ive had this happen many times in a domain enviorment and has worked for me everytime.

IChat fails to connect in a user's profile

Someone in my office uses iChat to connect with AIM. We have verified the password and server settings as correct, but the program stalls with the message connecting.
I am able to connect to her AIM account using iChat under a different user's login for the the same machine. Any advice on how to get iChat working again withing this user's profile?

Hi,
I can do very little as to why MSN or Yahoo can not write an App for a Mac especially as the Processors are Intel based now.
I can point you to this User'S Tip http://discussions.apple.com/thread.jspa?threadID=1968438 about iChat to AIM.
It is in fact in the list of Recent User's Tips at the head of the forum.
I can assure you the .plists are in Hard Drive/Users/(your Account)/Library/Preferences (as in ~/Library/Preferences or Home Folder/Library/Preferences or Little House Icon/Library/Preferences)
8:12 PM Tuesday; August 18, 2009
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Solution Manager 4.0 Solution Monitoring User -Roles-Profiles for Satellite

Hi All,
I have installed Solution Manager 4.0 (OS -Linux ,Database - DB2) .
Now i need to connect solution manager to the R/3 4.6C
Satellite Systems (DEV, QAS ,PRD) for Solution Monitoring
and Service level Reporting .
I have read the configuration guide , but unable to get clear idea .
1) what users (alos type of user -Dialog , Service, Communication etc) do i need create in DEV , and Test in QAS for solution Monitoring .
2) what exact roles /profiles need to be assigned to these users in satellite systems .
3) what users/roles /profiles needs to be done in SOLMAN system
i have applied all the required plug ins and support packs
in satellite systems and solman 40 ..
Please advice . Your response will be a great help for me .
Satish

Hello Satish,
Just clarify, if u have meant connecting the satellite systems for EWA reports to be precise. Early watch Reports. If its is the case, then repond so that i can putin my inputs which may be helpful for you in this config.
Rgds,
Sri

Clean install from a Lenovo installa. dvd: UEFI vs Legacy + Thinkpad setup acc. to Lenovo user Guide

Machine: T520 bought Feb. 2012
O.S. W~7 Pro 64-bit
I want to wipe the harddrive, buy a Lenovo W~7 PRO installation DVD, and do a completely clean installation.
Lenovo User Guide (.pdf) Ch. 8, Adv'd Config, Installing Windows 7, p. 295 (212 of 298) says:
Start Thinkpad setup, then choose UEFI versus Legacy, then insert the installation DVD.
This obviously does not apply when the harddrive has already been wiped (necessary to 100% eliminate all traces of irreversible damage caused by a virus, including the re-installation partition (Q-drive).
When an intallation DVD is purchased from Lenovo, is not the first step to insert the DVD ?!! Then presumably there is an installation wizard resulting in a restored O.S. ?!!
If not, please tell me what surprises are in store, and where I can find a reliable written resource to consult !!!
Thank-you.
Solved!
Go to Solution.

You're over-thinking this and making it harder than it needs to be. The manual isn't helping...
The BIOS is stored in non-volatile memory on the motherboard. One would probably call it firmware, not software. It is there regardless of what's on the HDD - or whether there's even an HDD installed.
Turn your machine off. Turn it on again. When you see the logo screen, hit F1 - multiple times if necessary. That gets you into the motherboard's BIOS configuration utility - what the manual is calling "Setup".
Here's a snip below from the T520 BIOS configuration utility (actually from the on-line BIOS simulator). In the StartUp tab you can see where UEFI/Legacy can be selected. You can configure UEFI boot there. Or "both". Or - probably - just select Setup Defaults, save, and exit.
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Open another users exchange profile

In exchange 2007 which we are migrating from, I could log into my workstation with my domain admin account, create a new outlook profile and open up any users mailbox because I have rights to them. This is useful when troubleshooting outlook issues
for users I cannot remote.
Now in exchange 2013, I have to find the users mailbox guid, use it for the servename and set the outlook anywhere settings for it to resolve the username. But even after that, when I try to open the outlook profile (under my login) it still is prompting
for username/password. Is it possible in Exchange 2013 to open another users outlook profile like I could in Exchange 2007?

Hi,
According to your description, there is credential issue when you open Outlook with your own account configured. If I misunderstand your meaning, please feel free to let me know.
If yes, I’d like to explain, different from Exchange 2007, all Outlook clients in Exchange 2013 use Outlook Anywhere. And the credential may be caused by the improper Authentication method.
Thus, let’s check if all users come across the same issue.
If yes, we can firstly check the authentication by running the following command:
Get-outlookanywhere |fl
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

In Service Orders - Adding addition status in User Status Profile

Hi Guyds,
I have a question.
Customer have a requirement where, in repair process when they receive the defective device (equipment) thru return delivery they want to put the device in contamination. And once the contamination is done they want to stage the device for repair. They are asking how can this requirement be met or mapped in SAP system? I suggested we can define additional user statuses in user status profile. Like when the device is received the user can manually set the user status as "Put to decontamination" status in service order. And once the decontamination is complete, then user can manually set another user status as "Decontamination complete" (just as an example). Customer has agreed with this suggestion.
Now, my question is I can meet this requirement by adding addtional statuses to the user profile and then assigning the user profile to service order right? And as customer has agreed that user will have to manually set these statuses in service order, so customizing/configuring the status profile should suffice right? Or do I have to perform any enhancement? Please advice but remember that the customer has agreed to setting the user status manually, automation is not required. So, in this case do I still have to go for any enhancement to meet this requirement or can I do it just by defining extra statuses in user status profile.
Please guide me. Appreciate your help.
If you have any questions or need any clarifications, please let me know.
Best regards,
Abdul Rafey

Hi
As you correctly pointed out user status will be straight answer. there is no enhancement required. you have to create the user status and assign the same for the order type .
also you can automate to some extent ex while order created you can make the "Put to decontamination" as initial and while releasing the order you can automate that "device for repair" will be set on releasing
regards
thyagarajan

Printable User Guide

Maybe I'm odd, but I am extremely uncomfortable reading a 200+ page PDF document at my computer, so of course I tried to print out sections of the User Guide so that I could actually read them. However, the User Guide has a weird page size and it won't print right. I tried printing it from Preview, and after suffering defeat, moved the PDF file to a Windows machine and tried printing it from Adobe Acrobat 7. It has completely defeated me.
The User Guide is too huge to be a PDF. Is there a printable version with standard-sized pages? Or is it available in print form? I would like to read this document.
iMac Mac OS X (10.4)

It's hard to answer definitively, since printers and drivers may differ.
However the PDF is set up for printing on A5, single sided (all the margins are on the left). I've tried it on a Canon iP90 and it works fine. You may wish to adjust for fine print and special effects if your driver has them - but be prepared to spend a bit of ink.
There is a scaling option in Preview Preferences, too, which you may need to check. 100% works for A5 with this file, but if you'd prefer A4 try 200%, or you may consider using your printer's scaling option as an alternative (mine has "scale to paper size" as an option).
The iP90 also has an option to reset the margins for two sided printing with a booklet stapled left (though you have to print odd pages first and turn them over for the evens. You may care to experiment with the equivalent, if you have it on your printers. I'll only be running the pages I need to for reference to the new features of Pages 2 myself. Otherwise it's a pretty long job, even for a laser.
And no, you're not odd. Why would anyone buy Pages if they didn't want hard copy? Computers will never obsolete books, they only help us write them.
I suggest you also provide feedback to the Pages team. The guide should come as a booklet with the package. You want it when your computer's busy!
Cheers.
iBook G4 Mac OS X (10.4.4)

Sharing a folder with other users on the same machine (SOLVED)

Hi,
Recently, I've been sharing my computer with my dad. I don't want him to use my account, since I have a lot of secret files and bookmarks on my profile. However, I would like to share all my music with him. What I did was to set the permission of my Music directory to 777 and using root create a symbolic link from my own account to his account. But then when I log into his account, it says the folder is corrupt.
Then I created a symbolic link from my music directory to /media/ and set the permission to 777. Again I tried to see if I can access it from my dad's account and got the same error.
What's the best way of creating common folders between users in a linux machine?
Note that, since I use Amarok, I don't want to move my Music to somewhere else, because it will mess up with the database info of songs.
EDIT: I solved the problem by using mount instead of symbolic links.
You have to issue the following command:
mount --bind /home/name/music /media/music/
Of course you have to execute this command whenever you boot the computer. Just place this command in rc.local and you're good.
Thanks
Last edited by mohtasham1983 (2009-11-05 22:06:03)

grey wrote:If I wanted to share it between different users, I wouldn't put it inside one particular users home directory. Just use a reasonable place that is not used by the system, like /usr/local/data, /var/shared or so, give it the desired permissions and that's it.
you are absolutely right and i recommend this as well.
grey wrote:The link will probably not work, because in order to read /home/yourname/music, you need to be able to read /home/yourname. That is even true if root created the link.
that is true for symbolic links, not bind mounts. a bind mounted dir doesn't care about the parent directories because your not traversing to it through a link, it's just 'there'. this is how i put folders under my ~ out on my http server.

U110 user guide - Profile your machine

Similar Messages

Maybe you are looking for