Author Topic: [SOLVED]Windows: BUG not make sense with NASM ver 2.11.05 and NASM ver 2.10.05  (Read 4850 times)

Offline shaynox

  • Full Member
  • **
  • Posts: 117
  • Country: fr
  • use Windows 10 x64
Hello everyone i want to tell you a big big BUG with those version of NASM.

I have wrote operating system in 2012 full assembly with NASM, and assembly this with ver 2.10.05. And all work when i run it on PC (no qemu).

Two year later, i assembly again my OS with latest version of nasm (2.11.05), but when i start it, it's reboot immediatly after that i jumped to my kernel:
"Appuyer sur une touche pour charger le kernel"/"Press a key for load kernel"

I use HxD http://mh-nexus.de/en/hxd for copy HackOS.bin in my USB

PS: I'm french so you risk to don't understand commentary, sorry :(
keyboard: azerty mode in my OS
« Last Edit: October 01, 2014, 06:07:54 PM by shaynox »
Basic asm standard:
reg(lowercase) - instruction(lowercase) -> instruction     dest, src

Offline Frank Kotler

  • NASM Developer
  • Hero Member
  • *****
  • Posts: 2379
  • Country: us
Re: Windows: BUG not make sense with NASM ver 2.11.05 and NASM ver 2.10.05
« Reply #1 on: September 02, 2014, 06:08:47 PM »
Okay, I'll bite. What's the "BUG"?

I see two .bin files which differ. At first glance, the bootloader parts appear to be identical. The kernel parts appear to differ by a word 0x1000 in several places. Perhaps by coincidence, this is the "org" of your kernel file. I have not tracked down where in the code this is coming from. I'll look some more but - have mercy, Shaynox - give me a hint what you think I should be looking for.

Best,
Frank


Offline shaynox

  • Full Member
  • **
  • Posts: 117
  • Country: fr
  • use Windows 10 x64
Re: Windows: BUG not make sense with NASM ver 2.11.05 and NASM ver 2.10.05
« Reply #2 on: September 02, 2014, 06:15:28 PM »
Hi,

Well those binary are assembly from the same files, use batch in 2.MAKE.
And this batch use nasm, one with recent (don't work) version and other the older (work).

I put 2 ORG, because i assembly Bootloader.asm and Kernel.asm separately, then i copy those bin in one: HackOS.bin with: copy /b in console.

Thanks for your interest
« Last Edit: September 02, 2014, 06:35:42 PM by shaynox »
Basic asm standard:
reg(lowercase) - instruction(lowercase) -> instruction     dest, src

Offline Frank Kotler

  • NASM Developer
  • Hero Member
  • *****
  • Posts: 2379
  • Country: us
Re: Windows: BUG not make sense with NASM ver 2.11.05 and NASM ver 2.10.05
« Reply #3 on: September 02, 2014, 06:59:33 PM »
Well, yes. Of course batch files don't work for me, nor does "copy /b". I have, however, assembled your kernel.asm with nasm-2.10 (nearest I had on hand) and nasm-2.11.05. They are identical. I'm claiming that the problem is on your end. I'm willing to be proven wrong...

Best,
Frank


Offline shaynox

  • Full Member
  • **
  • Posts: 117
  • Country: fr
  • use Windows 10 x64
Re: Windows: BUG not make sense with NASM ver 2.11.05 and NASM ver 2.10.05
« Reply #4 on: September 02, 2014, 07:09:10 PM »
Re,

I use HxD for show you what the difference of assembly in those binary, 2sec ^-^
Basic asm standard:
reg(lowercase) - instruction(lowercase) -> instruction     dest, src

Offline shaynox

  • Full Member
  • **
  • Posts: 117
  • Country: fr
  • use Windows 10 x64
Re: Windows: BUG not make sense with NASM ver 2.11.05 and NASM ver 2.10.05
« Reply #5 on: September 02, 2014, 07:15:57 PM »
well, there are too many difference omg, only byte size :o

Can you use HxD or same software ?

And can you upload yours binary please ? for test

Thanks
« Last Edit: September 02, 2014, 07:19:26 PM by shaynox »
Basic asm standard:
reg(lowercase) - instruction(lowercase) -> instruction     dest, src

Offline Frank Kotler

  • NASM Developer
  • Hero Member
  • *****
  • Posts: 2379
  • Country: us
Re: Windows: BUG not make sense with NASM ver 2.11.05 and NASM ver 2.10.05
« Reply #6 on: September 02, 2014, 07:47:28 PM »
I don't know what "HxD" is. What do you think the "BUG" in Nasm is?

I can not attach a .bin file. I could zip it/them up. Doesn't seem worthwhile. What I could do is install 2.10.05, but if there was a bug in 2.10.05 that was allowing your OS to work, it's gone now.

Best,
Frank


Offline shaynox

  • Full Member
  • **
  • Posts: 117
  • Country: fr
  • use Windows 10 x64
Re: Windows: BUG not make sense with NASM ver 2.11.05 and NASM ver 2.10.05
« Reply #7 on: September 02, 2014, 07:53:42 PM »
:D, yeah i think this possibility one moment, but sound like crazy :D

Thanks for your help, i will try to found the bug later because i don't working on my OS at the moment honnestly.

Actually i work on 3D engine with the same base of my OS, and it's work with the latest nasm, strange :o

I don't know if it can help you, but 3D engine run on 32 bit, and my shell run on 64 bit.


PS: HxD is a Freeware Hex Editor and Disk Editor: http://mh-nexus.de/en/hxd/
« Last Edit: September 02, 2014, 08:09:37 PM by shaynox »
Basic asm standard:
reg(lowercase) - instruction(lowercase) -> instruction     dest, src

Offline shaynox

  • Full Member
  • **
  • Posts: 117
  • Country: fr
  • use Windows 10 x64
Re: Windows: BUG not make sense with NASM ver 2.11.05 and NASM ver 2.10.05
« Reply #8 on: September 02, 2014, 11:34:44 PM »
Back, well i found the problem :D i'm sorry i used snapshots instead releasebuilds haha,
and it's work with releasebuilds nasm 2.11.05  :P

is snapshots is like beta ?

Sorry again :p

Thanks for your patience.

Bye
Basic asm standard:
reg(lowercase) - instruction(lowercase) -> instruction     dest, src

Offline Frank Kotler

  • NASM Developer
  • Hero Member
  • *****
  • Posts: 2379
  • Country: us
Hi Shaynox,
Sorry for the delayed reply. Yeah, I guess you could say a snapshot is like a beta. Actually maybe a "release candidate" is more like a beta. A snapshot is just "whatever the code is" on that date. Even the purportedly "stable" releases aren't guaranteed to be bug free. A snapshot "should" be useable in most cases, but obviously not this time. Sorry you ran into a bad one.

There's a large and expanding "test suite", but still most(?) bugs are found by users assembling their own projects. We do appreciate your feedback, even though you didn't get a very helpful response here. Hope it goes smoother from here on.

Best,
Frank