Page 1 of 2

Kernel Editing Problems

Posted: Sun Sep 12, 2010 7:34 pm
by bigttcool2
'Hi.
I want to edit the boot screen's text. I compile the kernel with fasm and compact it with kpack. I use winimage to place it in a flp file, then try to boot it with Oracle VM VirtualBox. It just says "Starting systemmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm" and keeps printing a bunch of m's.
When I put the kernel file on floppy disk and boot from it it says "Starting System........." and displays 136 dots.
What am i doing wrong? :oops:

~bigttcool

Re: Kernel Editing Problems

Posted: Sun Sep 12, 2010 9:10 pm
by ChE
Use kerpack to compress the kernel instead of kpack

Re: Kernel Editing Problems

Posted: Sun Sep 12, 2010 9:19 pm
by bigttcool2
I'm using windows to compile, not kolibri

Re: Kernel Editing Problems

Posted: Sun Sep 12, 2010 9:47 pm
by Mario
kpack only for applications and driver - it is not for kernel.mnt

Re: Kernel Editing Problems

Posted: Mon Sep 13, 2010 12:58 am
by bigttcool2
I see. Then how do I compile kernel.mnt on windows with kerpack? My console won't let me execute it (MS-DOS)

Re: Kernel Editing Problems

Posted: Mon Sep 13, 2010 8:59 am
by Mario
You can use kernel.mnt without packing. If you need more space in kolibri.img - just delete any games or demo files.

Re: Kernel Editing Problems

Posted: Mon Sep 13, 2010 12:13 pm
by art_zh
bigttcool2

another way is to compile the kernel inside KolibriOS.

1) load an official distro,
2) run a file manager. MSDOS-users may prefere KFAR - it looks like old-and-good Norton Commander
3) in KFAR press <Alt>-<F2> and choose the disk where your new kernel source files located (it has to be a FAT-disk to avoid file writing problems)
4) jump to the right panel (<Tab>) and enter the source directory (keep /rd/1 on your left panel)
5) load kernel.asm with tinypad text editor (starts by default when you choose an .asm-file),
6) in tinypad menu click Run, then Compile.
7) return to KFAR: a new file KERNEL should appear. Copy it to the left panel (<F5>) as /rd/1/kernel.mnt
8 ) on the left panel, run kerpack
9) run rdsave to store kolibri.img back to your disk.
10) reboot.

the whole procedure takes less than 2 minutes (what other OS has a faster modify-recompile-test routine for itself ?!)

Re: Kernel Editing Problems

Posted: Wed Sep 15, 2010 12:20 am
by bigttcool2
That makes sense, but I'm using virtual box that doesn't have access to writing the IMG file, or to anything except the ramdrive. Can I do the uncompressed version in the ISO file? It would go faster and would beable to grow. How would I edit the ISO file so that VirtualBox can read it. Any time I try, it fails. Is there something better than MagicISO?

Re: Kernel Editing Problems

Posted: Wed Sep 15, 2010 10:26 am
by SoUrcerer
As for me, I used trial version of WinImage. Now I use linux :)

Re: Kernel Editing Problems

Posted: Thu Sep 16, 2010 12:12 am
by bigttcool2
Linux has the native ability to read and write to ISO images?
I have Ubuntu 10.04 on another Virtual Box.

Re: Kernel Editing Problems

Posted: Thu Sep 16, 2010 4:00 am
by <Lrz>
Maybe this way will be usefull for you:
So you need some Windows, Kerpack, KlbrInWin.
1) Run config.exe in ../KlbrInWin/comfig.exe. See way for FDD (for example ../Kolibri/A).
2) Make a new kernel (run the ../trunk/build.bat), copy kernel.mnt in ../Kolibri/A( fdd's way).
3) Copy Kerpack in ../Kolibri/A( fdd's way).
4) Run Kerpack over KlbrInWin.
The end. Your kernel will be packed.

Re: Kernel Editing Problems

Posted: Fri Oct 08, 2010 12:00 am
by diamond
art_zh wrote:5) load kernel.asm with tinypad text editor (starts by default when you choose an .asm-file),
6) in tinypad menu click Run, then Compile.
7) return to KFAR: a new file KERNEL should appear. Copy it to the left panel (<F5>) as /rd/1/kernel.mnt
Why so complicated? KFar -> locate kernel.asm -> <Menu> button -> Compile instead of all these steps.
bigttcool2 wrote:Can I do the uncompressed version in the ISO file? It would go faster and would beable to grow. How would I edit the ISO file so that VirtualBox can read it. Any time I try, it fails. Is there something better than MagicISO?
No. The LiveCD ISO is not intended for editing.

Re: Kernel Editing Problems

Posted: Sun Nov 28, 2010 6:12 pm
by bigttcool2
Why can't I edit the LiveCD ISO?

A) Whats the difference?
B) Where's the source code?

I would like to use a CD because I can do more things and its more practical than to use a floppy drive. Right?

Re: Kernel Editing Problems

Posted: Sun Nov 28, 2010 7:16 pm
by dunkaist
Hi, bigttcool2!
bigttcool2 wrote:Why can't I edit the LiveCD ISO?

A) Whats the difference?
This is because KolibriOS boots from CD using floppy emulation. Such approach gives some advantages but the other side is (as you mentioned above) difficulties in editing. Do not despair! You really _can_ get *.iso image working (bootable). All you need is:
1). to edit floppy image (e.g. kolibri.img);
2). to place files you would like to have on CD in some folder;
3). make an *.iso image (using corresponding software) from this folder with kolibri.img as 'boot image' or something else depending on your software.
bigttcool2 wrote:B) Where's the source code?
You can get all the source code from KolibriOS svn repository (svn co svn://kolibrios.org) using subversion (if you are familiar, the latest snapshot) or just download this archive.
bigttcool2 wrote:I would like to use a CD because I can do more things and its more practical than to use a floppy drive. Right?
AFAIK, most KolibriOS developers use floppy images because they are convenient to work with. All depends on your target.

Re: Kernel Editing Problems

Posted: Fri Apr 29, 2011 4:27 pm
by anstein99
Well thanks, but what is 'official distro'?