Re: Accessing bios information (windows)

Dirk Wolfgang Glomp wrote:
Am Wed, 27 Aug 2008 20:13:17 +0100 schrieb Sean Farrow:

Hi:
I need to get hold of the bios date/serial number.

How can i find the adress of those serial number?

Dunno about "serial number". We can get bios date and version. I recall a "privacy flap" about "serial numbers"... IIRC they compromised by making access to the serial number "off" by default. I have no idea how to get it, if any...

I don't have a 16-bit asm compiler if that's what I need.

16-bit assembler:
[NASM]
http://sourceforge.net/project/showfiles.php?group_id=6208

Just to clarify, you do *not* want the obsolete, no longer supported, "16 bit dos" build! The 32-bit dos build would work(?), but the Windows build - way down at the bottom of the page - is probably what you want. Any of 'em will output 16-bit code. If you make a .com file, you won't need a 16-bit linker.

[MASM]
A search with google shows these result: [masm51.zip]
http://www.bbs.motion-bg.com/index.php?file=431

It is also possible to use MASM 6.x(need windows) and link
the *.obj-file with the linker from MASM5 to get a 16-bit executable.
MASM 6.x provide MMX/XMM/3DNOW.

You might also look at:

http://www.japheth.de/JWasm.html

Japheth's "free and open source" equivalent... (for those who care about such things).

Any help apreciated.

To get some bytes from the Bios, we don´t need any compiler/assembler,
debug is usefull enough:
debug
- o70 0
- i71
...<-SECONDS
-q

RBIL->inter61d.zip->Cmos.lst
----------R00--------------------------------
CMOS 00h - RTC - SECONDS
Desc: (BCD 00-59, Hex 00-3B)
Note: Bit 7 is read only
SeeAlso: CMOS 01h,CMOS 02h,CMOS 04h
-----

Oh, a port access at 70h/71h is also possible with the DOS-box from
Windows2000.

Good point. Untested, but we should be able to write/read those ports in Linux, after getting "permission". Dunno if we can get bios version/date from that (*current* date, yes)... Could use debug to examine memory, too... (d f000:fff5 ?)

There's a file...

http://home.comcast.net/~fbkotler/seemem.zip

(source and executable for two OSen and documentation - 10k - Thanks, "Annie"!)

That will allow you to poke around in memory. Dunno how well it will work in a modern Windows "dos box"... (might give you a clue how to write such a thing, if that's what you want to do, Sean)

Best,
Frank

.

Relevant Pages

  • Re: MAKEINTRESOURCE
    ... few bytes here and there to keep from overflowing a 64K data segment was ... My memory of those days is fuzzy now (I once knew this ... "far" keyword you still see in many of the Windows headers to this day). ... this was more of an issue for DOS than it ...
    (microsoft.public.vc.language)
  • Re: screenshots
    ... Back in the days of DOS, the PrtScn key used to print the screen. ... press alt-PrtScn to capture an image of the active window. ... captures the image to the Windows clipboard (in memory). ...
    (microsoft.public.windows.vista.general)
  • Re: can the loading of a large number of records go as quick as in DOS
    ... that loading a large number of records is not as quick as in DOS. ... The diference between the DOS-and Windows program is probarbly caused ... these records all the time in memory. ... Am I right and is there a solution for the delaying loading in the ...
    (microsoft.public.vb.general.discussion)
  • Re: Ram Drive
    ... DOS did not do pre-emptive multi-tasking. ... Data is literally left in memory ... > Is it possible to setup a ramdrive in Windows XP? ...
    (microsoft.public.windowsxp.general)
  • Re: Linux syscalls
    ... > A device driver or a rewrite of DOS could permit this, ... really "DOS inside Windows" or "Windows inside DOS"? ... > DOS interrupts are revectored... ... if you re-write DOS to use the _Windows device drivers_ ...
    (alt.lang.asm)
Loading