0 Members and 2 Guests are viewing this topic.
Ok this might just be me but I just rabbed the .rom file from the provided link and dragged 'n dropped it unto wabbitemu. It then says boot succesfull but if I press any key the screen goes blank. I suppose this is not what should be happening? 3 dedicated buffers made my day though lol
I'd like to put up a request for 5 Graph buffers -- two main, two for copying to the main ones for quick static rendering, and an extra one
Hey, nice to see you post about this. I'm looking forward to seeing this develop. =)
good luck on the file system, eeems!
/ ; root directory boot/ ; where all the bootup files are stored boot.bin ; binary to run on bootup boot.txt ; welcome message to display at bootup etc/ ; All the settings will be stored here hostname.txt ; Hostname of the system ("Rogue"). It's a placeholder for now.
eeems@Chloe ~/workspace/rogueos $ make allCreating Include File Boot Sleep DispHexA Shift Newline DrawString MeasureString PutChar LCDRight LCDLeft LCDUp LCDDown ClearBuffer PutSpriteXOR PutSpriteOR LCDDelay LCDReady RequestLock GetKey FlushKeys WaitKey LoadReturnText FreeMem AllocateMem LoadExecutableToRAM LoadFileToRAM ExecFile NewThread KernelPanicCompiling filesystem boot/ boot.bin.asm -> Compiling boot.bin.asm Pass one... Pass two... Program Start: 0 Size: Program End: 36 Done <- Done Compiling boot.bin.asm boot.txt etc/ hostname.txtCompiling pages Pass one... Pass two... Compiling Page00 Free Space: 13328 bytes Compiling Page 01 Start of FAT: 16384 Entry root/: 16386 Entry boot/: 16396 Entry boot.bin.asm: 16406 Entry boot.txt: 16423 Entry etc/: 16440 Entry hostname.txt: 16449 End of FAT 16470 boot.bin.asm Start 16471 Length boot.txt Start 16509 Length hostname.txt Start 16549 Length Free Space: 16210 bytes DoneCreating 8xu Building OS data... Hashing OS data... Key file 0A.key specified, reading contents... Building 8XU... Writing validation data... Done.Creating Rom Knight Kernel HexToRom ToolFinished
you're computer's name is "chloe"? lolGlad to see it builds well with the filesystem.
ah, ok thanks.do you think there's any way this could have been what was causing the garbled text issue, eeems? it certainly seemed liked an interrupt issue. i can't svn checkout the new code to test, though, because my father has blocked google.code again.
Looks pretty cool!