The Failed Attempt -- BeeHex 1.00 is out!




> Perhaps I did a no-no by using a hex-editor on the
> ISO [ wanted it to display "Kick-AsmOS!" ;-) ],
> but my CD acted like it might be booting but it wouldn't
> display any text nor wait for any keypresses and just
> simply caused a reset. Wouldn't boot on the laptop period.


Don't be sad. This is not a failure.
You just need to be proper re-educated.

Perhaps you should start making simpler things before
kicking the Asm-OS. I'm not quite sure if that's the right
way to make a kicking OS though, unless it is Trojan OS
that is a good landing ground for really kicking
format-resisting infections. Then it's truly a Kick...

Try a floppy - easy to edit - easy to investigate.

Here's an example, that does nothing but prints a
funny ASCII face, waits for any key and softly
reboots the computer:

INTEL 8086 MACHINE CODE:

B4 0E B0 01 CD 10 B4 00 CD 16 CD 19

Equivalent to assembly code:

MOV AH, 0Eh ; print like teletype
MOV AL, 1 ; ASCII code for a funny face :)
INT 10h ;
MOV AH, 0 ; wait for any key..
INT 16h ;
INT 19h ; soft boot

NOTES:
* IBM or 100% compatible PC is required.
* You may load this 12 byte binary file to emu8086 for investigation,
<< in fact it is highly recommended to test this on emu8086
before the actual test to save time and prevent
overwriting valuable data >>
* Don't forget to eject the floppy!

:)


MACHINE CODE EXPLANATIONS:
All values are hexadecimal.

B4 + <byte> = MOV AH, <byte>
B0 + <byte> = MOV AL, <byte>
CD + <byte> = INT <byte>
<byte> = immediate byte that follows.

You can create an empty file and then use BeeHex to enter
the 12 bytes, and then use WriteBin to write the file to a floppy,
from console type: writebin [filename]

The default output file for BeeHex is "temp.bin"
New "temp.bin" is created every time, old file gets auto-deleted!
To keep changes - close BeeHex and rename the file.

You can get both of these tools for free from here:

http://www.emu8086.com/BeeHex

There is "test.bin" in the pack that prints out "Hello, World!"
when it is witten to a boot record. 120 bytes.
See ReadMe.txt for more information.

Q: What to do if your system does not boot from floppy?
A: Do not use Linux's "Boot from floppy" option.
Instead set it temporary in BIOS to boot from floppy.

If you have a computer without a floppy drive, buy a USB floppy
drive. And set it in BIOS to boot from USB-Floppy. If you do not
have a floopy drive and your BIOS does not support booting from
USB devices, then go to eBay and buy some old computer for $20
for tests or call the manufacturer of your cool & kicking PC
for support and BIOS update.

To run BeeHex under Windows 95/98 it may be required to download
and install a specific system library:
http://www.emu8086.com/BeeHex/lib.html
Windows XP users generally do not require any additional files.

You have two choices, to read pages of High Level license or
to read a tiny tutorial and two lines licence for BeeHex:

BeeHex License
==============
Freeware. Use as you want. When distributing keep all files
together in Zip. Do not distribute modified or corrupted files.

.



Relevant Pages

  • Re: program to map out weak HD sectors?
    ... >>> I don't have a floppy drive or bootable CDROM. ... Bios Date is 1998. ... can't boot from it. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Cpq Presario 906
    ... which comes w/o the internal FDD. ... also has the 26-pin flexprint floppy connector on the mobo, ... properly detected during POST and the BIOS briefly scans the ... floppy in it BUT is too stupid to actually boot from it! ...
    (comp.sys.laptops)
  • Re: Cpq Presario 906
    ... which comes w/o the internal FDD. ... also has the 26-pin flexprint floppy connector on the mobo, ... properly detected during POST and the BIOS briefly scans the ... floppy in it BUT is too stupid to actually boot from it! ...
    (comp.sys.laptops)
  • Re: FC4 and Assembly Language Program
    ... i am about to make a bootable floppy for test ... #objcopy -O binary myos.o BOOT ... Does the BIOS actually contain the software interrupt code you are ...
    (Fedora)
  • Re: so I decided to remove SUSE 9.2 from my machine
    ... > If that works AND IF you correctly made a BOOTABLE floppy with Windows ... That will remove your old Master Boot Record. ... Now reboot and enter the BIOS as above and change your First Boot ... It must contain the Windows system files ...
    (alt.os.linux.suse)