IS-Retail Guide

Hi Friends,
Can any give me some pointers , where I can get help Related SAP Retail?
Please reply me ...it is urgent.
I will prefer some e-books if I can get online.
Thanks a lot for giving your valuable time to me.
Regards,
Rajwant.

Hi
Please refer to the link below
http://help.sap.com/saphelp_47x200/helpdata/en/50/94f500470e11d1894a0000e8323352/frameset.htm
Raghu

Similar Messages

  • HT3777 I have a Window 7 HP laptop. I want to install Snow Leopard on an external hard drive as the memory space on my laptop is very less. I have the original snow leopard disc and I think it's a retail version . Please guide me through the installation.

    I have a Window 7 HP laptop. I want to install Snow Leopard on an external hard drive as the memory space on my laptop is very less. I have the original snow leopard disc and I think it's a retail version . Please guide me through the installation in details. Can you also please let me know about this boot camp.

    You cannot. From a legal standpoint, the license agreement for OS X mandates that you run OS X only on Apple hardware. HP is not (yet) owned by Apple.
    From a technical standpoint, your HP laptop doesn't use EFI, but rather an early predecessor called a BIOS. Apple is the only vendor of consumer computer hardware that uses EFI; other vendors reserve EFI for use in servers.
    Secondly, Apple's operating systems support a rather limited number of configurations of video hardware and mainboard chipsets directly since they need only support those systems that they manufacture. You cannot use Windows software or drivers on OS X, so prior to installation, you would need to write your own hardware drivers for your laptop, create an OS X drive image on a Mac, and then modify that image with your drivers before putting it in the HP.
    It will be simpler (and legal), to simply purchase a used Mac. Apple's online store has refurbished MacBook Airs starting at $850 and Mac Minis for $700. If you go to e-bay or craigslist, you'll find used Macs for considerably less.

  • Locate Quick Guide for installing Retail

    I am following a SAP Best Practice (Building Block Configuration Guide ) but I am unable to obtain the Quick Guide for installing Retail located on the DVD in Retail_US\Documentation\Retail_Quick_Guide_EN_US_V1603.doc
    Our DVD has been damaged,  I have been looking on SERVICE Market place etc but can not find it. If it is there THEN please help me locate it and I will get it from there.

    Hi Jack,
    Good news for you.
    Please login to SAP Marketplace
    And search for the SAP note: 1242830
    In the attachments, you will find your file "Retail_Quick_Guide_EN_US_V1603.doc" in .zip format.
    Right click and save.
    It will solve your purpose.
    Else you may have it from me.
    Take Care
    Regards,
    Anirban Roy

  • ,Retail Integration Customization Process/Guide/Techniques

    How can i get the information on the Retail Customization techniques.As what ever the document available in the Oracle site mostly deals about the whole rib.
    I just want some information/standard process or steps to customize the RIB (like RIB for RMS,SIM etc ) for different customers.
    If some one could help it will be great.
    Thanks in Advance,
    Edited by: user11095621 on May 7, 2009 4:29 PM

    Yes, I know the process that you describe.
    The RIB did not fulfill our integration requirements on a few points:
    - not all needed message types and/or details are being published.
    (An Oracle Retail senior consultant said to me that if we were missing information in the RIB, we had to reconsider our integration requirements, as they where likely to be not a valid retail scenario...)
    - it is a publish/subscribe mechanism (JMS), while we also need request/response type integration (RSL provides something like this but has quite a short list of services and is also focused quite on the Oracle Retail internal architecture).
    - it is not an ESB
    (Now when you also purchase the BI Publisher option to the Oracle Application server for the Oracle Retail operational report, you need the Enterprise Edition of the OAS to be allowed to buy that OAS BIP option, and the OAS-EE comes wth the Oracle ESB (at least before the BEA acquisition) - we chose however for a different ESB, Progress Sonic.
    - the RIB message model (any source specific datamodel) is not a valid source for a true canonical data model, as the enterprise canonical encompasses more attributes and business objects.
    - the level of documentation on customization can be improved
    We do not consult the database directly, in the sense that we build a plsql package with some custom functions, e.g. f_get_season_for_item(i_item_nr), and wrap them with Java and OC4J as a SOAP webservice (using the JPublisher framework). See it like this, we wrapped the database in a custom integration layer, the ESB processes interact with that custom layer, and in case of upgrade of RMS, we need to re-fit the integration wrapper, limiting the impact of the upgrade to there (except for some bigger changes) and hopefully not impacting the ESB processes.
    Of course this approach is also not ideal - but we wanted the RIB to stay vanilla and blackbox. But integration is not ideal ever - especially when for a message or service based integration architecture you need to rely on the messages and services that the application vendor has provided. Oracle Retail is the best in that respect, our other ERP/OLTP systems up to now do not do anything with SOAP/JMS.
    Additionally we have a different messaging system that is the core of our enterprise integration (Progress Sonic MQ), and RIB is just one of the several sources/targets for that system. Other systems post to the Sonic MQ - that is our core integration bus. Where possible we post back to the RIB from our ESB processes.
    We are also building more classical integration using Oracle Warehouse Builder and PLSQL to create flatfiles and create custom batches - directly accessing the RMS data model - there is just no other solution. (We have decided to ban custom Pro*C, and use PLSQL and OWB where needed - yes OWB also for non-ETL style processes - OWB has a great advantage over PLSQL: you generate code and you don't write code, and it comes with the database license.)
    And then we also have to fill our RDW and Corporate Datawarehouse - but that's a whole other piece of cake.
    PS: what is the ESB that you use?
    Regards,
    Erik

  • 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]

  • Neo4 Overclocking Guide

    This guide is intended to help those people who have K8N Neo4 (nforce 4 based) boards.  It will provide some general background information, but a lot of things will be specific to this particular series of motherboards, and in general it is assumed that the user is at least moderately familiar with the basic concepts of computer hardware and the concepts and risks associated with overclocking.  As usual, I am in no way responsible for any losses/damages resulting in whole or in part from the use or misuse of this information, or in short, "overclock at your own risk".  It should also be noted that I have the Neo4 Platinum, so things might be slightly different for those of you with the SLI or other variants of this board, though I would strongly suspect that most of the overclocking features will be pretty much the same.  Anyways:
    The Basics:
    Okay, for those of you who are new to the overclocking crowd, here is a quick overview of some of the essential bits of knowledge.  A very complete and thorough introduction and general overclocking guide is also available at https://forum-en.msi.com/index.php?topic=40413.0 for those of you who need extra help.
    CPU Speed - If you don't know what this is, then I wonder what you were hoping to attain by accessing an article about "overclocking".  The main aim of overclocking is to increase the CPU speed beyond what it is originally specified to run at.  The CPU speed is equivalent to the product of your FSB speed and the CPU multiplier.
    FSB - FSB is short for "frontside bus".  Historically the FSB essentially controls the speed at which the CPU is able to communicate with the rest of the system, and this is pretty much still true for the Athlon64, although the impact of higher FSB speeds is somewhat diminished, as we will see later.  On the Neo4 (and most any other board) the FSB and various multipliers/dividers are responsible for determining the core CPU speed, the memory speed, and the HTT speed.  You PCI-E bus is locked, so raising the FSB will not cause your video card and other devices to become unstable.  Additionally, there is no need to worry about an overclocked FSB screwing up the built-in SATA/IDE controller (the nforce one at least, I haven't tested the SiL, although it should be fine as well).
    HTT - HTT (or sometimes just HT) is short for "HyperTransport Technology".  Not to be confused with the HyperThreading feature on Intel's P4 processors, this is the communication link between an Athlon64 processor and the PCI-E bus, as well as everything that hangs off this bus, including the SATA/IDE controllers and so on.  Basically, everything except for the RAM talks to the CPU via the HTT bus.  The speed of the HTT bus is determined by taking the product of the FSB speed and the HyperTransport multiplier, and it provides an extremely large amount of potential throughput, so much so that once its speed is above about 800 MHz, there's very little to be gained by pushing the HTT speed higher.
    Memory Clock - The memory clock refers to the speed at which the RAM modules are operated.  The memory clock is determined by taking the FSB and applying a ratio to it.  Generally speaking, a higher memory clock is better, although there are tradeoffs in terms of latency if memory timings (CAS latency, etc.) have to be loosened in order to get the memory clock higher, or if a ratio other than 1:1 is used (which will be necessary for high overclocks unless the RAM you are using is of extremely high quality).
    PCI-E - The PCI-Express bus.  This provides connectivity for your graphics card(s) and other add-in cards.  The default PCI-E speed is 100 MHz, and this is locked on the Neo4 so that increasing the FSB does not increase the PCI-E speed.  You may manually increase the PCI-E speed if you wish, although this is not at all recommended.
    vcore - This is an abbreviated way of referring to the voltage that is applied to the CPU.  Generally speaking, a higher vcore will provide stability at higher clock speeds, the tradeoff being additional heat, which may or may not require a more robust cooling solution, depending on how high the vcore is being pushed, the quality of your thermal interface compound, and the thermal characteristics of your individual CPU (some just overclock better than others).  For the 90 nm Athlon64, the default vcore is 1.40V.  The default is slightly higher for the 130 nm variants.
    vmem - Similar to "vcore", this is a shorthand way of referring to the voltage that is currently being applied to the RAM modules.  Again, an elevated vmem will generally give you improved stability at higher memory clock speeds.  Memory specifications vary from manufacturer to manufacturer in terms of what voltages are supported (for instance, my RAM supports from 2.55V to 2.95V), though the default voltage is usually 2.65V.  Vmem, vdimm, and vram all refer to the same thing.
    Purchasing:
    For anyone who happens to stumble across this guide while in the process of looking for some new hardware, I thought I'd list some of the things that are important considerations when you are buying a system with the intent of overclocking it.
    The CPU - For most people, the main point behind their desire to overclock is that they want to be able to get a cheap CPU, and then run it at the same speed (or faster than) of a CPU that costs much more (possibly one for which the price premium has not come down on yet).  When choosing which CPU to purchase, there are a few aspects that are especially relevant to overclocking (I'm going to assume that you've already decided to use an AMD CPU, due to the reduced overclockability, thermal problems, and generally poorer performance in most areas despite having higher raw clock speeds that all of Intel's current P4 models offer).  Arguably the most important feature (when looking at the current Athlon64's anyways, which are very good CPU's and which you have to use if you want the Neo4) is the manufacturing process used.  This denotes the size of the smallest individual feature on the chip (smaller is better).  Your two choices right now are 90 nm and 130 nm.  The 90 nm carries a fairly small price premium (about $10 for the 3000+/3200+ models), but is *much* more overclockable due to the fact that it operates at a lower voltage (and thus generates less heat), and also uses a more "mature" revision than the 130 nm parts.  It is *strongly* recommended that you make sure to get a 90 nm CPU if you are in the market for a new socket 939 Athlon64.  The next thing to consider is the default CPU multiplier.  This is the one reason why it might be preferable to get a 3200+ over a 3000+ chip (generally speaking, all the 90 nm Athlon64's have about the same upper limit on their overclocked core speeds, until you hit the still very expensive 3800+ and FX variants, so it doesn't make sense to buy a more expensive CPU when you're not getting any extra overclockability out of it).  The multipliers on the Athlon64 CPU's are "half-locked", meaning that you can run at the default multiplier (9x for the 3000+, 10x for the 3200+), or any multiplier that is smaller than the default, but you cannot select a multiplier that is higher than your default multiplier.  Thus, getting the 3200+ over the 3000+ gives you two extra multipliers (10x and 9.5x) and, all things being equal, will let you achieve a higher clock speed before you are forced to run your RAM asynchronously and pay the latency penalty for doing so, although your max clock speed will likely be about the same as it would if you had gotten the 3000+ instead (so if you have cheap RAM that's not giong to overclock well at all, there's very little reason to go with the 3200+ unless a RAM upgrade is planned in the near future).  So, for overclocking purposes my recommendation is a 90 nm Socket 939 Athlon64 3000+, or if you have high performance memory and want to get the most out of it, the 3200+.  Both chips are competitively priced and should overclock at least to 2.4 GHz, if not higher, on stock cooling (spend the extra $10 for the non-OEM variant and get the HSF that comes with the chip, it works as well as many more expensive third-party air-based systems and is well worth the extra $10), and of course both offer the attractive feature-set of a socket 939 Athlon64 (dual integrated memory controllers, 64-bit support, dual-core processors on the future upgrade path, etc.).
    The Motherboard - The motherboard is an important part of overclocking as well.  There's not much point in getting a highly overclockable CPU and then pairing it with a mainboard that was not designed with overclocking in mind, and this is one area where the Neo4 really shines...it has superb overclocking support.  Probably the most important feature to have if you indend to overclock your CPU by 20%+ (which should be easily attainable on either of the recommended CPU's above) is that the board have locks that prevent the overclocked FSB from overclocking parts of the system that can't handle the extra speed (like the PCI/PCI-E bus, for example), and long story short, the Neo4 has these (unlike the Via-based K8T Neo, which had no locks and which limited SATA users to overclocks of no more than about 225 MHz because any high than that and the SATA controllers would start to become unstable and kill your HDD data...working locks are a very good and important thing if you are overclocking).  The next important feature is to choose a board whose BIOS lets you control the options that are important for overclocking.  Again, the Neo4 does excellent here, letting you pick your memory divider, memory timings (and some very obscure ones at that), CPU multiplier, FSB speed, HTT multiplier, CPU voltage, chipset voltage, RAM voltage, and so on without complaint.  The MB also has a handly little button on it that will clear the CMOS with a single press (no more screwing around with those annoying jumpers) in case you screw up and the system won't POST.  The board also has some extra cooling hardware installed in the form of a passive heatsink near the rear I/O panel, but mostly it's the presence of functional locks and the wide range over overclocking related BIOS features that make it attractive from an overclocking perspective.  Aside from this, it has a very nice feature set in general, including 8 SATA ports and 2 IDE channels (for a total of up to 12 drives), two gigabit ethernet adapters, firewire, 7.1 channel audio, and the additional selling point that nvidia's unified drivers tend to be much easier to install than most companies' drivers.
    Cooling:
    Okay, one last thing to consider before the overclocking starts.  Cooling is important in general and especially if you are going to be overclocking.  While a 90 nm Athlon64 performs rather admirably from a thermal perspective even when only stock cooling components are used, some simple modifications can drop your idle/load temps by 5+ degrees, which can give you a bit more overclocking headroom and which in any event will make your CPU happier. 
    Case Fans - The first thing you want to do is make sure your case is adequately ventilated...in general a single 120 mm exhaust fan will do the job just fine.  If your case does not support fans this large, use at least two 80 mm fans, either both as exhaust, or one as exhaust and one as intake (if they perform differently, use the more powerful one as the exhaust fan to avoid overpressuring your case).  If noise is a concern, the Vantec Stealth (http://www.newegg.com/app/ViewProductDesc.asp?description=11-999-614&depa=1) series of case fans are affordable, come in a variety of sizes, perform quite well, and do not make much noise at all (though you might want to consider doubling up on the 120 mm's just to be on the safe side).  This can lower your CPU temp by about 2 to 5 degrees over a poorly ventilated case configuration using the same CPU fan.
    CPU Fan - As I mentioned earlier, the default CPU fan that comes packaged with the retail Athlon64 chips is perfectly acceptable for overclocking use in my opinion.  The only complaint I have is that the thermal compound that comes preapplied to the HSF is fairly cheap and does not perform that well.  I *very strongly* recommend replacing it with Arctic Silver (http://www.arcticsilver.com/as5.htm) before ever installing it on your CPU.  To remove the default thermal pad, you can use a razor blade to get most of it off, and then hot soapy water (or denatured alcohol I've heard) to remove any remaining reside.  Be sure that the HSF is free of any cleaning residue and also of any moisture before going to install it on the CPU, and then just apply the Arctic Silver and then complete the HSF installation, and you're good to go.  Arctic Silver is relatively cheap (the tube you'll get will do several CPU's, and it doesn't go bad), and by replacing the thermal pad that comes on the stock HSF with it, you should be able to reduce your idle/load times by at least 5 degrees, and with this plus the added reduction you get from having a well ventilated case, you should have enough headroom to pull off some pretty aggressive overclocks.
    Overclocking:
    Finally, on to the good (and Neo4 specific) stuff.  Hopefully at this point you have a freshly built Neo4 based system with an Athlon64 CPU that provides a large headroom for overclocking.
    Initial Setup - Okay, the first thing you're going to want to do once the system is built and powered on for the first time is enter the BIOS and configure everything to run at its *default* settings.  It's not quite time to overclock yet.  First, you want to install Windows, patch it to SP2 if necessary, and then install some benchmarking, stress testing, and monitoring software.  SiSoft Sandra is a good benchmark suite, as are FutureMark's PCMark and 3dMark lines of software.  For stress testing you can use SuperPi and Prime95 (and Memtest86 if you don't mind the tedium of having to reboot in order to use it, which I do so I don't bother with it).  For monitoring you can use SpeedFan or Motherboard Monitor 5.  At the very least you should install one application from each category, and configure your monitoring software to launch when Windows loads.  One you have all this configured and working right, it's time to start overclocking (don't install too much else, in case of the worst case scenario in which an instability causes your HDD to become corrupted, requiring a reinstall of Windows and all the software, which is admittedly very unlikely, but unfortunately possible if you're unlucky enough).  For comparison purposes you may want to run some benchmarks and record the results before you start.  Additionally, you may want to install something like ClockGen, which will let you tweak your FSB/CPU coltage on the fly and which can make it easier to zero in on a stable configuration without having to reboot every time an instability is found.
    BIOS Layout - Just to save some time, I'll describe where BIOS options that we'll be using are all in one place, so that when I reference something you can just look up here and figure out how to find the appropriate setting in the BIOS.  Basically, there are two pages that we're interested in for overclocking (note that the Neo4 manual is actually extremely well done, and describes pretty much all of the BIOS options, so you can use it as well).  The first is the "Advanced Chipset Features" page.  Going "Advanced Chipset Features" -> "DRAM Configuration" brings up pretty much all of your memory related options (divider, timings, etc.), *except* for the RAM voltage.  The RAM voltage option is on the "Cell Menu" page, which happens to also contain all the other settings we are interested in, including FSB speed, HTT multiplier, CPU multiplier, vcore, vmem, chipset voltage, etc..  Basically, if it's not memory related, it's on the "Cell Menu" page.
    HTT Speed - As mentioned earlier, your HTT speed pretty much has no performance impact on the system once it gets to 800+ MHz, so the very first thing you can do is select the 4x HTT multiplier in the BIOS.  Note that as the HTT speed gets above about 1100 MHz, it will probably start to make the system unstable.  Therefore, you should keep track of the product of your FSB setting and your HTT multiplier, and whenever it gets to be above 1100, decrement the HTT multiplier to the next lowest setting.  at a 4x multiplier, you should be good up to about 275 MHz on your FSB.  Because the HTT's impact on performance is negligible, you do not need to worry about trying to maximize its value during overclocking.
    CPU speed - Onve you've reduced your HTT multiplier, it's time to find your max stable core speed.  To do this first go to the memory page and select a memclock index of 100 MHz.  This will run your RAM it half the FSB speed, and the reason for doing this is to ensure that as we raise the FSB, any instability the occurs is a result of the overclocked CPU and not a result of overclocked RAM, so that we can be sure that we have indeed found the maximum stable CPU speed when we are done.  Leave your other RAM settings at their defaults, we'll come back and tweak these later.  Now go to the CPU page and select "Manual" for the "High Performance Mode" option if necessary to enable editing of the settings.  You should disable Dynamic Overclocking (since you are doing this manually) and I recommend disabling Cool'n'Quiet, though you don't have to if you really don't want to.  Disable all the "... Spectrum" settings (what these do is kind of complicated, but the manual plainly states that they should be disabled if you are overclocking, so heed its advice).  Also disable "Aggressive Timing", as this will decrease your RAM overclockability substantially without providing any real benefit (and may make it unstable even at its rated settings).  Now, what you want to do is, leaving the other CPU settings (i.e. vcore and multiplier) the same, start raising your FSB Frequency in 10 to 12 MHz increments, depending on your multiplier (basically you want to raise it about 100 MHz at a time).  Some people feel this is a fairly large jump to do at a time, but I've found that the Athlon64 handles it just fine.  If you get up above about 2.4 GHz, then you might want to only go by half of this at a time though.  Remember to decrement your HTT multiplier as necessary.  Basically, every time you raise the FSB, test for stability by letting the system try to boot to Windows.  If it is successful, return to BIOS and raise the core speed some more.  Once the system fails to boot, you have two options, either raise the CPU voltage (use the "CPU VID" setting in the BIOS to adjust the voltage directly, or the "CPU Voltage" setting to specify how much over the specified amount of voltage to apply...personally I prefer the "CPU VID" route, but it's really a matter of personal preference, and yes, both can be manipulated in unison...one thing I've noticed here is that the "CPU Voltage" settings seem to allow for less variance in the final vcore setting, keeping it very close to the specified voltage at all times, whereas increasing via the "CPU VID" option lets the voltage decrease a bit from the specified value when the system is not under load) and try again (and keep repeating until you have given the CPU as much voltage as you are comfortable with and the system can no longer be made stable), or return to you last stable setting and let it boot.  Once you have done this, use your benchmarking and stress testing software to make sure you really are stable at your settings.  If the system crashes or the test reports errors, you will either need to raise the voltage a little, or lower the FSB a little (this is where ClockGen can be a big timesaver).  While some people swear by Prime95, my opinion is that if you can get through the largest SuperPi test without any errors, your overclock is stable.  Monitor your temps while you do this.  If you notice that the CPU temperature is getting above 60 degrees, you are running a bit too hot.  Generally speaking, about 55 should be considered the threshold of safety here.  If you're running hot, you can either decrease the voltage and FSB settings, or get a better cooling solution.  Once you have determined that your setting is stable and not overheating your CPU, record your core speed (not your FSB speed, the total CPU speed) and voltage settings for later.  You should probably be shooting for a target clock speed of around 2.4 GHz, or more if you have good cooling, or if you are interested in doing a "safe" overclock, just shoot for as high as you can get without raising the voltage.
    Memory Speed - Now that you know your CPU's limits, it's time to work on the RAM.  First restore your FSB to 200 MHz and your CPU voltage to its default, and specify a CPU multiplier of 6x to make sure that the CPU will not be stressed as your raise the FSB.  Go to your RAM page, and manually specify whatever timings are appropriate to your RAM modules.  Also be sure to set "1T/2T Memory Timing" to 1T (set the "... Mode" setting to Manual to make the RAM settings editable).  Leave the rest of the settings alone, except for the "Memclock Index Value".  Here, you have a choice to make.  If you have high quality RAM, or your target CPU speed is not too high (like < 2.3 GHz), you can try to run your RAM synchronously, which will give you somewhat better latency.  If this is the case, select an index value of 200 MHz (note that on the Neo4, when you select a memclock index what you are really specifying in the ratio at which the RAM operates relative to the FSB...the memclock index option is basically just obscuring this setting.  To calculate your ratio, divide whatever the index value is by 200, so an index of 200 MHz is a 1:1 ratio, an index of 150 MHz is a 3:4 ratio, and so on).  If your RAM is not of very high quality (for example, it's only rated as PC3200), or your target CPU speed is high, you will likely need to run the RAM asynchronously, so select the next highest index value of 180 MHz.  This will let you get slightly higher RAM clock speeds, at the cost of a little bit of added latency (the performance hit isn't much...you'll be much faster running asynch at 2.4 GHz than synch at 2.2 GHz).  Now you do the same thing that you did with the CPU, gradually increasing the FSB (you might want to use smaller increments this time though) until the system will no longer boot (remember again to decrease the HTT multiplier if necessary), and then returning to your last stable setting (or increasing the voltage and repeating) and booting to Windows and running stability tests.  You do not need to monitor your temps while doing the RAM tests (unless you want to).  Generally I find that Sandra's "Cache and Memory..." benchmark works well for detecting memory instability, and you can also use SuperPi, Prime95, or Memtest86 as well.  Once you have tested stable, record your memory clock speed (use the formula:  memory speed = FSB speed * memclock index value / 200) and voltage and reboot to the BIOS settings menu.  Note that while you may be able to attain a higher memory clock speed by selecting a higher CAS latency, it is not generally advisible to do so, as from what I've seen, although memory bandwidth remains about the same as CAS increases (as far as Sandra is concerned anyways), the lower latency provided by CAS2 improves the system score by 5% in PCMark 04, and given that RAM performance scales pretty much linearly relative to the clock speed, unless running at CL2.5 lets you get *at least* 10 to 15 MHz higher than at CL2, it is not worth it overall.
    Run the Numbers - Believe it or not the performance of the Neo4 system is dictacted pretty much entirely by the core and memory clock speeds (given identical memory timing settings).  The only other real factor is whether the RAM is run synchronously or not, which you just decided in the above step, so all that's left to do now is find the combination of memclock index, FSB, and CPU multiplier that allow you to get as clost to both your target core and memory speeds as possible.  If you are running synchronously, your task is simple, just keep your memclock index of 200 MHz, specify your target FSB speed, and your default CPU multiplier (unless your RAM is so good that the CPU is not stable at the default multiplier and the RAM's top FSB speed, in which case drop the multiplier accordingly).  If running the RAM asynchronously your task is a bit more difficult (having a calculator for this part will help), basically you have to go through the list of memory dividers (memclock indexes), and for each one calculate the ratio of memclock index / 200, and then divide your target memory clock speed by that ratio to get the FSB needed to attain your target memory speed (for example, if the target is 230 MHz, for a memclock index of 150 we get a ratio of 0.75, and 230 / 0.75 = 307 MHz, so running the RAM at 230 MHz with an index of 150 MHz requires a FSB setting of 307 MHz...pretty good if your target clockspeed is 2.45 GHz, as selecting an 8x multiplier will pretty much hit this exactly), and then go through the available *whole* CPU multipliers (I've heard that the half-multipliers should be avoided, as they cause the memory to get clocked incorrectly) and see if any multiplier times the FSB you calculated hits (or comes reasonably close to hitting) your target CPU speed.  Go through all of them until you get an exact (or very close) match, and pick whichever one ends up matching most closely.  Note that there is no benefit in this case to a higher FSB speed configuration over a lower FSB speed configuration, provided that both produce the same core and memory clock values, so you should not favor configurations with needlessly high FSB settings unless they produce a better fit than the others.  Apply whichever settings are closest, and then apply the appropriate CPU and memory voltage settings that you got from the previous steps.  Also apply whichever HTT multiplier will put you closest to 1000 MHz without going over 1100 MHz.  After this, your system should be ready to boot, overclocked and stable.  Be sure to do additional benchmarking and stress testing to make sure that you really are stable (if you saved your scores at the beginning, compare them to your scores now and marvel at the improvement...and post the results for people to see), and be sure to monitor your temps for a bit to make sure your cooling is working adequately.
    Post Overclock Overclocking:
    There's not a whole lot to do now, but if you want to try to tweak your memory timings to get a little bit of extra performance, now is the time to do it...just remember to record your stable overclock settings somewhere (*not* on the computer) in case the tweaking forces a CMOS reset and you lose all your settings, and enjoy.  Also you can overclock whatever video card you have, a process that's much easier and faster than overclocking your CPU/RAM/FSB.
    In Closing:
    I hope someone out there finds this useful, given how long it took to write up.  Maybe I'll get lucky and this will end up as a sticky...we'll see.  And just to start things off, here are my benchmark scores, at stock and at the overclock described in my sig:
    Stock:
    3dMark05 = 3141
    PCMark04 = 3589
    Overclocked:
    3dMark05 = 3704
    PCMark = 4805
     

    Just started ocing the system, I'm new at this so these are where my system stands and the results
                                  --------[ EVEREST Home Edition (c) 2003-2005 Lavalys, Inc. ]------------------------------------------------------------
        Version                                           EVEREST v2.20.405
        Homepage                                          http://www.lavalys.com/
        Report Type                                       Report Wizard
        Computer                                          HOWARD-4B304E62
        Generator                                         Howard
        Operating System                                  Microsoft Windows XP Home Edition 5.1.2600 (WinXP Retail)
        Date                                              2005-09-16
        Time                                              16:14
    --------[ Overclock ]---------------------------------------------------------------------------------------------------
        CPU Properties:
          CPU Type                                          AMD Athlon 64
          CPU Alias                                         Venice S939
          CPU Stepping                                      DH-E3
          CPUID CPU Name                                    AMD Athlon(tm) 64 Processor 3000+
          CPUID Revision                                    00020FF0h
        CPU Speed:
          CPU Clock                                         2456.56 MHz
          CPU Multiplier                                    9.0x
          CPU FSB                                           272.95 MHz  (original: 200 MHz, overclock: 36%)
          Memory Bus                                        204.71 MHz
        CPU Cache:
          L1 Code Cache                                     64 KB  (Parity)
          L1 Data Cache                                     64 KB  (ECC)
          L2 Cache                                          512 KB  (On-Die, ECC, Full-Speed)
        Motherboard Properties:
          Motherboard ID                                    03/15/2005-MS-7100-6A61FM4BC-00
          Motherboard Name                                  MSI K8N Diamond / K8N SLI Platinum (MS-7100)  (3 PCI, 2 PCI-E x16, 4 DDR DIMM, Audio, Gigabit LAN, IEEE-1394)
        Chipset Properties:
          Motherboard Chipset                               nVIDIA nForce4 SLI, AMD Hammer
          Memory Timings                                    2-4-4-6  (CL-RCD-RP-RAS)
          Command Rate (CR)                                 1T
        SPD Memory Modules:
          DIMM1: GeIL CL25-4-4DDR 500                       512 MB PC4000 DDR SDRAM  (2.5-5-5-9 @ 250 MHz)  (2.0-5-5-9 @ 232 MHz)
          DIMM2: GeIL CL25-4-4DDR 500                       512 MB PC4000 DDR SDRAM  (2.5-5-5-9 @ 250 MHz)  (2.0-5-5-9 @ 232 MHz)
        BIOS Properties:
          System BIOS Date                                  03/15/05
          Video BIOS Date                                   06/27/05
          Award BIOS Type                                   Phoenix - AwardBIOS v6.00PG
          Award BIOS Message                                W7100NZ1 V9.0 031505 14:17:53
          DMI BIOS Version                                  6.00 PG
        Graphics Processor Properties:
          Video Adapter                                     nVIDIA GeForce 6600 GT PCI-E
          GPU Code Name                                     NV43GT  (PCI Express x16 10DE / 0140, Rev A2)
          GPU Clock                                         299 MHz
          Memory Clock                                      522 MHz
    --------[ Power Management ]--------------------------------------------------------------------------------------------
        Power Management Properties:
          Current Power Source                              AC Line
          Battery Status                                    No Battery
          Full Battery Lifetime                             Unknown
          Remaining Battery Lifetime                        Unknown
    --------[ Sensor ]------------------------------------------------------------------------------------------------------
        Sensor Properties:
          Sensor Type                                       Winbond W83627THF  (ISA 290h)
          GPU Sensor Type                                   Driver  (NV-DRV)
          Motherboard Name                                  MSI MS-7046 / 7100 / 7125
        Temperatures:
          Motherboard                                       32 °C  (90 °F)
          CPU                                               35 °C  (95 °F)
          GPU1: GPU                                         56 °C  (133 °F)
          GPU2: GPU                                         50 °C  (122 °F)
        Cooling Fans:
          CPU                                               3444 RPM
          System                                            2637 RPM
          North Bridge                                      7337 RPM
        Voltage Values:
          CPU Core                                          1.38 V
          +3.3 V                                            3.34 V
          +5 V                                              5.08 V
          +12 V                                             12.04 V
          +5 V Standby                                      5.17 V
          VBAT Battery                                      3.10 V
          Debug Info F                                      40 31 17
          Debug Info T                                      32 35 157
          Debug Info V                                      56 D1 C6 BD 1C 14 34 (01)
    --------[ Debug - PCI ]-------------------------------------------------------------------------------------------------
    Benchmarking     PCMARK04/score:4684      3DMARK03/score:15075 
    got any suggestions, Im just trying to learn how to do this, any help would be greatly appreciated
     

  • NIghtmare - Brand new S230u from major retailer: Lenovo says warranty expired

    I just purchased a new (sealed) Lenovo S230u factory box with security tape on both ends unopened, with no additional tape, from a major online retailer that also have physical stores in selected States.
    It is a refurnished machine, according to the major retailer website, it has 90 days warranty from Lenovo with Levono phone number etc. Having bought several 1000+ Thinkpad and 3000 desktop from IBM, with the *very good* price offered and manufacture warranty, I am willing for the first time to try out the Thinkpads after it is owned by a Chinese company Lenovo. I had been very skeptical whether the Chinese company Lenovo would provide the same level of support as IBM. And this is where the nightmare begins.
    I called and checked with the online retailer and they had a few hundred machines but I bought one of the last one they have in stock since it went to SOLD OUT within hours. I confirmed with them they are factory refurnished machines and they had hundreds of them. With the low price and short warranty, I made sure I have the ability to purchase extended warranty and went to Levono online chat for warranty to confirm how much it would cost to buy extended warranty and that shipping for any needed service is free BOTH ways.  My last machine was HP and I loved how they provided two way free shipping and excellent technical support service. HP helped me fix an unexpected motherboard issue, deemed manufacturer’s defect and replaced it for free.  No way I am buying any laptop with worse off warranty for a cheap price.   The agent confirmed that I will be able to buy extended warranty with 2-way free shipping but need to receive the machine and give them the serial no. for a quote.
    I felt safe, guaranteed by BOTH the online retailer and Lenovo and went ahead with my purchase.
    Having read online discussions, I am very cautious to buy refurnished machines sold on eBay, non-major retailers that may switch off parts and discredit the warranty. I still checked that machine came with security tape sealed on both ends, nothing was altered. 
    However, when I started using the machine, I realized that it said my warranty expired! I called Levono immediately and the first agent gave me the lenovo_pop email address to send in my warranty and told me they can update and extend it for a year - I thought WOW, great if it is one year. I had tech issues as I performed a series of windows, lenovo, microsoft updates randomly, and getting some registry error message and wanted tech support to guide me quickly to restore to factory condition but the request was denied because warranty expired! Furthermore, he said they do NOT honor any warranty of refurnished machine NOT sold by lenovo.com! WHAT??? That is NOT what they informed me from online support BEFORE i purchased the machine!! And if my warranty end date is AFTER the day I called, they could have easily helped me? The machine expired 1/14/2014 (a year from manufacturer’s date) and I bought it beginning of Feb 2014. Oh great, I guess the few hundred customers that bought the same machine a few weeks before me won’t have this problem as I bought the last few machines – no wonder the cheap price for a wonderful laptop.
    This issue was stretched out for weeks! With my case no. CLOSED – reason: no customer contact, when I was waiting for the agent who promised to call me back AFTER I emailed to Lenovo my proof of purchase twice to different emails -  yet no one called. An agent then told me new info saying that the major retailer should be responsible to contact Lenovo. Then another agent said they don't honor any third party refurnished machine, even major retailers!! Another case no. opened and a supervisor escalated to a different Lenovo team with screen captures of links to retailer product page, warranty info, as well as  my conversation with the Lenovo rep, yet I still receive no resolution 10 days after. This is night and day experience compared to previous IBM or HP experience I had. All contradicting info and the customer penalized.
    With the major retailer, I have escalated the issue twice to supervisors, yet the Lenovo closed the first case no. when Lenovo supposed to call me back and the retailer couldn't do much while I still didnt' hear back from the second supervisor but they extended my 14 days return policy to 30 days. Their name not mentioned yet, because unlike Levono, the low level support person called me daily to follow up while I have been chasing after Lenovo every few days and know it would be ignored if I don’t keep pushing it.
    This is madness, and if for the diligent cautious buyer I am, this is what I go through from a major online retailer,  I can not imagine what a normal buyer would go through. Loyal customers should NOT be the ones who pays for this.
    I sincerely hope something can be resolved within a day before my extended return date expired and a senior forum administrator can help me. If not, at least loyal and potential customers would know that things like this could happen and consider this before you buy a refurbished levono anywhere other than Lenovo, and you can be the judge whether Lenovo and it’s policies are worth supporting. 
    To be honest, I loved IBM, I love my new laptop and I just want the technical support I deserve to check on some potential driver issue and windows 8.1 upgrade support. I want to be able to perhaps buy the extended warranty that was promised. The peace of mind. Now I even have doubt about the company and whether to spend extra money for protection that does not protect customers!  To be fair, 90% of the many agents/supervisor I talked to have been professional and helpful which made the process tolerable. The reason I waited so long to post this message on a public forum. It just seems like their system, policies and communication between departments are ridiculous and customers are penalized for it.  If you don’t honor ANY third party refurbished warranty - deal with your wholesale agents, retailers, don't sell new or refurbished machines to them. Your loyal customers should NOT be penalized for it and make sure that customers are well informed if they do simple research! Information across departments should be consistent. And the supervisors of the departments should be able to honor and fix a mistake related to wrong info (if it was wrong) provided by another Lenovo department and handle things in a TIMELY manner. I should not have to spent over 15 hours on this for nearly a month! This is NOT what I expect from a top computer company in the US market. Something needs to be done so other loyal customers do not have to go through this and also ensure that customers who support Lenovo would NOT fall into traps of dishonest merchants.

    wabibi,
    Thanks for the additional details via private message.   My apologies for the troubles you have had so far - let's look into the situation and see what can be done to help you get this resolved.
    Best regards,
    Mark
    ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
    Mark Hopkins
    Program Manager, Lenovo Social Media (Services)
    twitter @lenovoforums
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Need to boot broken Mac-Mini using retail Snow Leopard 10.6 DVD

    Hi,
    In Summary:
    ==========
    I have Mac Mini (late 2009) which does not boot anymore and I need to install Snow Leopard using retail DVD (version 10.6). The OS/installer from the DVD does not seem to boot either. I always very much appreciate the efforts of true geeks. So please, any casual beginner, please do not demoralize with something like "cannot be done" etc.
    The complete story:
    ==================
    The start of the problem:
    1. All of a sudden, one fine day, on start up, my Mac Mini strated to shut itself down without no apparent reason to me. When trying to boot, it would show a progress bar for about 5 minutes - I am assuming that was disk-consistency check being performed. My best guess is that right after the use of Carbon-Copy Cloner (but I am not 100% sure) it all strated to happen.
    2. Performed Mac's Disk-Util check and [Verify Volume] used to display "invalid directory item count, should be 31 instead of 29". Surface scan said disk hardware is 100% fine. Volume Repair never worked, since OS X was installed on the primary disk. I lost the DVDs that came with this Mac Mini, so the option to boot from that DVD and launch Disk Util etc. was not possible.
    TechTool Pro - No Help:
    3. Started googling and had to choose between [TechTool Pro] and [Disk Warrior], opted for TechTool Pro. Tried its bootable DVD only to learn that TechTool Pro cannot fix it. Again, it's surface scan suggested disk hardware is 100% fine. Sent the details to TechTool Pro support team, they couldn't help either after a couple of e-mails+data exchange. (How do I claim my lost money with TechTool Pro - suggestions appreciated as well).
    Googling / Mac Forums:
    4. Started looking into forums, learnt that someone had successfully repaired this problem using Ubuntu 11.04 install DVD (i.e., without installing the Ubuntu, but just using its 'try from DVD' feature). I had that handy, but forgot to disable HFS+ journaling before attempting to fix the problem. Anyway, attempting volume repair that way couldn't fix the problem as well. However this step took away my ability to boot from Mac.
    5. However using Ubuntu's bootable disk, I could access Mac-HDDs contents - and was able to successfully back-up *all* my important data.
    6. Googled and learnt that just attempting to boot using Ubuntu DVD can take away ability to boot using Mac bootable media - possibly due to EFI internals. Suspecting EFI is now corrupt, I tried other 'hacks' like:
      6.1 eEFIt Boot Disk - which does not work at all,
      6.2 Empire EFI w/ Chameleon - not sure how to proceed with options presented - trying either does not work,
      6.3 Super GRUB2 - boots fine, but attempting to boot from Mac-HDD fails after a couple of seconds,
      6.4 Boot-132 - boots fine, prompt asks for input, but then I cannot eject/replace the DVD due to Mac-Mini (lack of) design,
      6.5 Ubuntu 11.04 / 11.10 - still boots fine - just that I cannot go into Mac-OS-X from here,
      6.6 TechTool Pro bootable DVD - which used to boot fine earlier stopped to boot.
    As you can see, none worked successfully. So I didn't yet try other popular rescue media - as I suspect that is not the direction I need to go into.
    >> Looks like most of my problems are due to the fact that I have Mac-Mini which does not allow eject/replace of DVD from command prompt / out side of Mac-OS-X.
    7. Tried emptying EFI partition, playing with EFI/Mac-OS partitions boot flags, Zapping the PRAM, nothing still allows me to boot either from Mac-HDD or any Mac-Bootable-DVD.
    Current State:
    8. Now while boot time, Mac displays a gray screen for a few seconds, and then a blinking prompt on black background. That's it!
    Snow Leopard 10.6 Retail Install DVD:
    9. Went to Mac store and bought this DVD only to witness that I can't boot from it as well. (This is a huge shocker, how is Apple able to sell these DVDs if these don't work on genuine MacMini itself. After all we are able to boot from and install Windows/Linux on a variety of Machines).
    I am hoping for a very small step/fix that I am missing, since I can still see and access all Mac-HDD contents after booting from Ubuntu bootable DVD. However I am prepared for a good amount of exercise as well - assuming someone posts a valid/verified fix.
    Things available right now:
    ==========================
    A. Genuine Mac-Mini (Late 2009) who lost it's ability to boot either from its HDD or Mac-bootable DVDs (TechTools Pro, Mac OS X retail DVD)
    B. Mac OS X 10.6 Retail DVD
    C. NOT AVAILABLE - DVD that came with this Mac-Mini
    D. Variety of rescue DVDs, listed in section 6 above
    E. Another machine/PC with Ubuntu 11.04 - giving me ability to access internet
    Thanks for reading.
    Zita

    I had a similar discussion recently with another user.
    Your Mac mini (late 2009) originally came with Mac OS X 10.6.2 build 10A432 or build 10C2234 see http://support.apple.com/kb/HT1159 it would have come with an original install disc specific to your model of Mac which you could use to run Disk Utility from or to do a complete reinstall.
    The retail boxed copy of Mac OS X 10.6 (Snow Leopard) was originally intended for older Macs which had previously come with Mac OS X 10.5 or 10.4. It would have on it a version of Mac OS X 10.6 or 10.6.1 which would be able to boot these older Macs, but had no need to boot newer Macs which were released after the launch of Mac OS X 10.6 since all those newer Macs already shipped with their own discs.
    So it is normal that the retail boxed Snow Leopard installer does not work on your model Mac mini. You should be using the one that shipped with your Mac mini instead. I am guessing you have lost it.
    Assuming you have lost the Mac mini original disc, I can suggest the following options to try and workaround this.
    If you have another Mac, an older Mac, one that will be bootable using the retail Snow Leopard install disc you have, you could do either of the following.
    Connect an empty external GUID partitioned hard disk to this other Mac
    Boot from the retail Snow Leopard installer
    Install on to the external disk
    Once the install is complete, update it using the combo update not the one via Software Update to Mac OS X 10.6.8. This will add all the newer drivers needed to allow it to work on your newer Mac mini. You can download this combo update from here http://support.apple.com/kb/DL1399
    You can now disconnect the external drive and connect it to your Mac mini and boot from it by holding down the Option key when you turn the Mac mini on
    or a similar process if you want to wipe the Mac mini and reinstall directly on to it
    Boot the Mac mini in FireWire Target Disk Mode (see http://support.apple.com/kb/ht1661 )
    Connect the Mac mini as an external hard disk to the other older Mac
    Boot from the retail Snow Leopard installer
    Install on to the external disk
    Once the install is complete, update it using the combo update not the one via Software Update to Mac OS X 10.6.8. This will add all the newer drivers needed to allow it to work on your newer Mac mini. You can download this combo update from here http://support.apple.com/kb/DL1399
    You can now disconnect the Mac mini and boot from it as normal
    Note: While the Mac mini is connected in FireWire Target Disk mode to the second Mac, you could backup (if you don't already have a backup) any files you need to retrieve.
    If you don't have a suitable second Mac you may have to either borrow someone else's, or get the help of an Apple Store if one is in your area.

  • Please help --- Drivers for SB0220. OEM in liew of retail pa

    Hi all,
    This is my first post here, although I have been reading up the posts here regularly to troubleshoot problems with my SoundBlaster sound cards -- and thanks to all of you. I have used a few of them till date, a SB Li've! 5. DE, a SB Li've! (with digital out), a PCI 4. Digital, and even a good old Vibra.
    Anyway, my problem pertains to the mystery that surround the so-called OEM SoundBlaster cards and ?Creative's involvement with them -- and of course a "good old" driver issue.
    I got my Creative SB Li've! 5. DE card in 2002 (so this way past the "warranty"). This was a box-packed retail version. I don't remember the model number that was marked (number on the right top corner) on it though, but it worked fine -- as long as I used it with the accomanying CD. However, when I tried updating the drivers using the latest drivers from the Creative website, I would get a message that said something like this "No soundblaster card is detected...." Anyway, the software and drivers from the CD worked fine. However, just before the warranty was about to expire, the sound card suddenly stopped working and I returned it the importers/distributors from whom I had purchased it. Incidentally, I li've in India. When I first started looking for this sound card, I could not find it anywhere in the stores, so I had to order it directly from one of the authorized importers for India, Compuage Infocom Limited (www.compuageindia.com). Compuage promptly sent me a replacement with a similar-looking card, but it said "Creative SB Li've!" Those days I did not have a 5. speaker set and I used this card with the default drivers from the OS.
    Finally, last month when I got a 5. speaker set (Creative Inspire 5200), I was horrified to learn that this card (the one Compuage sent me as replacement) did not support 5. speakers! On taking a closer look, I discovered that the card was marked CT4830. I looked up the Creative Asia website, and there was no mention of such a card!! Googling confirmed that this was indeed an OEM card. I could not believe that I had been given an OEM card in lieu of my retail card. I wrote back to the importers. They told me that they would replace it with a 5. card (even though it was way past warranty). Well, I sure was glad. I soon received a replacement card and this time it said "Sound Blaster Li've! 5. Digital." (Note: This was not Digital Entertainment and only Digital). The model number is SB0220 (Serial number on the other side = C6SB02294370385Q). Now this card is also supposed to be an OEM card. As luck would have it, I have not been able to install the sound card (using the original CD that I had), or the latest ones for the 5. series of cards from the Creative website -- the card is simply not detected as a Sound Blaster card. It has been a big headache and I feel like throwing it in the dustbin. I talked to Compuage (the importer for India) and the tech guy there insists that it is the "same card." While I am trying to troubleshoot this issue, my questions are:
    . How come Creative (I am attributing this to Creative as Compuage is one of only two authorized importers for their products in India) giving OEM cards to their retail customers when giving out replacement cards (warranty replacements)? In fact, this would lead me to believe that maybe Creative itself is retailing OEM cards through their vendors --- could it be true? Is this the reason that so many of us unwittingly end up with these OEM cards from Creative? Is this FAIR?
    2. Secondly and most importantly, how do I solve this problem? Which Creative drivers should I use? I know I can try the KX project drivers and maybe try those from www.driverguide.com -- but what about Creative Drivers -- am I not entitled to Creative Drivers having been an authentic retail customer?
    I would really appreciate inputs from everyone, esp., the moderators.
    Thanks in advance.
    johy

    shadowcage wrote:
    okay well i tryed the patching method on all of the isos i had after extracting them.
    I patched it and it said it was successful. when i ran each successi've setup it still didnt detect any soundblaster hardware.
    I also went to compaq and tryed a driver i found there without any luck. Im thinking at this point it is an OEM
    Although i still dont understand how you got compaq from the model number, im going to continue looking around their site.
    Maybe ill luck out but so far im about to the point im ready to throw this @#$%@%#@$@##@$#@$% thing away lol.
    Im looking on driver guide now again. :Sighs This is so aggrivating Normally i wouldnt have bought a card without the drivers but
    my wifes the one that got it and she didnt know. Oh well......
    You can get the model information from here.
    You can also try by installing kX drivers -> if kX package don't get installed, your card may have some problems.
    kX Home pages - http://kxproject.lugosoft.com/index.php?skip=
    kX support forum - http://www.driverheaven.net/forumdisplay.php?f=74
    jutapa

  • 1xm1n's Guide to the Audigy 2 ZS (FAQ)

    PART GUIDE. This guide comes in 3 parts. Hello all Creative Audigy 2 ZS ( non Pro ) owners. After owning this card for close on 7 mths now and getting to know the basic ins and outs that need to be set up to get the most out of the card I thought I would write up a basic guide to get new owners started as quickly as possiable. I know when I first got home with it, it was close to hour or so before it was all up and running 00%. Hopefully with this basic guide to getting started, new owners will be up and running 00% in about 0 mins. My guide is not aimed at serious problems? and/or software releated issues as there is just far to many variables. Instead I have compiled the basic needs for installing and setting up the card to get the very best possiable sound reproduction for games/music and DVD video playback. Along with a few common problem solving ti
    ps.
    For the most part the card is simple enough to setup,install and update drivers and get fantastic DD 5. sound, THX and DTS reproduction. As far as games go, everything should work right off the bat and in most cases going to the developers web site for patches will solve any sound issue you may have. It is impossiable for me to add any fixes for games in this guide but if you have a problem most developers have a dedicated forum for thier games at which help is at hand. I have not included any tips/info on recording media as there are WAY too many things to list, so a seperate guide may follow although the online manual for all creative products is very good. THIS GUIDE IS FOR THE CREATIVE AUDIGY 2zs ( NON PRO ) though should work with all creative products. Table of contents:
    1: SETTING UP FOR THE FIRST TIME:
    2: INSTALLING THE zs:
    3: Updating Drivers and applications ( This is a 2 part guide ):
    4: PLXCore.PLX Error:
    5: UNINSTALL DRIVERS:
    6: UPDATEING DRIVERS : PART 2 : BETAS
    7: SLOW BOOTUP AFTER DRIVER INSTALL/UPDATE:
    8: SOUND CARD NOT DETECTED OR DRIVER WONT INSTALL:
    9: NO SOUND AT ALL:
    10: SOUND POPS AND CRACKLES:
    11: 5. SOUND IN DVD MOVIES:
    12: FILTERS AND CODECS:
    13: Some common errors you may encounter with WMP0:
    14: Fix a Codec/filter error:
    15: MISC Errors you may encounter:
    16: Test your overall sound with RightMark:
    17: Music playback:?: SETTING UP FOR THE FIRST TIME:Make sure all previous sound devices and drivers are removed. The first thing that needs to be done is general system maintenants. The first thing is to make sure that any previous sound device drivers and application, ( mixers and recorders etc ) you have are removed from your system. This is very simple to do. Go to add remove programmes and find the device driver and the applications and select remove. Now you may think, thats it but there is a little bit more to be done. After the driver is removed there is bound to be a few files left over. So in general simply go through your temp folder? C:\Documents and Settings\"user"\Local Settings\Temp and delete all files. Also go through C:\WINDOWS\Temp and delete files in here. Go through C:/ and locate any folders that contain the apps for your old sound device, these may include mixers and the like. Delete these folders if found.
    After this is done it is a good idea to uninstall any and all third party codecs. ( more on codecs later ) These would include Divx, AC3 filter etc. You should know what Codecs you have installed, and as there are many different codecs its not practical for me to go through them all here. Now that we have covered the removal of previous sound devices and its applictions along with all 3rd party codecs its time to get that new ZS up and running.NOTE: If you have onboard sound you MUST dissable it in the bios.
    At boot hit the Del key and once in the bios ( read through the manual for your Motherboard ) find the onboard sound device and dissable it.2: Installing the ZS:As a rule you do not want to install any PCi device in the PCI slot directly under the AGP slot as it can and mostly will cause an IRQ conflict. PCI-e has no issue with this though. So on an AGP board I have found the PCI slot 4 is best suited. After the Sound card is sloted in place, double check it is sercure and the mounting screw is in place.Fire up your PC. The first thing to happen is windows will find the device. Let Windows find the device, then you will get a screen asking if you want windows to find drivers or simular. Say no and cancel this. Place the CD that came with your card into the CD dri've and simply follow the prompts to install the drivers and applictaions. It is important not to cancel this and to install ALL the applictions such as media source etc. After all is installed you will need to reboot for all changes to take affect. Once the system reboots you will then given the choice to regeister your Creative product. I would highly recommend you do this now, if not just to get it out the way but you may get an application is not regestered error.
    Hopefully you now have your card installed and working. Please do view the getting started demo as it will show you first hand all the settings and options for Media source applictaions. Very handy. CHECK THIS FIRST UP:?In Creative Media Player click on tools and then settings. Click general and under play back sound devices, ensure your card is selected thus to the device features.
    Type in run "C:\Program Files\Creative\MediaSource\Audio Device Selection" Doulble click the "CTAudSel" Icon and ensure your device is selected?
    3: Updating Drivers and applications ( This is a 2 part guide ):The next thing you WILL want to do before running games or Media is to update your drivers and ap
    ps.
    Creative have made this process easy with their Auto Updater. Simply go to the surrport page at creative.com and select drivers. You will then need to select the auto update fuction which will need to install acti'veX control ( this one is safe so dont stress ) after this is installed your card will be detected and the next page will be displayed with all relevent di'vers and applictaions. I highly reconmend you install any apps that state Critical or essectial. Other reconmened applications are for specific fuctions so use you own judgement on these. The process wont take to long and is fully automated. Now you may ask, what about the beta driver. To update to the latest beta you need to download it manually and install it from your desktop.Note: The betas are?GREAT so dont be afraid to use them though you must understand that some applictaions may not work correclty, though I have found these issues to be somewhat hit and miss. If an application fails,? simply reboot usally this fixes it.Ok, so thats the easy stuff out the way then and hopefully you dont need to read on, though errors do happen and things go a bit pear shaped from time to time and I myself get the odd issue, though I've found for the most part these things are simple enough to solve hence this guide. 4: PLXCore.PLX Error:?This is a mystery error that can arise for no reason at all, sometimes.
    Verify that the file PLXCore.PLX is located in the correct folder in your hard dri've. The default folder is C:\Program Files\Creative\Shared Files folder. If the file is not present in the folder, manually copy the file from the original installation CD-ROM disk to the above location. To do so, insert the Sound Blaster installation CD-ROM disk, exit from the Installation procedure if it auto runs.Go to My Computer, right click on the CD-ROM dri've that contains the installation CD-ROM disk, and select Explorer.Double click on the CTEngine folder, then the PlayRec.cab file, it should expand.Select the file PLXCore.PLX and copy it to C:\Program Files\Creative\Shared Files.Reboot.Any other bootup error that may arise can be fixed using the same method as above, though you will be looking for a different file.
    5: UNINSTALL DRIVERSIf you want to un-install all drivers before updateing to beta drivers).
    This is my tried and tested technique.BACK UP THIS FILE NOW! ( this may save time later )? PLXCore.PLX? located in C:\Program Files\Creative\Shared Files. Incase you get PLXCore.PLX error.Go to Add Remove Programs and un-install all listings related to your audio card.Also any? apps, eg: media source. Do not restart your computer when prompted so. In? C:\Program Files folder you should have an installshield folder ( may be hidden). In here are GUID named folders. . If hidden, to view these folders Open folder options under tools . Now untick HIDE PROTECTED OPERATING SYSTEM FILES ( RECOMMENED ) it also may be just under hide files also. Try both methods if need be to veiw files.Make sure when you are all done place tick back in box.::YOU WANT TO DELETE THE INSTALLSHIELD files for CRETAIVE::If you go through all the folders and look at each setup.ini you will find ones corresponding to Creative .
    You can right click on some and it gives you info or open the ini? with note pad and if there is a reference to Creative labs, media source? and other creative apps? delete the entire folder.
    Go through this twice to make 00% sure you get them all.
    Empty out all temp folders. Type in run MSCONFIG and make sure all creative entries are untick. There may? be nothing in here.
    Type in run regedit and then in search / find / type in? startupreg . This will give you the MS startup entries. Delete the keys for creative if any.
    No need to Delete this folder ---- C:\Program Files\Creative ---- its proberly safest to leave it anyway.Run the Beta installer. 6: UPDATEING DRIVERS : PART 2 : BETASYou can use the auto updater from Creative and this is infact the best way to do this. However if you want to update the Beta Drivers ( which are infact better ) its best to just over right them,? with this method things SHOULD go smooth. I have always installed beta drivers this way with no issue as of yet.Download the Beta. Type in run "msconfig" and make sure ALL creative apps are unticked thus not to run at boot.
    Type in run "services.msc" and dissable the Creative service.Reboot.Now run the installer for the Beta driver. You will come to a screen that will say or to this effect. An older file was found and may no longer be needed. SAY NO TO REMOVING THIS FILE AND ANY FILES!If after this if you have any kind of media source application error ( which can happen with betas ) then simply re-install the applications. Its best to re-install ALL media source applictaions. 7: SLOW BOOTUP AFTER DRIVER INSTALL/UPDATE:
    Search for these in sys32 "ctaud2k.sys" & ha0kx2k.sys. Are they the same version?
    All system devices and drivers need to be the same version. In control panel ( windows ) sound and Audio Device Properties, go to Audio and make sure they are all the same device.EG:
    Sound playback
    Default device: SB Audigy 2ZS Audio [DF00]Sound recording
    Default device :SB Audigy 2ZS Audio [DF00]MIDI music playback
    Default device : SB Audigy 2ZS Syth A [DF00]Place a tick in Use only default devicesGo to C:\WINDOWS Updreg.exe. Right click on it and go to Pro
    ps.
    In general go to advance .( this is for regestering your product.)
    check its set up as follows.Under Archi've and index attributes are 2 boxs. File is ready for archiving and For fast searching, allow Indexing.
    Untick File is ready for Archiving.
    Place a Tick in? For For fast searching, allow Indexing.Under Compress or Encrypt untick both.Do the same for this exe. in C\:windows CTRegRun.EXE
    Message Edited by xmn on 02-7-2006:40 AM

    PART 3.
    2: Filters and Codecs.
    For the most part you only need AC3 filter , Xvid ( or the full Divx Pack ) WMP0 and which ever other Play back programme you may prefer, Eg, Win DVD, Winamp and so on.
    Codec stands for Coder/Decoder. Basically it is a piece of software or a driver that adds a support for certain video/audio format for your operating system. With codec, your system recognizes the format the codec is built for and allows you to play the audio/video file (=decode) or in some cases, to change another audio/video file into that format (=(en)code).
    For example, when you install Windows to your home computer, Windows installs automatically most commonly used codecs into the system, so you don't have to download them separately from their vendors. However there are some codecs that are widely used, but not installed by Windows. Most notably DivX , MPEG-2.
    Get all the Codecs/Filters/Plugins you could ever need from:
    http://www.free-codecs.com/AC3_Filter_download.htm
    http://www.free-codecs.com/
    http://www.microsoft.com/windows/win...0/default.aspx
    Ok, you now should be all set.
    A major required Filter is AC3.
    AC3Filter - it is DirectShow filter for AC3 decoding to play AVI with AC3 audio tracks and MPEG2 (DVD). Required for WMP.
    NOTE: If you have DVD software that should play encoded 5. then make sure you have any updates/patches for the player installed and go through the tools/options for the player and ensure its setup correctly to decode AC3filters in the applictions tools menu.
    If you use Cyberlink Power DVD you may need to pay an extra fee to get the required AC3filter/MPEG2 decoders to fuction as all 5. sound settings may be greyed out on some dated versions.
    InterVideo WIN DVD ( this software suit comes with most "Asus" if not all makes of Mainboards. This suit comes complete with the required codecs/filters so get full surrport for 5. - 6. - 7. out of the box. Note: you must set it up first under audio options as it defualts to 2..
    If you use WMP0 you NEED to download and install the AC3filter or get the latest XP codec/filters packs. With out these filters you may not get 5. sound and/or poor reproduction.
    Supported file types:
    The following table lists the file types (formats) supported by Windows Media Player .(For files type played by Power DVD or WIN DVD please refer to the makers website or read me file for a detailed list).
    File type (format) File name extension .Music CD Playback (CD audio) .cda Audio Interchange File Format (AIFF) .aif, .aifc, and .aiff Windows Media audio and video files .asf, .asx, .wax, .wm, .wma, .wmd, .wmp, .wmv, .wmx, .wpl, and .wvx Windows audio and video files .avi and .wav Windows Media Player skins .wmz Moving Picture Experts Group (MPEG) .mpeg, .mpg, .mv, .mp2, .mpa, .mpe, .mp2v*, and .mpv2 Musical Instrument Digital Interface (MIDI) .mid, .midi, and .rmi AU (UNIX) .au and .snd MP3 .mp3 and .m3u DVD video .vob Macromedia Flash .swf Microsoft Recorded TV Show .dvr-ms* NOTE: WMP defualts to 2.. To enable 5. run WMP0. Click on tools then point to options. Navigate to DVD then open up the advanced window. In here is everything you need to set things up. If you dont see AC3 then you need to install the AC3 codec.
    NOTE: If you mess things up simply return to defult settings and start over.
    3: Some common errors you may encounter with WMP0:
    Error messages are identified by numerical IDs, such as C00D0BC2 and 800704CF. You can determine the ID of a specific error message by clicking the More Information or Web Help button on the error message when you encounter it. The resulting page will indicate the error ID.
    : Error's C00D6A and C00D9A while playing DVD's or MPEG-2 content. This is directly related to either your current video card drivers or the MPEG-2/DVD decoder you have installed (EG: PowerDVD, Win DVD etc ). Reinstalling and/or uninstalling the MPEG-2/DVD decoder (PowerDVD, Win DVD ) and/or video drivers should fix the problem for you.You should now be able to re-install you decoder ( Power DVD etc ) and continue its use.
    Erro : C00DAC:Cannot play the file Windows Media Player cannot play the protected file because there is a problem with your sound device, such as a sound card or sound controller. You might encounter this error message for one of the following reasons.
    Your sound device requires an updated driver. ( update driver )
    The selected sound device does not support Secure Audio Path (SAP).
    If you have multiple sound devices installed on your computer, try using a different one.
    To use a different sound device, on the Tools menu, click Options, and then click the Devices tab. Double-click Speakers, audio device to use, click a different device.
    Error : "divide error in module IVIAUDIO.AX at".
    Only exists in systems that have various Sound Blaster Li've sound cards and WinDVD installed. This is infact a compatibility problem between these products. The problem is realized when MP3 oriented applications call upon certain sound card services making it look as though the error was raised from within the application in question.
    FIX:Uninstall WIN DVD. Reinstall WMP and AC3 filter and then reinstall DVD WIN.
    A simple but rare issue.
    ModName.Win DVD "msvcrt.dll" and/or Win DVD MFC application error.
    FIX:
    Uninstall any java filters. Macromedia and Macromedia Acti'veX.( to remove Acti'veX go to C:\WINDOWS\Downloaded Program Files and delete the Acti'veX )
    4: Fix a Codec/filter error:
    Codecs/Filters/Plugins are like any other kind of software installed and things can go wrong. If things are not working as they should try the following.
    Download and install "Gspot"
    http://gspot.headbands.com/download.htmlBuild 0307 - 23 KB Run the programme and simply point to system and select "List Codecs and other Filters"
    Its easy really to know whats what here and how to use it to find out the source of the issue, if you have one. If its red, its bad so you then need to trace the Filter/Codec to its source and remove it.
    Here is just one very simple excample you may encounter and how it was fixed.
    If you have ffdshow file is missing error pop up while running a player application, first go to C:\WINDOWS\system32 and search for ffdshow.en. Its proberly not here though. If it is just leave it be.
    NOTE: ffdshow is used for AVI/Xvid enc/dec source.
    To fix this "ffdshow Video Codec file is missing " error Simply uninstall your Xvid codec or your entire DivX programme, or any other Filter/Codec you have installed for playback of DivX files and AVI Video Files.
    (Some times it seems a few Codecs/Filters dont get along so you must be aware of what you install).
    Cheak "Gspot" again and Filter should be removed from the list.
    Now you can reinstall the Xvid filter "XviD-.0.3-2022004" or your desired DivX programme.
    Now go back toC:\WINDOWS\system32 and search for ffdshow.en. It should be there if it was not before. If the issue is back try a different version of required Filter.
    So, thats just excample of a simple fix that got everything working again. Its not to hard to find out what the problem Codec/Filter is and then its just a case of uninstalling it. You can re-install the Codec/Filter but you should double cheak with "Gspot" and ensure the issue has not repeated itself .
    If it has you can try and find out if the issue is related to another type filter causing a conflict or use an alternate Filter/Codec that will perform the same task .
    Search for an updated version of required the Codec/Filter also.
    Ok, thats pretty much the basics in getting correct and stable 5. sound working the way it should with your new Creative Audigy 2 ZS sound card.
    5 : MISC Errors you may encounter:
    ModName.Win DVD 7 msvcrt.dll and/orWin DVD MFC application error.
    Uninstall any java filters. Macromedia and Macromedia Acti'veX.
    For Explorer issues such as pages not operning, media not working and the like :
    type in run:regsvr32 vbscript.dllregsvr32 jscript.dll
    Sound stutter:Go to Device ManagerGo to Sound,video and Game ControllersIn there you will see Audio Codecs double click itGo the to the properties TABYou will see Windows Media Audio double click itChange the priority from 7 to Apply OK exit everythingRestart PC
    If it fails, set back to .
    Any Media file errors you may encounter can be fixed by going to add remove programme list and uninstall the codec/filter. EG, you get an error playing an AVI file. Remove Divx and or other AVI codecs. Re-install just one AVI codec.
    6: Test your overall sound with RightMark:
    http://audio.rightmark.org/index_new.shtml . This tool is just a simple tool for testing all fuctions of your card. You will soon enough know if your card has an issue in relation to EAX HD and surround sound.
    7: Music playback:
    Well, not a lot to say here really. Put in your Music CD or select your MP3/WAV file ( NOTE : MP3 will NEVER-EVER sound as good as a retail CD, FACT ) and then go to Mixer. Set up CMSS in EAX the console as you prefer and adjust the 7 band EQ to your liking. Thats all there is to it really. Its more about experimentation over the correct way to set things up.
    Ofcause you can use WinAMP for Music playback also
    Well, there you have it. The basic grail of the Creative Audigy 2 ZS ( non pro ) setup guide. I do hope it has made your experience with setting things up a breeze and are now enjoying full range 5. in games and DVD movies.

  • Virtual machine setup mini guide for thoes with XP or 7

    Sorry this guide is very rough.
    Why do we need this? Because application loader works only on mac. Not on PC. The final step to submit the application requires application loader. There is no way around it at the moment.
    So you need to submit your app but you don't have a mac or money for a used mac. You can still submit but You will need the following
    1. Retail DVD of snow leopard (ebay has brand new copies for $45 shipped)
    2. computer with AMD or Intel CPU
    3. about 20gig HD and 2gig ram
    4. fast internet connection
    5. a big cup of coffe
    6. a gigantic bag of patience.
    also needed
    Latest Empire EFI boot discs, combo update 10.5.6 for snow leopard, usb flash drive, multibeast, vmware preconfigered files for snow leopard, xcode
    all available if you just google them.
    1. start download process on vmware workstation 7, combo update 10.5.6, EFI bootdisc for AMD or Intel, multibeast
    2. install vmware, reboot. open up the vmware preconfigered files, make changes to HD and ram size. save it.
    3. mount the EFI bootdisc in VMware, boot VM up, on the EFI boot screen, insert your Retail DVD and change the VM dvd drive to connect to your physical drive
    4. hit F5, it should change the icon to MAC OSX INSTALL. Install Mac. configure it if you want. after install is finished, reattach the EFI bootdisc to boot your system. you willl not be able to boot without the bootdisc.
    5. before it boots, shut it down and make a snapshot. when EFI boots up again, you will see your mac installation, select that and it will boot into mac desktop.
    6. now copy multibeast, combo update, xcode on to your usb flash drive. then connect your flash drive with mac osx, copy all the files onto your desktop
    7. open multibeast, don't install it, run combo update, then complete multibeast installation with Easybeast option
    8. now reboot your VM, if everything works, shut it down and make another snap shot
    9. install xcode! finaly! after xcode finishes installation, you are good to go.
    couple of questions you might ask
    1. how to copy files around xp and mac on vmware. My suggestion, don't invest time into connecting the computers. just use the flash drive.
    2. must we always use the bootdisc to boot. No. You can find out how to resolve that. I just left it alone.
    3. why not just use xcode to develope. Well, vmware is extremlily slow running mac osx.
    4. finaly, vmware workstation 7 is trial version. Yes, you might be able to get the vmware player to run your vm after you finished the setup.
    This guide might get removed by adobe. if it does oh wells. google is your friend.
    if you still need help you can pm me. if i am not banned i suppose.

    Sorry this guide is very rough.
    Why do we need this? Because application loader works only on mac. Not on PC. The final step to submit the application requires application loader. There is no way around it at the moment.
    So you need to submit your app but you don't have a mac or money for a used mac. You can still submit but You will need the following
    1. Retail DVD of snow leopard (ebay has brand new copies for $45 shipped)
    2. computer with AMD or Intel CPU
    3. about 20gig HD and 2gig ram
    4. fast internet connection
    5. a big cup of coffe
    6. a gigantic bag of patience.
    also needed
    Latest Empire EFI boot discs, combo update 10.5.6 for snow leopard, usb flash drive, multibeast, vmware preconfigered files for snow leopard, xcode
    all available if you just google them.
    1. start download process on vmware workstation 7, combo update 10.5.6, EFI bootdisc for AMD or Intel, multibeast
    2. install vmware, reboot. open up the vmware preconfigered files, make changes to HD and ram size. save it.
    3. mount the EFI bootdisc in VMware, boot VM up, on the EFI boot screen, insert your Retail DVD and change the VM dvd drive to connect to your physical drive
    4. hit F5, it should change the icon to MAC OSX INSTALL. Install Mac. configure it if you want. after install is finished, reattach the EFI bootdisc to boot your system. you willl not be able to boot without the bootdisc.
    5. before it boots, shut it down and make a snapshot. when EFI boots up again, you will see your mac installation, select that and it will boot into mac desktop.
    6. now copy multibeast, combo update, xcode on to your usb flash drive. then connect your flash drive with mac osx, copy all the files onto your desktop
    7. open multibeast, don't install it, run combo update, then complete multibeast installation with Easybeast option
    8. now reboot your VM, if everything works, shut it down and make another snap shot
    9. install xcode! finaly! after xcode finishes installation, you are good to go.
    couple of questions you might ask
    1. how to copy files around xp and mac on vmware. My suggestion, don't invest time into connecting the computers. just use the flash drive.
    2. must we always use the bootdisc to boot. No. You can find out how to resolve that. I just left it alone.
    3. why not just use xcode to develope. Well, vmware is extremlily slow running mac osx.
    4. finaly, vmware workstation 7 is trial version. Yes, you might be able to get the vmware player to run your vm after you finished the setup.
    This guide might get removed by adobe. if it does oh wells. google is your friend.
    if you still need help you can pm me. if i am not banned i suppose.

  • Can anyone tell me where I can find a beginners guide to the filing system?

    Can anyone tell me where I can find a beginners guide to the filing system on the Macbook Air iOS 10.9.4?

    So, does this mean you have given up and decided to return to the MS Windows (PC) embrace?
    The link that dominic23 provided has parts 1, 2, and 3 — did you review all of these? What remaining question(s) do you have about the Apple file system?
    Videos that you may find on the Apple site are not updated regularly, and steps/techniques shown in them may be outdated, or not work as shown on the current operating system release.
    Did you look into the Apple Retail Store One to One learning assistance?
    Did you consider either of the following books as a learning aide?
    Switching to the Mac: The Missing Manual, Mavericks Edition
    OS X Mavericks: The Missing Manual

  • Windows 7 Professional 64bit OEM Retail Key has been blocked for used by microsoft

    I purchased Windows 7 Professional 64-bit OEM on 19th
    March 2014,  from a well known retailer, it is legit with the plastic case Hologram and the COA sticker. Before I instal on my laptop HP430, I ask to [email protected] about the Key is valid or not. On 20th March 2014 I got an email reply
    from [email protected] that my Key was Valid. After that I decide to instal on my HP430 Laptop and activated with no issues.  On 2nd May 2014 my laptop was error so I decide to re-instal my Windows on the same Lapotp HP430. Finally I try to re-activate
    my License using online activation and got an error message "This product key is blocked for used by Microsoft". I was trying to activate with Phone activation, but I got the same error "This product key is blocked for used by Microsoft".
    Can anyone provide details on this? Why is my key blocked from activation? What could of happened that compromised my license key?
    Thanks for your time reading this.
    Below is my Diagnostic Report :
    Diagnostic Report (1.9.0027.0):
    Windows Validation Data-->
    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-HCDX4-Q8V8T-8YTGC
    Windows Product Key Hash: Cis9b0F7nPyYY28ASxP8BpOaCpM=
    Windows Product ID: 00371-702-6995841-06073
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {3430F04C-466C-462E-B312-702BD690EF08}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.130828-1532
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A
    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    OGA Data-->
    Office Status: 103 Blocked VLK
    Microsoft Office Enterprise 2007 - 103 Blocked VLK
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    File Scan Data-->
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{3430F04C-466C-462E-B312-702BD690EF08}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-8YTGC</PKey><PID>00371-702-6995841-06073</PID><PIDType>5</PIDType><SID>S-1-5-21-185284974-1149994224-1979197176</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP
    430 Notebook PC              </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.39</Version><SMBIOSVersion major="2"
    minor="7"/><Date>20111218000000.000000+000</Date></BIOS><HWID>53803307018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>SE Asia Standard Time(GMT+07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>103</Result><Products><Product
    GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>103</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>ACD7202654E586</Val><Hash>fFic3JgCreGGRxyF8uMWB4R4Jcg=</Hash><Pid>89388-707-1528066-65065</Pid><PidType>14</PidType></Product></Products><Applications><App
    Id="15" Version="12" Result="103"/><App Id="16" Version="12" Result="103"/><App Id="18" Version="12" Result="103"/><App Id="19" Version="12"
    Result="103"/><App Id="1A" Version="12" Result="103"/><App Id="1B" Version="12" Result="103"/><App Id="44" Version="12" Result="103"/><App
    Id="A1" Version="12" Result="103"/><App Id="BA" Version="12" Result="103"/></Applications></Office></Software></GenuineResults>  
    Spsys.log Content: 0x80070002
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, RETAIL channel
    Activation ID: c1e88de3-96c4-4563-ad7d-775f65b1e670
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00212-702-699584-00-1033-7601.0000-1222014
    Installation ID: 003864977163724541444611907516049313404610751646466300
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: 8YTGC
    License Status: Initial grace period
    Time remaining: 40020 minute(s) (27 day(s))
    Remaining Windows rearm count: 3
    Trusted time: 5/5/2014 3:46:04 PM
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 5:3:2014 02:01
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    HWID Data-->
    HWID Hash Current: MAAAAAIAAQABAAEAAAABAAAAAwABAAEAonYuGt6VdxYsZvAIoLNek8JprtZekS5z
    OEM Activation 1.0 Data-->
    N/A
    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no Windows marker
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            HPQOEM        SLIC-MPC
      FACP            HPQOEM        SLIC-MPC
      HPET            HPQOEM        SLIC-MPC
      BOOT            HPQOEM        SLIC-MPC
      MCFG            HPQOEM        SLIC-MPC
      ASF!            HPQOEM        SLIC-MPC
      SLIC            HPQOEM        SLIC-MPC
      SSDT            HPQOEM        SLIC-MPC
      ASPT            HPQOEM        SLIC-MPC
      SSDT            HPQOEM        SLIC-MPC
      SSDT            HPQOEM        SLIC-MPC
      SSDT            HPQOEM        SLIC-MPC
      SSDT            HPQOEM        SLIC-MPC

    The lack of a Windows marker in the SLIC table could indicate that the machine originally shipped without Windows installed - certainly, in India, this ships often with only some form of DOS present.
    I'll go into more detail in the new thread.
    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC |
    The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

  • S20 *new* RAID config for retail Windows 7 install...questions

    I’ve recently ordered a S20 and I have a few questions about my situation/configuration, if anyone has the knowledge and time, I'd really appreciate it.
    I’ve configured the workstation to be shipped without an installed OS, a single SATA hard drive, and no optical drive.  I have a new retail copy of Windows 7 Professional that I will install, two Seagate 1TB SATA hard drives that I will install in RAID1 configuration, and a new DVD multi-recorder ready to install.  The drive that comes with the workstation will be used as well, but not as the boot drive.  I wish to boot off of a partition on the RAID1 set.
    I’ve looked into the hardware/user guides for as much information as I could find, but I’m not clear, and thus concerned, as to what I will need to do to get RAID setup with a boot partition and install Windows.
    I see that there are three SATA ports for hard drives on the main board. 
    1)  Can RAID be configured using ANY combination of these ports, and is the unused port still available for normal SATA drive hosting?
    For instance, can I configure two 1TB hard drives on the first two ports and configure a third non-RAID drive on the third port?
    I am now familiar with the BIOS RAID configuration utility from reading the guides.
    2)  How do I install an OS (Windows 7 32 or 64) on a new RAID partition, once it is configured, if my retail version of Windows doesn't have the driver?
    For instance, can I provide the driver during installation via the Windows 7 setup?
    I understand that there are also two SATA ports for optical drives on a separate controller (for five SATA ports total).
    3)  If I attach my DVD drive to one of the SATA ports intended for optical devices, will the system see it as a bootable device?
    I need to make my DVD drive a boot device in order to install windows, so I'm hoping that the system will see it that way.  I also hope that the SATA ports are labeled on the main board!  (Optical 0, 1 / Disk 0, 1, 2)  ???
    If anyone has the time to help me with these three questions I think I will be more at ease.  I worry about going off the path and ordering a blank machine, but I am adamant about a non-OEM OS.
    BTW, I am moving to the S20 from a five year old IntelliStation M Pro which is the best machine I've owned so far.  I also keep a ThinkPad X61 at my side.  Really looking forward to the new workstation!
    Cheers!
    Matt
    www.mattloweryphotography.com

    erik, thank you so much.
    I was thrown off by the Marvell driver in the S20 download page, I think.  Now I'm ready to go.
    Come on Lenovo...
    Matt
    www.mattloweryphotography.com

  • Vista Ultimate SP1 (retail dvd) will not install on new Mac Pro

    I wish to dedicate a new 1TB hard drive in Bay3 on a brand new Mac Pro for Vista Ultimate SP1, preferably 64-bit. I have tried several times to install a retail dvd version of Vista Ultimate with SP1 (both 32- and 64-bit) without success on two different hard drives (first the one in bay 3; then, after lack of success, the one in bay 4). The installation process does not proceed beyond the stage where Vista must format the hard drive. Vista always displays the message that Vista cannot be installed on a disk of the "GPT style." After giving up on the installation, the disk appears to Disk Utility as a "GUID" disk.
    I am seeking advice from anyone who might be able to help me proceed. The remainder of this message provides more detail about what I have tried.
    Before starting Boot Camp, I formatted the hard drives initially as MS-DOS FAT, and on later attempts, as Mac OS Extended (Journaled). Neither matters. After several attempts, I verified the functionality of the drives by partitioning them using Disk Utility and then repartitioning to one partition. Both 1TB drives appear healthy and can be partitioned and re-partitioned.
    When Bootcamp Assistant (BC) calls for the Vista disk, the Vista installation proceeds until the stage when Vista calls for me to identify a hard drive partition for installation. After selecting the largest partition on drive 2 (in bay 3; size 931GB) , the BC Installation and Setup Guide instructs me to "format" the partition. When I do so, the following Windows error message appears:
    "Windows cannot be installed to this disk. The selected disk is of the GPT partition style."
    Based on some forum comments, I also tried a different procedure at this stage of the Vista installation. Instead of choosing "format," I first chose to "delete" the selected partition. The disk then appears as "unallocated space." I then chose "new" and "apply" in the hope that it would create a correct NTFS partition for Vista. It then appears as Partition 2 of either Disk 2 (or Disk 3, which I tried subsequently). However, the subsequent "format" still yields the same error.
    I tried both procedures with Vista 64-bit and with Vista 32-bit. No difference.
    Suggestions most welcome.

    When I provided a link to threads about "Install Vista SP1 DVD" I knew and had in mind a couple threads where people have tried. And trying will help understand.
    You don't need to format as NTFS on another PC when just installing MacFuse plus 3G driver extensions will let you do so on your Mac Pro. And that is just one option. There are always multiple ways to get to the same place.
    Due to EFI changes there is a tool and tips on how to convert your DVD, but I didn't have time to go back and find and pull those together.
    Installing SP1 DVD attempt without success:
    http://discussions.apple.com/thread.jspa?threadID=1501656
    http://www.ezbsystems.com/ultraiso/
    MS OSCDIMG.exe
    Yes, it’s a fairly long process and requires you to download stuff (and be running Windows in the first place) But, it does work as long as you follow the instructions correctly.
    Convert DVD to ISO and prepare for EFI booting on Mac
    tried rebooting about 10 times. No luck. Finally I pointed Parallels (free trial available) to my blank bootcamp partition and set parallels to boot from CD before HD. Parallels booted the Vista install CD just fine, and put Vista on my HD. Crashed at the end though and said it couldn't make the boot camp partition bootable so all changes were removed. Rebooted under boot camp and the installer came up fine off the CD.
    So if you have this problem, and nobody else can help, and if you can find it, maybe you can download..... Parallels. Feel free to post this on the other threads. Unlike other workarounds I'm guessing this will work for everyone and it only takes a free trial download of parallels to give it a try. Still wish apple would acknowledge the problem and post a fix. Can't be that hard.
    I think VMWare Fusion also supports vitualization with the bootcamp partition as the target so that may help you get around this install bug in boot camp(or the mac's firmware) too.
    I would have thought that with Intel and Microsoft both saying they would begin to support UEFI with Vista SP1 64-bit, and Apple is part of the EFI Group, that "we're different" was a thing of the past. Instead it is harder.
    http://www.microsoft.com/windows/products/windowsvista/sp1.mspx
    Remember, Google is your friend (usually) - "Apple Vista SP1 64-bit DVD Install":
    MacBook Pro Vista SP1 64-bit Install:
    http://andersonshatch.wordpress.com/tag/vista-64-bit/
    Oh, and while I read Apple KB changes daily, I have never seen anything address Vista SP1 64-bit install, support, etc mentioned once. Am I missing something? or is it MIA?

Maybe you are looking for

  • Install error messages

    I get the following error messages when installing CS6. Anybody have any idea if this is a problem, or if these are components of the various programs that I will never need? Exit Code: 6 Please see specific errors and warnings below for troubleshoot

  • Starting SOA Suite server in debug mode

    Hello, anyone knows how to start soa suite server on debug mode? it basically oc4j server started from opmn. is there anyway i can pass the "-ojvm -XXdebug,port4000,detached,quiet" to opmn? Rudi

  • Apple Outreach to the Aging Community?

    Hello,   My mother in law is an intellectually active 80 year old who is, although sharp and an avid reader, never the less extremely intimidated by technology.  My wife and I are concerned that she is becoming increasingly isolated by her age, the d

  • Problem Connecting Developer Suite Form 9 with Oracle 9i Database

    Hi, I have a problem to connect Developer Suite Release 2 forms 9 with Oracle 9i database release 1. I have done net8 easy configuration but no success. The error is ORA-12514 TNS: Listener could not resolve SERVICE_NAME given in connect descriptor.

  • How to Create dynamic checkbox in line item

    Dear all,         In selection-screen i have using select-options  If i select select-option range, the output  will display dynamic check box in line item what range i have select above select options. Regards, Baskaran.