In order to get checksums recalculated, replacing orom/oprom-modules cannot be done in cbrom. Manual microcode replacement in hex-editor (the microcodes have the same size (0x1000)) leads to “checksum”-errors when trying to flash using winphlash (different versions) or phlash16 (in DOS). wph/.rom-file, as well as PhoenixBiosEditorPro (version 2.2.1.3). MCExtractor (1.70.0) gives accurate information of. When trying nc_cpucode method in cbrom155 I get an error, that there was not enough space (strange - I thought microcodes would be replaced with that command, and newer microcodes have (in my case) the same size as the old ones) You can open the bios file with versions up to cbrom155.1, higher versions get stuck when trying to display bios information using command "cbromXX bios.wph /D"Įven in cbrom1551 or cbrom155 no table of modules is displayed (as it should be) - just cryptic information about ‘file size’/‘code space’ is shown. No matter if you use a) bios from Lenovo-website b) bios extracted from laptop c) modded bios from other source.
Later on I played around with PhoenixTool (SLIC Mod, 2.56) but no recalculated checksum or soĬBrom seems to be unable to handle.
hex-edit method (manual replacement of microcode after extraction with MCExtractor, same thread as above) nc_cpucode method for phoenix bios (using cbrom/different versions) from this thread ( How to update the CPU microcodes on a non-UEFI Award/Phoenix BIOS or …r-phoenix-bios/) Yeah! But the bios’ microcodes a bit outdated:/ So I tried to fix that. Background: CPU replacement has been done towards a T9300 (=new CPU, CPUID: 10676). I tried the beta above with the same non result.I tried a lot to update intel-microcodes for an old Lenovo G550 laptop. I know a bit of a reach and this guy must be in outer space but that is my thought process. I also noted that the word 'Display' is a hard search as Monitor or Graphics information comes up all the time even with a quoted ("display port") in the search and that coupled with the total lack of recognition of sound in the device manager made me wonder if the word 'display' is a proprietary name in the windows 10 device manager and it can't find it because when it reads 'display' it is looking for graphics monitor rather than sound. I downloaded this 'Intel Display Audio Driver' Rev 8.20.0.865 but I can't get a system to recognize it at all. On non working systems at initial build it would work until the first reboot. Again I have several system without sound and one system with sound. This may or may not be a related problem. I have a working build and multiple non working builds.ĭual Monitors: Asus VE248 with display port audio. Not meaning to intrude here but I have a related problem that is somewhat similar but different.
0 kommentar(er)
