Printable View
Hey Guys
Though i would add something to the post. I amd trying to write an OS and so far have written a very basic bootloader and laid down the concepts behind my file system, memory managment and I/O allocation. Anyway what i was wondering is does anyone know where i can get a 64bit assembler and 64bit emulator that will run under windows as i want to develop a 64bit OS.
Peter
A 64-bit O.S.? Hmmm... You won't be able to run it on any Pentium chips... You'll need a chip made by SGI such as the R4000(The chip inside the N64). I believe that a SUN HyperSPARC is also a 64-bit CPU... You may possibly make your O.S. for the Macintosh G4 cube... But I think that's 128-bit... Oh well... good luck...
One last thing: a 64-bit emulator would be VERY SLOW. One for the N64(SGI R4000 - a SIMPLE 64-bit chip) needs a P3 @ 450MHz.
phew! I've been keeping up with this thread and I understand
nothing! I made a boostrap b4 but looks like its ant meets
elephant! You guyz are really good in ASM!
I bet u guyz could push down M$!
Anyway, I want to know how you guyz learn all this?
I keep on reading the tutorials but still not understand...
Au contraire(sp?)... I don't really know that much about assembler, I just know some of the syntax and some of the opcodes... But, I do know lots of things in C. My C++ teacher calls me the top in the class and some of the things I tell her in C++ she didn't even know was possible. Example:
struct xy{int x, int y}
struct xy myfunc(int x, int y)
{
struct xy temp;
xy.x = x, xy.y = y;
return xy;
}
She did not know that it is possible to return a structure from a function. I believe you can do this in ASM as well, but you have to say word x, word y(2 byte = one word). Long is double word... I think that some machines such as some MACs support quad words. Anyways, for CTOS, I got the some of the IDE interface ready. It should be able to identify the geometry of different drives and read and write to the drives. I can write to 4 different controller port for a total of 4 controllers or 8 IDE Hard disks. Today, I started looking up information on the FAT12/16/32 filesystems(FloppyDOS, HDDDOS, and HDDWINDOWs, respectively). I have already coded structures for holding the Boot Parameter Block, the FAT12/16 BPB at offset 36, the FAT32 BPB at offset 36, the FATInfo sector, and the 32byte Directory/file entries. These are just simple structures taken from a document taken from the OS heaven, http://www.nondot.org/sabre/os
All I have to do is load sectors using my hard disk routines and use the info from the BPB to access files by reading sectors at calculated offsets given by the FAT Info. It's not the most difficult thing to do, but it IS possible.
I looked into that. Up to 12 bytes, the return value will be in ecx:edx:eax
After that the compiler automatically creates a storage area in the calling function's stack and passes a pointer to this area.
I can only help people who have VB :(
VBTZH:
Learn C. It's a bit more difficult than VB (Actually it's more than a bit...), but you get pointers(direct memory access... Raw power and speed... <drool> ). Your programs will run faster(lots faster!), but they take longer to code... unless your a code guru like some people I know(I could POSSIBLY be a C Code guru). You can also hit the hardware directly and manipulate data quicker and easier.
Take it a bit further with assembler and then your programs run from 2 to 20 times faster than in C, and the executables are super small (A 'Hello world prog in C: 4KBytes. Hello world prog in ASM is about 100-150 BYTES). Some instructions are even faster! The big draw back of ASM is that it'll take a while for you to code, and you need lines upon lines just to display a bit of text... Basically, if you need tons of speed and need to do ultimate direct hardware access and are short on space(Bootsectors - big time! Short on space...), do it in ASM!
Hey Guys
To all the people who have started writing OS's im curious what ideas have you come up with for memory managment. Have you just stuck to the standard shove a program in where theres space or have you com up with better ways of dealing with it.
I had an idea for memory managment put i think it would require big processor overhead. I was thinking though processors are getting ridiculously powerful now so this may not be a problem anymore. What do you guys think?
Basically my idea is to have a program stored all over memory anywhere there is free space to put a bit of it. This would allow for 100% memory usage the problem is whenever the program jumps or gets to the end of one of teh blocks the processor would have to check to make sure and then redirect the jmp or tell teh program where its next line of code is. Do you reckon this is worth implementing or would it just be too slow.
Peter
I don't really think that that method would be too efficient. Even with fast processors that we have today, they will be greatly slowed down because most of a processor's actions deal with memory accessing, whether it be adding or whatever, you still need to access memory. Having bits and pieces of a program lying all around your whole memory space is almost as bad as the FAT filesystem. Sorry to destroy your idea like that, it seems good at first(Good waste management), but analyse it and you will see the great dissadvantage(Possibiliy that a program could get lost, and great speed loss). One more thing, if you actually decide to implement this idea, look into "Garbage Collecting" algorythms for memory management.
One last thing of advice and then onto a big lecture: Use alot of malloc(), realloc(), and free(). If you didn't make these, then do it! These are important. Use malloc in your MM to make space for the programs, and use realloc for re-organizing to make more space. These are dynamic memory management techniques and are very important.
Think of memory as a type of filesystem(Hard disks are non-volatile, slow[not any more], magnetic storage). The programs are your 'files' in this analogy. You have tables and descriptors to tell the processor where everything is. But what will be faster? A filesystem that spreads files all over and fragments the data(FAT12/16/32 will do this alot - run defragmentor), or a filesystem that stores everything linearly(in a straight line and together) and rearrages data to resize the data(Such as EXT2[:)][extended FS v2] and my new filesystem ALFS[Advanced Lookup FS])?
My OS, CTOS, stores everything together in clumps(Blocks?). The memory manager has sort of a table to save information about the allocated data(Where and how big it is). It is possible to move the whole linked list or move just a section of it where there is more space for realloc()ing.
Actually, my memory management code DOES need work, I REALLY need to work on this(The mem.c file is about 13KB of code. The rest of the CTOS kernel takes up like 3MB. The MM code definitely needs a facelift :D ). I have the great idea, but it's just NOT FUN to implement. Later, I plan to make virtual memory and stuff using file. But, I need to get the rest of the kernel AND the filesystems up and running first off ;)
BTW: I hate DJGPP(GCC)! I can't get rhide to show any errors that I have. It just says "There were some errors" and that's it! Can ANYONE help me out? I'm going to have to do a heck of alot of debugging :(... :D :rolleyes:
Yeah i here what your syaing but surely because memory isn't a rotational medium having the program all over memory shouldn't make a difference to access speed as it just has to address the next space and not rotate round to then read it off.
As for DJGPP doesn't it output the errors to a file i migth be wrong but i think it does.
Peter
Yeah... But it is slower. The processor needs to compute the next part of the program given the packet/block information that you have in your descriptor for the program. This could mean an extra memory read cycle and add / subtract cycle for EACH access. usually memory can be accessed once a clock cycle. The jumping CAN double the time needed to access SOME piece of program in memory(Moving to different packets that are computed).
One more thing: I didn't know that you even could rip up programs and put the parts into memory in totally different places. Oh well... maybe windows does it (that COULD explain some of the crashes[losing address locations and such])
Your method does sound like it could be a neat experimental thing. Code it up and see it. Make a timer for normal mem accesses, and a timer for your method. Move around huge quantities of memory then stop the timer(do for each method). If the time isn't vastly different, then try it for your OS :)
Thats a very good point i completly forgot that the adress of the next bit would be stored in memory so would have to be accessed.
I might still code it up though it would be interesting to experiment and see what its like.
Peter
Well, I've made a bootstrap.
Now I am starting the kernel from scratch.
I wanna start with file management.
How am I to create and access FAT32?
Then later on I'll just have to pass the ASCIIZ and the mode I am
opening it,ie text,binary,random...
Or any advice is also welcomed.
FAT32... I need help with that as well... I sort of get some of it, but I don't exactly get how it all fits together. I think I'll review my documentation again. Go to...
http://nondot.org/sabre/os/filesystems
...and click on anything that deals with FAT12/16/32. When you make your code, don't just right away open the drive as a FAT, as you might get errors. First, open the partition table on the drive to see if it actually is a FAT drive. Here: code from...
CTOS/drivers/block/ide.c
I condensed some of that code so that it's not too ugly(removed some comments). The code above basically checks all the IDE hard disks and asks them for their first sector(boot block) for the FS IDs. When making your boot block, be sure to include the FAT identifier table. I'll show you people the CTOS boot block as an attachment :)Quote:
void ata_partProbe(void)
{
struct partition part_entry;
unsigned char buffer[512], drive, part;
unsigned char lheads, heads, sects, Temp3;
unsigned int Temp, track, Temp2;
unsigned short offset, cyls;
unsigned char* cp;
unsigned int i;
unsigned char str[255];
unsigned int d_cyl, d_head, d_sec;
printk("IDE Disk Partition probe: ( )) <--- \n");
for(drive=0; drive < MAX_INTERFACES; drive++)
{
if (ide_interfaces[drive].detect == 0) continue;
if (ide_interfaces[drive].flags & ATA_FLG_ATAPI) continue;
/* load sector 0 (the partition table) - 1 block, 1 count - 512 Bytes */
Temp = ata_read(drive, 1, 1, Buffer);
if (Temp < 0) continue;
if (buffer[0x1FE] != 0x55 || buffer[0x1FF] != 0xAA)
{
error("Invalid parition table on IDE Hard Disk device %d! Recommend you format it",drive);
continue;
}
lheads = ide_interfaces[drive].max_head;
for (part=0; part < MAX_INTERFACES; part++)
{
offset = 0x1BE + 16 * part;
Temp=*(unsigned int *)(Buffer + Offset + 8);
if (Temp == 0) continue;
sects = Temp % ide_interfaces[drive].max_sec + 1;
track = Temp / ide_interfaces[drive].max_sec;
heads = track % lheads;
cyls = track / lheads;
Temp2=*(unsigned int *)(buffer + offset + 12);
Temp3=*(unsigned char *)(buffer + offset + 4);
switch (Temp3)
{
case 0x01: sprintf(str,"FAT12"); break;
case 0x04: sprintf(str,"FAT16"); break;
case 0x05: sprintf(str,"Extended"); break;
case 0x06: sprintf(str,"FAT16 >32MB"); break;
case 0x07: sprintf(str,"HPFS"); break;
case 0x0B: sprintf(str,"FAT32"); break;
case 0x0C: sprintf(str,"FAT32"); break;
case 0x0E: sprintf(str,"FAT16"); break;
}
printk("HDD%d%c: start LBA=%d, start CHS=%d:%d:%d, Size: %dMB %s", drive, 'a' + part, Temp, Cyls, Heads, Sects, Temp2 * 512/1024/1024, str);
drive_para [drive * 4 + 4 + part].start_block = Temp;
sprintf(str,"HDD%d%c",drive,'a' + part);
}
}
}
Have fun! (It's actually a "Stapled together" mess of boot blocks, but just take the table at the top of the file and use that.
I'd like to use OUT...:)
I see your C code...
Shouldn't the first sector be the boot sector?
Why it is the partition table?
I thought it's after boot sector...
The code reads block 1 (CHS = 0/0/0). This block the first sector and it contains the boot sector(AKA boot block). The drive's partition table is INSIDE the boot block's code.
Yes, I see what you mean.
I am not quite familiar with C codes, because I seldom use them,
though I know C fairly well.
Sometimes I feel C is more difficult than ASM. :)
I am no way good in FAT.
So, my naive thought is:I want to write couples functions that
will receive an ASCIIZ string and do all the hard stuffs.
Compatible with MS-DOS.
Uh,never mind. I'll check out www.freedos.org
New update for my OS. I have 8MBytes of stuff in total, 2.4MBytes are pure code for the OS - 2 years of data by just me(I haven't really worked too much on it the first 6 months and these last 6 months).
I have designed the GUI, but have not coded it(It's all on paper, in my head, and in bitmaps on my computer). This is going to be one big chore. Here comes another 150,000 lines of C code(The GUI) to double the size of my OS.
Check out these pictures I created (I already made algorythms to draw the alternating patterns on the windows - get a closer look). I like my ideas, WinXP looks like M$ collided with Fisher Price or something.
This is what CTOS will look like in possibly 2 or 3 years:
Hi,
Interesting reading on this thread. I have a couple of big picture questions that are not so clear to me.
I understand the CPU calls an address that points to BIOS. BIOS does it stuff and then searches for Boot Record....
Now, when you folks develop a bootstrap, are you talking about programming the BIOS...or programming a bootable sector, MBR, etc. so that the CPU has someplace to go after BIOS program?
Do you test your OS on the PC you use to develop it?
I imagine you do something like this...using Windows/DOS, editor, compiler, you build operating system software and compile it....then you place it somewhere...boot disk? Then you do a warm boot and then test it. Is that right?
Please, I need to be clear on the basic process you folks follow. I understand software and hardware pretty well but I have not done this OS thing before.
Regards,
ChuckB
The first thing you generally do is program you Bootsector, this is the first sector on a disk. This is loaded at 0x07C0 in memory by the bios after it preforms its POST checks. It is the resposibility of the Bootsector to call the second stage of the bootloader or go ahead and load the full OS. It is quite possible to test your OS on your development PC but you really should get an old 486 or something to test it on. All you do (atleast untill you got a bootloader on a harddisk) is write the bootsector to a floppy disk using debug (the dos program) then copy the other files to disk (atleast if you are using a FAT filesystem).
GuitarMan,
Your bootsector explanation makes sense to me.
Writing an OS has always been one of those mystical things to me. I have done a lot of relearning of assembler and reading various tutorials and now it doesn't seem all too incredible. Sigh! However, I have never done this. I am a pretty decent programmer in VB and C but somehow feel inadequate until I write an OS. :-)
Now, I understand that when BIOS read the bootsector and runs the bootloader, it loads IO.SYS which contains all sorts of hardware functions (interrupts)...then MSDOS.SYS for higher functions...CONFIG.SYS, COMMAND.COM and then AUTOEXEC.BAT. Does that sound right?
My goal would be to write a very simple OS that boots up off of a floppy disk and then displays a command prompt that allows me to type in anything...and all it does is echo what I have typed. Nothing more. Is that too complex?
To implement I would write a bootloader in the boot sector (I think that is where the loader is located). I can then write another program to monitor the keyboard and print to monitor. I could do this with BIOS interrupts and no DOS interrupts. Would this then qualify as an OS?
Is an MSDOS formatted floppy disk sufficient or do I have to define my own format level? If this is okay then I guess I need to be able to read the FAT from the bootloader to pull up the second program I mention above. Is that correct?
Does a bootloader only qualify as an OS?
Sorry for the simple questions but I am trying to put together the big flick in my mind.
Thanks. ChuckB
Goto Planet-Source-Code and search in C\C++. I've found some things, all of them have a bootstrap made in ASM and they use partcopy to put it in the first sector of a floppy.
Or, you could use this piece of code from my OS. It is a FAT12 boot sector that loads KERNEL.BIN from the floppy. It will search for the file until it finds it. If there is no kernel, it will tell you, then hang the system. I have included a simple kernel that displays a message and hangs.
ChuckB, you can use this minimal OS as a backbone for starting your OS. You don't need to change the boot file. To start off, download this file, then NASM. Extract the files from this zip some where. Format a floppy, then go into DOS prompt(in the folder) and type in "partcopy boot 0 200 -f0" to copy the boot file onto the floppy's boot sector. The partcopy numbers are all in hex. Edit kernel.asm and add what you need to so get input and then display it. Put it in a loop, then go to DOS and type "nasm kernel.asm". Rename kernel to kernel.bin, then copy the file to the root directory of the floppy. Shut off your PC, then turn it on with the floppy in the drive. Your OS should load(Whatever is in kernel.bin). Put out the disk when you are done and restart to get your windows back.
I already asked this but got no response.
Warmaster, in your Kernel.asm file, it prints a message. I first moves the segment of your "startmessage" string to ax and then it moves it to ds (data segment). Here is how you're doing:
Why can you do something like this (for NASM):PHP Code:mov ax, 0x1000
mov ds, ax
I already tried this sort of coding but NASM gives me an error on the line containing "seg". This works fine in TASM when I use "segment" instead of "seg".PHP Code:mov ax, seg startmessage
mov ds, ax
I understand now what you're trying to say. There is an error in that because I had a start-up file that was supposed to be loaded and run inable to enable more than the 1MByte limit for the CTOS kernel to be loaded. The number should be 0x0050, not 0x1000. These are basically initializers to set the program's active segment. That are not needed for this particular KERNEL.ASM, but it is a good idea to have them for expansion. As soon as you declare a variable, the CPU will look in the previous segment. Therefore, you need to set an "active segment" (0x0050). The code to CALL the textprinter is just this:
mov si, message
call PrintStartup
Just make sure you have a string called message with a 0(NULL) as the last char(Be sure to have "PrintStartup" as well).
I hope that I have cleared this up :)
Ok thanks, but how would you display another string? For example, if you declare another string called message2, how would you print it using its segment and offset?
I did not see the code, but however I think you should do
mov si,message
call PrintStartup
mov si,message2
call PrintStartup
This is how it worked in my very basic OS, in ASM, but however its now in C.
is that code available here,or something like that
im asking this becouse u are talking about some function ,and i dont know how everybody know names of your func,or maybe it is available just for specified person :D
and thaks ABDUL ,ive learnt somthing useful things from your program HIDEWINDOW .im useing it right now :D
:D :D :D :D :D :o :o :o :o :o
You would say:Quote:
Originally posted by abdul
Ok thanks, but how would you display another string? For example, if you declare another string called message2, how would you print it using its segment and offset?
mov si, message2
call PrintStartup
...to print message2. Remember to have a NULL(0) at the end of each string or this will hang your PC.
mmiill, the code is available at my post on the top of this page.
You're copying what I said :eek: Naughty boy! ;)
Thanks, I understand it now. I see you're using a different interrupt instead of 21h and function 9h. I was trying to use 9h before which requires the the address of the string to be placed at DS:DX. I tried so using nasm but it said that binary format doesn't support this type of segment reference. Also when I try to include an external .inc file and then compile it to a binary file, it gives me an error saying that binary format doesn't support reference to an external file.
Weird because TASM lets me do all this pretty easily.
Geez... It took about 7 minutes just to load this "Reply to topic" page. NEVER EVER get Bell Sympatico High speed DSL. They say it's fast all the time? What a load of BS...
Anyways...
Dan, I didn't realize that you had already posted. I should check everything first before posting an answer.
I am designing my start-up module, known as STARTUP.BIN - It's the file the boot sector loads. STARTUP.BIN will be able to:
- Read FAT12/16/32
- Set the display to 640x480x256 color VESA
- Set the A20 address line(enable more than 1MByte of RAM)
- Load a startup bitmap and CPU logo bitmaps (according to detected CPU)
- Load KERNEL.BIN and a pmode disk driver for IDE or SCSI
- Initialize the GLD, IDT, LDT, and 32-bit Protected Mode
- Jump to the kernel
This whole file should be completely assembler. Total file size should need less than 1 segment (64KBytes). The bitmaps are separate files. This is VERY do-able. It should be done in a few months(with just me coding it). The FAT code is done, except for opening files and directories(The FAT manip. fncs. are ready), and read_sectors(d,s,*b); The FAT code is all in C, but my compiler can generate ASM code from the C code (BorlandC v3.1)
Read_sectors(); is giving me one big hassel. I have tried last night and all of today to get my computer to read the first sector into the correct buffer address. This is necessary for the FAT code to work. The buffer is always off by about 100-300 bytes and I have no idea why. I am embedding ASM code in my C code, and I think I am not passing the buffer's address correctly. I am using Int13h to read, but maybe I should use Int25h instead. This stupid/simple read_sectors(); is really annoying me. This should be very simple - someone tell me how to do it!!! :mad: :confused: :rolleyes: I will try using Int 25h. Tomarrow (thursday) is my last day on here for a while - gone for 3 days without a PC. I got to get me a laptop PC
Abdul, the reason I did not use Int 21h is because it's only supported by DOS. DOS installs that handler. Since we are making our own O.S.'es, we can't use that interrupt. Us people that are using Protected mode, We cannot call the BIOS while in Protected Mode (NO INTERRUPTS) except it we switch to V86 mode or back to real mode. Therefore, all loading of filesystem and disk drivers should be done BEFORE we enter protected mode or else we are stuck, lol (I found this out 2 days ago :p )
I read some tutorials, and I knew :D He, with its very much better OS than mine, didn't even know LOL!
warmaster, you could post the function here and so we can look for errors - I don't know much about OSs, but quite a lot about ASM and C, and cooperation of the two.
I found that I can't use Int 25h because it's a DOS routine.
OK, here is the code. It's been brutally beaten and massacred, so I don't know if it's even a good start. It is possible that the error was just my BIOS on my old computer, but don't they ALL support Int 13h?
mega-tokyo.com/forum
I found numerous FAT guides...
however, no way 4 me 2 understand it...
Pls anyone post codes on FAT, the foundation of FAT and creating
files and folders as well as managing them...
Compatible with MS-DOS...
Pls I need 2 know how...anyone?
BY FAR the best document for describing FAT12/16/32 has to be this one. It tells you how to access each cluster based on the FAT table in the beginning of the drive, how to calculate the position of the table based on the boot sector, what the boot sector for a FAT system should look like... It's an amazing resource. I have used it for making my ALMOST complete FAT driver. All that's needed is a function to open/close files and directories. I could get that finished very soon.
Now, does anyone have a fix for my readsector problem? Or will I have to just go for assembler?
No apparent errors, I'll read about INT 13h tomorrow.
Just one thing: it says you should reset floppies between read attempts.
Have you tried reading out ah on return?
Hey parskie,
I do not know what skill levels are required to do something like what you guys have talked about throughout this discussion, but i am well familiar with c,c++. Do not have any clue about ASM.
Can you guide me a little bit. Where should i start for learning ASM?
Hey TechySpecy 0xLv6Tfl/AWwL+ZFnFx9IV0O81SaXnOT2ckdHfpsJ9
XVkarZ2BC4hMdXQqFwvlhxn8S9cVXUCFGfxpQdTdRUbaCFeE9oc4f+El4OgZ19TFvfVAcc72arOh
xYeTKX9WCXe+yHgbGHD8V5qj3fmuUmzCpH7Oz52rcrX22sQ8O5VLjYUgT7wCrsaZeoik4yPoBXo0
zmhZ/CGiXaoF/fTTOcpdCWO9xzCjZxryIsEAykzuszAVWgFtoMe456KgVN6i3mDJ0rGOT+TC9fDX
GUl3lG69QRKhxlF4fXGUkE3q7T4ppIz0490a/n9JQlKtz6ap8EjGd8ByoOBpZ09Rl43f5JO/bsYA
GrDhohBx5D4QStqdn14mvfvqsfYrdhdn7pXhJcKIOLkWIkWbxoTJ5ioAaG/3wSsmHBn7XbELFiev
nXUwj+b33DNP5mCoyB1AoKp+QVoECaURSTpmiNzCw+N2lwYiHy+gQTXTC9vLwwSOp4Wv9LoKbU3U
PYwmbmxzZFVWZ4JnCp6cSF2toRE/EQPmU8KVmldlWfsGBuudYgaa/pjg5ah+NzNKXRVwBVbShNMl
phCF8iLHbpQepSbtUIcnkNMNwWk86UzM/iI5yV+vO8ISZuok4vmw93y+CMsGzEhPtbNIOWPqNLAd
nvN8/kDyFx7gzjOG4XXNoP2hA2MX6TPbuGIptSqBKHL8RzwkaRRVhsmPUR2LUhzmYdiVu5+5sRR5
RFllTE7fS4S3GrHsuGuYJ/LUBb1aKzXxCrC9HKfX1reBmaVcqWoQVm+4Kr+1vevbOQ/0
I need to learn ASM.
What is the best way?
PC Assembly Programming does teach you Assembly language so follow the link that pskyboy posted or you can also read the book Art Of Assembly (very long...about 1500 pages). The good thing about PC Assembly Programming is that it also teaches you 32-bit programming (using 32-bit registers) and also puts in some C and tells you how to use Assembly in C and vise-versa.
Please note; art of assembly is for MASM
There is a MASM version of AOA, but there also is a 16-bit version which doesn't use MASM.
BTW what happened to pskyboy's post?
Maybe an attack of madness :rolleyes:Quote:
Originally posted by CornedBee
There is a MASM version of AOA, but there also is a 16-bit version which doesn't use MASM.
BTW what happened to pskyboy's post?
...And now, here is my GUI(Window Manager) after working on it 7 days in school for an average of 30minutes a day during my programming class that I teach Grade 10's(I'm a peer tutor - I don't actually teach)
Currently, It (The Window Manager) can:
- Draw windows that have a border (that's it)
- Support up to 64 windows being active and up
- Support moving of windows
- Support switching of a window's z-order.
To use it, move the arrow key to move a little white dot(cursor). When over a window, press space to bring it to focus, then press space again to select it for moving. To release the window in the spot you want it, press space again. Press escape several times to quit... It does need to use double buffering to make it not flicker...
It is NOT complete, but this eventually WILL turn into my operating system's GUI! I am sorry, but I will NOT release source code :(
Updates to come when I get titlebars and window control boxes working(x, min, max)... and resizing...
(I just had to show you guys this)
The space doesnt work, I cant move the window...
Wheeeeeeeeeeeeeeee.
Works only for the three windows in the top right corner. The others don't react. (Don't even exist, they disappear once you bring any other window to the front).
Aaaah now it works, but it damned flickering..im getting mad of it..
I know... Those were the drawing routines drawing stuff... The bland, dark grey square is actually clipped. By the routine's definition, it should have taken up half the screen, BUT: I gave it a rect to clip to... It only draws in that rect... I only use 2 actual CLib functions: Getch(), and Int86(); All the rest(About 20-30) are created by me. The other shapes clear as soon as you select one of the 3 windows for moving. What I do right now(inefficient like crazy) is clear the screen and then call drawgui() which redraws all windows (and later, calls all functions that are in a window's struct [controls :)])Quote:
Originally posted by CornedBee
Wheeeeeeeeeeeeeeee.
Works only for the three windows in the top right corner. The others don't react. (Don't even exist, they disappear once you bring any other window to the front).
I said that the WM supports 64 windows, but right now, I only created 3 windows. createwin(x,y,w,h,txt,type); is what I made the function (similar to windows - familiar to some). Createwin looks through all 64 windows and finds one which does not have the WMFLAGS_ACTIVE bit in window[handle].flags set. Once you understand how I did this, it's really quite amazing. That is only 500 lines of code... and it condenses to 8KBytes using PowerC compiler.
Email me if you want PowerC - fits on a floppy and runs off DOS in a command line...
The flickering WILL go away... when I optimize the code and get a double buffer added (which for some reason doesn't work :mad: )