I have Realflight G3 simulator, has been working fine on my old XP. KEError 92994 serial numbers are invalid or missing, you must run.
![]()
Show Hide Menu. Activation. Serial Numbers do not appear to work. Summary Once installed, RealFlight requires the G5 serial number and an InterLink serial number. If these numbers are not typed in exactly as they appear on the serial number sticker, RealFlight G5 will not run.
Resolution The RealFlight G5 serial number has the following format: ########-G5-########## That is an eight digit number, followed by a dash, 'G5', another dash and finally a ten digit number. This number is located on the back of the RealFlight G5 disc case.
The InterLink serial number will have one of the following formats:. G3 InterLink Plus: #######-I2-######. G4/G5 InterLink Elite: #######-I3-###### Please note that the InterLink serial number contains the letter ' I' and not the number 1 for the middle section. This serial number is located on the back of your InterLink controller.
Hi folks, I've saved an old Thinkstation P500 by doing a jumper reset on the motherboard. My bios now shows invalid machine type and serial number. Articles and videos on the web say (and show) that there are prompts for this during a bios firmware upgrade.
However when I upgraded mine from A4KT80A to A4KT99A last night, it went straight to the upgrade and offered no prompts to do so! Is there a hotkey I need to hit or something? I also found a Lenov article with AMIDOS commands to repopulate this information, and I have AMIDOS with the firmware upgrade kit, but I'm not sure how to boot to AMIDOS instead of the firmware upgrade script. Any help greatly appreciated! Link to youtube video showing bios upgrade promts (which I don't get): Link to lenovo article showing AMIDOS commands.
You should be able to use AMIDEDOS.EXE to set the MT + SN, but to do so you'll need to be able to boot DOS and not the EFI shell. Can you tell me what your current BIOS settings are for the following settings: - In the exit tab/menu, what's the setting for OS Optimized Defaults? - In the startup tab/menu, is the CSM enabled? - If CSM is enabled, what is the setting for the Storage OPROM under CSM settings/configuration (Legacy or UEFI)? We need to know what mode your BIOS is in to make sure you can boot to a USB (DOS) key.
Alternatively, you could use the AMIDEEFIx64TS.efi tool to set those items as well if your system is in UEFI mode (i.e. OS Optimized Defaults set to enabled, or storage CSM set to UEFI).I'm just not sure off the top of my head if that particular flash package comes with that tool or not. Hi psuturtle, Yes, I'm running Linux Mint in UEFI mode.
I should have considered that AMIDEDOS wouldn't be compaitlbe (assuming it's a portable flavor of DOS). OS Optimized Defaults: Enabled CSM: Disabled - Does it make a difference which way (UEFI or legacy) I boot to the utility key for purposes of updating Machine Type and SN? - If' I'm guessing correctly, I should be able to set my system in legacy mode, boot to the key and input this information -. could I put the UEFI files into the root of the key and boot in UEFI mode. Am I way off?
I'm assuming you downloaded the ' from the support site? If so, that should have the correct files on it to boot to the EFI shell and run the tool from there once you create the key Since your BIOS is currently set up for full UEFI mode (OS Optimized Defaults = enabled), this is probably easiest. Note that you might need to turn Secure Boot off for this process.
Once you boot to the UEFI key, you'd want to change to the AFU directory and then run the following commands: AMIDEEFIx64TS.efi /ss '1234566' (where 12345667 is your actual serial number, 7 digits) AMIDEEFIx64TS.efi /sp 'abcdefg' (where abcdefg is your machine type model, 7 digits/characters) You can alternatively run AMIDEDOS.exe, but to do so you'd have to switch your system over to Legacy mode temporarily to run the tool and then switch it back when done. I'd personally just use the EFI shell. Hi psuturtle, Yep that's the file I have. I extracted all those files to the root of a clean usb key and booted. It updates the bios then exits, after which, my machine immediately reboots twice and then boots my linux OS - leaving me no opportunity to run the AMIDEEFIx64 utility. Looking at the UEFI starup batch file ('EFI/BOOT/startup.nsh'), I don't see any reboot command at the end, so I'm confused why the script doesn't just exiting to a prompt.
I must have something set incorrectly in my bios. I'm going to reformat my key, place a new set of the files from your link onto it, and try again. I'll let you know what happens. And thanks again for your help!
This has me scratching my head at the moment. This process worked like a champ on my system, though I was checking on the newer platforms. Let me see if I can dig up an older P500 system to see if the platform is actually making a difference here. Out of curiosity, when you are typing in the file name in the shell, are you using tab to have it auto-populate? Everything in your command line looks exactly like what I'm doing, as does the structure in your AFU directory. Just seems odd that it almost acts like it is not even recognizing the.efi file as a valid tool/file. Hi psuturtle, SUCCESS!!!
Ok, as I suspected the issue was with my 'chair-to-mouse interface' (me). I'm not at home right now, so i can't tell you how I got that error yesterday, however I do know why my previous (and proper) attempt to run AMIDEEFIx64TS failed. Here is where I went wrong: 1.) Boot to the startup USBKey 2.) System boots to EFI/BOOT/bootx64.efi 3.) System prompts user to interrupt bios firmware update with countdown 4.) User hits key to interrupt and is dumped to the shell 6.) User immediately tries to run AMIDEEFIx64TS - gets 'Command not recognized'. Basically, I needed to first mount a temp drive, which is what the first several if/then directives in the script look for. Here is what I was missing: 5) User issues command 'fs1:' to mount temp filesystem. After that, the command ran perfectly! I stared at EFI/BOOT/startup.nsh for a while to understand what I was missing.
I hadn't considered that I could be in a shell and not have any filesystem mounted - and the command error message wasn't helping much. Thanks again for all your help!!!
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |