Recommended Posts

How-To Change Boot Screen on Win7

- First, Use ResHack with %windir%\system32\bootres.dll file

- Extract the RCData resource.

- So you have two files, one *.rc and another one *.bin

- Rename the file *.bin into *.wim (not win!!)

- Use 7zip to extract your *.wim file

- In the extracted files you have an xml witch describe the second file witch is the boot logon bitmap animation!!!

Now you can modify the logon animation! But be carefull, to have a correct xml description file!!!

After modifications, do the inverse procedure, with a backup of your original bootres.dll file.

I advise you to try on a virtual machine before!

PS : Microsoft do not recommend to change it!!!

Link to comment
https://www.neowin.net/forum/topic/806920-how-to-change-boot-screen-on-win7/
Share on other sites

  • 2 months later...
  • 3 weeks later...

I'm assuming this is the glowing Windows logo?

A bitmap can be "animated" by containing "frames" of the animation next to each other, the application reads a "frame" every so many pixels across or down the file. That's just speculation for me, I don't have Win7 RTM to try this out with.

  • 2 months later...
  • 1 month later...

How-To Change Boot Screen on Win7

- First, Use ResHack with %windir%\system32\bootres.dll file

- Extract the RCData resource.

- So you have two files, one *.rc and another one *.bin

- Rename the file *.bin into *.wim (not win!!)

- Use 7zip to extract your *.wim file

- In the extracted files you have an xml witch describe the second file witch is the boot logon bitmap animation!!!

Now you can modify the logon animation! But be carefull, to have a correct xml description file!!!

After modifications, do the inverse procedure, with a backup of your original bootres.dll file.

I advise you to try on a virtual machine before!

PS : Microsoft do not recommend to change it!!!

1) How do I put the modified image back into the *.wim archive (7zip shows an error message that reads "incompatible interface")?

2) How do I put the *.rc and *.bin (*wim renamed back into *.bin) back into the bootres.dll?

EDIT: Instead of extracting the *.wim with 7zip (7zip can't compress *.wim archives) it's better to mount it r/w with gimagex (you'll need to download the WAIK first), copy the *bmp file out, modify it, put it back into the archive and unmount it with the "commit changes" option.

I'm still wondering how to put the *.bin (*.wim archive) and *.rc files back into the bootres.dll.

I have been able to extract, manipulate and repackage this files. My question is this:

How are you certifying the file as proper by MS standards? I have been able to pull out the CERTIFICATE but after inserting it into the DLL, the system still won't recognize it properly (I am assuming this based on outcome of the process, Vista loading worm only).

The other option is this:

If you were to select NOGUIBOOT as in previous versions of Windows, what could we use to load a static image? Any thoughts on this?

Even better....how about a replacement for the Vista loading worm? any ideas on THIS? All I really need is for a static image to display in reasonable resolution. Anyone know of a location to "load" an image to get this to happen?

I am not opposed to searching google either. I have run a laundry list of searches that have given a thousand results, none specific enough to be considered really helpful. Figured I would bounce this off where I found the most helpful information.

-Surfer

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • lots of people us facebook for stuff, threads though no
    • Can you read? I've said I'm willing to pay more for a notchless (no notch) 3:2 screen.
    • Not even an OLED display on the laptops. Also it seems that the laptop design isn't the same as the Surface Ultra model. Looks like bargain bin at high prices.
    • make your own notch - it's not that hard
    • VirtualBox 7.2.10 by Razvan Serea VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Presently, VirtualBox runs on Windows, Linux, macOS, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, 7, 8, Windows 10 and Windows 11), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x, 4.x, 5.x and 6.x), Solaris and OpenSolaris, OS/2, OpenBSD, NetBSD and FreeBSD. Some of the features of VirtualBox are: Modularity. VirtualBox has an extremely modular design with well-defined internal programming interfaces and a client/server design. This makes it easy to control it from several interfaces at once: for example, you can start a virtual machine in a typical virtual machine GUI and then control that machine from the command line, or possibly remotely. VirtualBox also comes with a full Software Development Kit: even though it is Open Source Software, you don't have to hack the source to write a new interface for VirtualBox. Virtual machine descriptions in XML. The configuration settings of virtual machines are stored entirely in XML and are independent of the local machines. Virtual machine definitions can therefore easily be ported to other computers. VirtualBox 7.2.10 changelog: VMM: Fixed issue when CentOS 10 VM was not booting due to the message "Fatal glibc error: CPU does not support x86-64-v3" (​github:gh-642) Devices/EFI: Fixed booting issue when ARM VM had less than 1024 MiB of RAM assigned (​github:gh-679) USB: Fixed issue when it was not possible to attach USB device to headless VM on Apple Silicon/macOS 26.4.1 (​github:gh-631) Storage: Fixed issue when VIRTIO-SCSI device was not recognized as SSD device by guest system (​github:gh-634) Network: Fixed issue in E1000 emulation code which triggered debug log creation (​github:gh-645) Network: Fixed issue in E1000 emulation code which prevented OS/2 guest from booting (​github:gh-683) Linux Host: Fixed issue when VMs could not be started due to kernel oops (​github:gh-639) Linux Host and Guest: Fixed issue when kernel modules were failing to build with openSUSE 16.0 kernel Linux Host and Guest: Added initial support for kernel 7.1 Linux Host and Guest: Added extra fixes for RHEL 9.8 kernel (​github:gh-676) Linux Host and Guest: Added possibility to build source code using NASM instead of YASM as the assembler (​github:gh-520) Linux Guest Additions: Added initial support for Extended Data Control Protocol for clipboard sharing with Plasma on Wayland guests (​github:gh-33) Linux Guest Additions: Added extra fixes for preventing vboxvideo kernel module build with kernel version 7.0 and newer (​github:gh-655) OS/2 Guest Additions: Fixed issue when Shared Folders automount and clipboard sharing stopped working (​github:gh-551) Download: VirtualBox 7.2.10 | 170.0 MB (Open Source) Download: VirtualBox 7.2.10 Extension Pack | 19.1 MB View: VirtualBox Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      suprememobiles48 earned a badge
      Week One Done
    • One Month Later
      Windows Guy earned a badge
      One Month Later
    • One Month Later
      Prasann earned a badge
      One Month Later
    • Week One Done
      Prasann earned a badge
      Week One Done
    • First Post
      Dys Topia earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      510
    2. 2
      +Edouard
      174
    3. 3
      PsYcHoKiLLa
      102
    4. 4
      Steven P.
      87
    5. 5
      ATLien_0
      70
  • Tell a friend

    Love Neowin? Tell a friend!