Atom-15 flashed patched bios, but no effect

[punkysuen]

I successfully installed crt_emudriver and everything works, then I want to try ATOM-15.

I followed the guide and flashed R9 260X.
    1) cd C:\atiwinflash
    2) atiflash -s 0 bios.rom
    3) Use atom-15.exe to patch the BIOS.
    4) atiflash -p 0 bios-mod.rom
    5) Reboot
Every step is done without issues. However, after reboot, there is no effect, I still see a boot screen with triple splits (which should be 1024x768 I guess).

Any advice?

Update#1:
uploaded the bios.rom.txt, bios-mod.rom.txt

Update#2:
uploaded the bios files
cmd screens

[buttersoft]

Post the BIOS file and the modded file - or just run a comparison yourself in a hex editor like HxD and see if you can see what's changed.

After that... IDK. You are ticking the right box to mod the BIOS, the 15kHz only box?

[punkysuen]

Thank you.
I will post the files when return home.
I ticked 15KHz box only, as my CRT accepts 15KHz only.

[punkysuen]

Post the BIOS file and the modded file - or just run a comparison yourself in a hex editor like HxD and see if you can see what's changed.

After that... IDK. You are ticking the right box to mod the BIOS, the 15kHz only box?

I uploaded two .txt files.
Do I need to upload bios rom files?

Thank you.

[buttersoft]

Let's say yes. I really don't know if i'd be able to do anything besides a side-by-side comparison, but maybe Calamity will see more in them.

[punkysuen]

I found something interesting.
#1 machine: R7 260X, Windows 10, JVC CRT, crt_emudriver works fine
During the ATOM-15 process, the cmd shows nothing after "atiflash -p 0 bios-mod.rom"

#2 machine: R7 260X, Windows 10, MVS-U4, crt_emudriver works fine
When I proceed the command "atiflash -p 0 bios-mod.rom", I saw something shown on the screen and told me to reboot to complete the Bios update.
I did so, and the screen shrinked a lot.
Then, I went back to cmd and flashed back to the original image, and things back to normal.

[buttersoft]

If you mean the picture is squashed vertically like the screenshot in the OP (please add relevant pics to relevant posts ) this is something that happens sometimes. Turning off Windows 10 fast start in the first step (google that). Then restart. If that doesn't fix it, it's probably caused by changing hardware, and turning EDID emulation on an off should fix it. If not, try using VMM to setup modelines again, or installing crt_emudriver again.