muckyfingers
Professional
- Thread starter 300wins
- Start date
Thanks very much to everyone involved in getting this new version of firmware for us to use 
One thing I noticed afterwards is a very slow boot time, this is due to the Intel Management Engine and the secondary network interface, both can be safely disabled in Device Manager. I tried to find a compatible driver but had no luck, maybe there is a BIOS setting I missed to enable or disable the Intel MEI?
One thing I noticed afterwards is a very slow boot time, this is due to the Intel Management Engine and the secondary network interface, both can be safely disabled in Device Manager. I tried to find a compatible driver but had no luck, maybe there is a BIOS setting I missed to enable or disable the Intel MEI?
muckyfingers
Professional
Thanks very much to everyone involved in getting this new version of firmware for us to use
One thing I noticed afterwards is a very slow boot time, this is due to the Intel Management Engine and the secondary network interface, both can be safely disabled in Device Manager. I tried to find a compatible driver but had no luck, maybe there is a BIOS setting I missed to enable or disable the Intel MEI?
Confirmed working, disabling those 2 things makes it a speedy boot up, just like before.
Lemony Vengeance
Champion
Anyone update this via USB boot and CLI? I would rather do it that way and would like to know what the switches would be to do it properly.
below is the contents of the CLI bios update tool's read me. if anyone could help with the correct switches, It would be much appreciated.
below is the contents of the CLI bios update tool's read me. if anyone could help with the correct switches, It would be much appreciated.
Code:
Usage (applies to AFUWIN, AFUDOS, AFUEFI and AFUEFI64...
for usage of AFUBSD and AFULNX see help files provided in their folders):
------------------------------------------------------------------
AFUDOS <BIOS ROM File Name> [Option 1] [Option 2]
Or
AFUDOS <Input or Output File Name> <Command>
Or
AFUDOS <Command>
BIOS ROM File Name
The mandatory field is used to specify path/filename of the BIOS ROM file with extension.
Commands
The mandatory field is used to select an operation mode.
- /O Save current ROM image to file
- /U Display ROM File's ROMID
- /S Refer to Options: /S
- /D Verification test of given ROM File without flashing BIOS.
- /OAD Refer to Options: /OAD
- /A Refer to Options: /A
- /CLNEVNLOG Refer to Options: /CLNEVNLOG
Options
The optional field used to supply more information for flashing BIOS ROM. Following lists the supported optional parameters and format:
- /MEUL: Program ME Entire Firmware Block, which supports
Production.BIN and PreProduction.BIN files.
- /Q Silent execution
- /X Don't Check ROM ID
- /CAF Compare ROM file's data with Systems is different or
not, if not then cancel related update.
- /S Display current system's ROMID
- /JBC Don't Check AC adapter and battery
- /HOLEOUT: Save specific ROM Hole according to RomHole GUID.
NewRomHole1.BIN /HOLEOUT:GUID
- /SP Preserve Setup setting.
- /Rn Preserve SMBIOS type N during programming(n=0-255)
- /R Preserve ALL SMBIOS structure during programming
- /B Program Boot Block
- /P Program Main BIOS
- /K Program all non-critical blocks.
- /N Program NVRAM
- /Kn Program n'th non-critical block(n=0-15).
- /HOLE: Update specific ROM Hole according to RomHole GUID.
NewRomHole1.BIN /HOLE:GUID
- /L Program all ROM Holes.
- /Ln Program n'th ROM Hole only(n=0-15).
- /E Program Embedded Controller Block.
- /OAD Delete Oem Activation key
- /A Oem Activation file
- /E Program Embedded Controller Block
- /ECUF Update EC BIOS when newer version is detected.
- /ME Program ME Entire Firmware Block.
- /MEUF Program ME Ignition Firmware Block.
- /CLNEVNLOG Clear Event Log.
- /CAPSULE Override Secure Flash policy to Capsule
- /RECOVERY Override Secure Flash policy to Recovery
- /EC Program Embedded Controller Block. (Flash Type)
- /CMD: Send special command to BIOS. /CMD:{xxx, xxx, xxx}
- /REBOOT Reboot after programming.
- /SHUTDOWN Shutdown after programming.
- /FDR Flash Flash-Descriptor Region.(*1)
- /GBER Flash GBE Region.(*1)
- /MER Flash Entire ME Region.(*1)
- /OPR Flash Operation Region of SPS.(*1)
- /PDR Flash PDR Region.(*1)
(*1)If BIOS ME Module have report, AFU will be show this command.
Rules
- Any parameter encolsed by < > is a mandatory field.
- Any parameter enclosed by [ ] is an optional field.
- <Commands> cannot co-exist with any [Options].
- Main BIOS image is default flashing area if no any option present.
- [/REBOOT], [/X], and [/S] will enable [/P] function automatically.
- If [/B] present alone, there is only the Boot Block area to be updated.
- If [/N] present alone, there is only the NVRAM area to be updated.
- If [/E] present alone, there is only the Embedded Controller block to be updated.Lemony Vengeance
Champion
that's the same command I had lined up before hesitating.. minus the /L switch. I wasn't sure on that one, either.
mugen_ketsueki
Professional
Would anyone help me find suitable ram that can work with the ttx3? Would like 16gb but everywhere I can't find anything to purchase ram.
war3zlod3r
Enthusiast
I think this should be suitable https://www.amazon.com/Kingston-Technology-240-Pin-Memory-KVR13N9S8/dp/B008CP5Q7M
Hackcell
Grand Master
What would be a 8GB per module option?
Keep in mind you'll need to consider if the ram module is high or low density. Although TTX3 came mostly with Intel based Sandy bridge CPU's, not sure if TTX3 motherboards were 40, or 50 series which do not support high density variety, which in turn will not be compatible with later reisions of DDR3 modules that ARE compatible with 67 Series.
Sum it up:
Intel 50 series and prior chipsets supported only DDR3 2Gbit components. 60 series and later chipsets worked with 2Gbit / 4Gbit
Kingston KVR13N9S8/4 is 4Gbit module and should work as long as TTX3 is a 67 series motherboard.
Hackcell
Grand Master
what brand/model of memory did you use?
300wins
Professional
I just bought some Patriot Viper DDR3 Ram from Amazon.com
Like this: https://www.amazon.com/gp/product/B008LTJJJ0/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
Like this: https://www.amazon.com/gp/product/B008LTJJJ0/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
Does anyone have a dump of the earlier b16 or b13 bios by chance? I'm trying to diagnose an issue where since updating my x3 to the b23 bios it shutsdown after about 30 minutes of run time.
I'm running a non-uefi gtx680 and it didn't do this on the old bios
I'm running a non-uefi gtx680 and it didn't do this on the old bios
mR_CaESaR
Champion
Does anyone have a dump of the earlier b16 or b13 bios by chance? I'm trying to diagnose an issue where since updating my x3 to the b23 bios it shutsdown after about 30 minutes of run time.
I'm running a non-uefi gtx680 and it didn't do this on the old bios
I had a similar behaviour like that with the original AH multi when FastIO was used and was in attract mode (not in game). I couldn't replicate the issue with JVS though. IIRC it was due to the one of the pins in the header and when it was removed, it no longer rebooted. A newer version of the base windows was then used and no longer had that issue - which I also believe is what's used in the newer multis.
Maybe the base windows from b23 needs to be used so this shutdown issue is not present - I have no real evidence to support the claim though
So far I've tested the b23 and b16 bios with the latest multi - fastio only
It will shutdown, not reboot and it doesn't matter if it's in attract mode, in game or even browsing in windows explorer.
I will try removing components and test it, nothing is overheating so I have excluded that as a cause and the power supply is a brand new 650w seasonic.
fun and games lol
It will shutdown, not reboot and it doesn't matter if it's in attract mode, in game or even browsing in windows explorer.
I will try removing components and test it, nothing is overheating so I have excluded that as a cause and the power supply is a brand new 650w seasonic.
fun and games lol
war3zlod3r
Enthusiast
