User talk:89.243.142.119

Custom ARC firmware bios for the MIPS version
Do you have that custom bios? If so, is it possible to share it please? Just in case. TC1995 (talk)
 * Sent you an email. 89.243.142.119 16:26, 9 February 2022 (UTC)
 * Thank you. TC1995 (talk)

Stop requesting or begging for any downloads on this wiki? Bubblebeam (will be renamed to Uncle Captain on May 16) (talk) 03:01, 11 February 2022 (UTC)
 * This is nowhere close to begging? It was a simple request for a Bios file. Xeno (talk) 03:02, 11 February 2022 (UTC)
 * Oh OK. But, the guidelines still say “Do not request any downloads on this site (but I don’t know about the BIOS files)”. Bubblebeam (will be renamed to Uncle Captain on May 16) (talk) 03:04, 11 February 2022 (UTC)
 * Unless the rules suddenly get rewritten. They only mention builds, not any tools and whatnot. Xeno (talk) 03:09, 11 February 2022 (UTC)

Some notes on symbol server binaries
I'm putting this here due to being unable to create pages without an account.

Getting a binary from the MS symbol server:

where x = PE TimeDateStamp %08x, y = PE SizeOfImage %x.

It seems that for insider builds, for certain files (using  as an example here) if there are no code changes (that is, PDB symbol GUID hasn't changed) the TimeDateStamp in the PE does not change.

TimeDateStamp (after the reproducible builds changes in rs2) was claimed by Raymond Chen to be "a hash of the binary", but that seems to not be entirely true.

By analysing diffs from the previous build (available via UpdateMetadataService for builds in *_release branches only; it's possible it's available via ClientWebService too if you tell it you're the previous build), the changes between 22562 and 22563 bootmgr.efi are: ...and that is all. No code change, no GUID change.
 * PE checksum (0x148-0x14B), although the high byte is unchanged
 * Version number in resources
 * Signature

Retrieving "this same binary" from the symbols server gives a file from build 22564, with a server-side modify date of Thu, 24 Feb 2022 21:32:36 GMT.

This means that the TimeDateStamp is not derived from the entire binary, but only parts that doesn't change. Possibly the hash is of all readable+executable sections, or of just the debug directory.

Some others:
 * 22543 bootmgr gets 22544
 * 22557 bootmgr gets 22559
 * 21996 bootmgr gets 22000.5 ~210707, this shows that this phenomena exists with prodsigned files too.
 * 22000.51 bootmgr gets 22000.53 ~210628

Hopefully this research helps someone... 89.243.142.119 15:03, 27 February 2022 (UTC)


 * It seems only files of subsystem windows boot application/efi boot application/efi driver get updated in this way. Getting build 22567's HAL.DLL, NULL.SYS, REGEDT32.EXE all get files from build 22561. 89.243.142.119 19:09, 2 March 2022 (UTC)

Bootmgr updates on symbol server
AMD64 bootmgr with TimeDateStamp 0x3a80c55e, SizeOfImage 0x255000 (earliest build known to use this is 22562, see 22562-22563 deltas; it was probably recompiled for 22560-22561 to fix the symbol GUID bug): 89.243.142.119 18:25, 2 March 2022 (UTC)
 * 22564 uploaded, replacing unknown build (probably 22563?): 2022-02-24 21:32:36
 * 22567 uploaded, replacing 22564: 2022-02-27 18:55:08 (hours after the above research got posted) (sorry, didn't save to wayback machine)
 * 22569 uploaded, replacing 22567: 2022-03-02 17:11:49 (~1 hour before 22567 release)

Boot applications for 22610 being updated on symbol server:
 * 22612.1 (~220428):
 * bootmgr.efi
 * cdboot.efi
 * cdboot_noprompt.efi

89.241.109.169 18:23, 29 April 2022 (UTC)