TBOS 0.5.1 released!

[Troy Martin]

When I saw "deflater" I was thinking it was either that guy making fun of you or it was the real you Then I noticed the correct spelling and grammar.
Wow, they actually banned you, surprising. I didn't even get a PM from a mod or anything. Something tells me this is all being discussed in the super secret mod forum...

Thanks for testing, do you mind telling me what you tested on and any strange things that happened (if any)?

[piranha]

Something tells me this is all being discussed in the super secret mod forum...

Shh!! They'll hear you!!

On topic: I tested it. Looks good. I like the man command.
One thing, the gray small text is hard to read if I'm not wearing my contact lenses. Maybe an option?

-JL

[deflater]

When I saw "deflater" I was thinking it was either that guy making fun of you or it was the real you Then I noticed the correct spelling and grammar.
Wow, they actually banned you, surprising. I didn't even get a PM from a mod or anything. Something tells me this is all being discussed in the super secret mod forum...

Heya, yup, they banned me for almost one month. Why? Well, "making bad situation worse". But I'm no toy to be called rude, so that's why they banned my account, the poor fella got mad about me calling him an *******. Isn't he? What I did wrong for crying out loud?
Anyways I'm glad you found out, I'm the real inflater .

About that super secret mod forum you've got that right. 10:00 CET in the morning and his thread was moved into that forum, but the site index said so it was in General ramblings until somebody posted in that section. (It looked the same like if a spambot would post it - but you were redirected to "You are not authorized to read this forum" instead of the original post). It was not accessible to non-mods though. The mod forum is located at http://forum.osdev.org/viewforum.php?f=14 btw.

Ow, that was grossly offtopic eh. Anyways to get back on the topic, I tested the OS on my testbed (http://inflater.wz.cz/site/pc/zelezo.htm the second picture and the text PARAMETRE testbedu.. and it's the PC with the black case ) and also Bochs, and everything worked fine.

Regards
inflater, undercover.

[Troy Martin]

Something tells me this is all being discussed in the super secret mod forum...

Shh!! They'll hear you!!

LOL! They have cameras everywhere...

On topic: I tested it. Looks good. I like the man command.
One thing, the gray small text is hard to read if I'm not wearing my contact lenses. Maybe an option?

-JL

I'll make the text default to the small 80x50 but I'll add a "mode" command in 0.3.1. Thanks for the input!

@inflater: Good luck trying to become a mod now
I might have a shot at it soon, I'm here 50% of the day on weekends and at least seven hours on weekdays, so I could catch these things quickly

EDIT: 0.3.1 released with piranha's video mode setup idea implemented as the "mode" command.

[JackScott]

Tested working fine on Virtual PC 2007.

The only gripe I could come up with is the non-implementation of the tab-completion feature common in other shells (Bash for example). Instead, it printed a lower-case circle (I checked, not the letter o), which I found a bit confusing at first. Indeed, I thought it must have been designed for a foreign keymap.

Apart from that, nothing else to report. Good work, and I can't wait to see more!

Edit: Tested the mode change feature, worked flawlessly for me. Haven't tested on a real machine yet though.

[Troy Martin]

Thanks, JackScott. I test all my stuff on Virtual PC as well.

I guess it wouldn't be too hard to implement a completion feature in the next version. Thanks for the input! It's designed for a standard North American QWERTY keyboard.

[jzgriffin]

I tested your OS in QEMU 0.9.1. It works.

Might I suggest, however, that you move the shell and other commands into their own files, and include them in the main file? Your k_main.asm files is growing rather quickly and will soon become difficult to manage.

[Troy Martin]

I tested your OS in QEMU 0.9.1. It works.

Might I suggest, however, that you move the shell and other commands into their own files, and include them in the main file? Your k_main.asm files is growing rather quickly and will soon become difficult to manage.

I was thinking that around the time I implemented man and strncmp. I'll do that for 0.3.2.

[Troy Martin]

Sorry for the double (almost triple) post, but I've released 0.4.0 early with all the planned features! Check out the website to get it, and read changes.txt** to find out everything that's been added!

**changes.txt has 0.4.0 and a bunch of 0.4.0N sections in it, all of the features combined are in 0.4.0.

[KKOverdose]

Hello

Code: Select all

	mov di,kern_filename
	mov al,'T'
	stosb
	mov al,'B'
	stosb
	mov al,'O'
	stosb
	mov al,'S'
	stosb
	mov al,'K'
	stosb
	mov al,'R'
	stosb
	mov al,'N'
	stosb
	mov al,'L'
	stosb
	mov al,'S'
	stosb
	mov al,'Y'
	stosb
	mov al,'S'
	stosb		; Kernel name is "TBOSKRNLSYS"

ouch, someone needs an assembly school methinks rep movsb is your friend, will turn that into like 4 lines

also you say its 186, nasm may allow that because the instructions are 186, however you use 32-bit (eax) and 386 regs (gs, fs) in your OS so it may crash on a real 186!

For CLI would be better to have a string parser to get options, this is a bit of a kludge....

Code: Select all

cmd_man db "man",0
cmd_man_ops db "man ",0
cmd_man_man db "man man",0
cmd_man_hash db "man hash",0
cmd_man_uname db "man uname",0
cmd_man_mode db "man mode",0

also what does this mean at the bottom of tbosload.asm?

Code: Select all

buffer:		; Disk buffer begins (8k after this, stack starts)

- KK

[Troy Martin]

you use 32-bit (eax) and 386 regs (gs, fs) in your OS so it may crash on a real 186!

Uhm, IIRC, nasm wouldn't compile anything for 186 that uses 386 features. I searched all my code, didn't see any eax used.

fs and gs are 386? Thought they were 8086...

For CLI would be better to have a string parser to get options, this is a bit of a kludge....

It works fine, unless it needs to be changed for technical reasons, I'll keep it that way for now.

also what does this mean at the bottom of tbosload.asm?

Uh, I didn't write the FAT code, but I'd assume from the comments that it's some temporary location for loading sectors to.

[KKOverdose]

Hello

Uhm, IIRC, nasm wouldn't compile anything for 186 that uses 386 features.

No nasm will make sure that you are using 186 instructions but it doesn't check registers

fs and gs are 386? Thought they were 8086...

then you thought wrong fs and gs = extra segment registers added for the 386, google is your friend! not sure how those operands would translate on a real 186 but it could lead to problems

Uh, I didn't write the FAT code, but I'd assume from the comments that it's some temporary location for loading sectors to.

No I mean the stack bit, it says the stack starts 8k after that but it cant, where is the stack located?

- KK

[Troy Martin]

No nasm will make sure that you are using 186 instructions but it doesn't check registers

Oopsies, fixed!

fs and gs = extra segment registers added for the 386, google is your friend! not sure how those operands would translate on a real 186 but it could lead to problems

Probably was moving 0x2000 into crap memory or something.

I mean the stack bit, it says the stack starts 8k after that but it cant, where is the stack located?

I don't exactly know, but it still works in my kernel so I'm happy enough!

Thanks for reading the code! Didn't find any use of eax though..

[KKOverdose]

I mean the stack bit, it says the stack starts 8k after that but it cant, where is the stack located?

I don't exactly know, but it still works in my kernel so I'm happy enough!

hehe OK, well as they say, if it works it works but not knowing where it is could come back to bite you if it starts overwriting data (or your code starts overwriting the stack). ouch!

- KK

[Troy Martin]

I think my kernel (at 2000h:0000) uses the bootloader stack still, so I don't really have much in the way of fear of overwriting stuff. Yet.

And the experimental FAT reading code is odd, can't seem to load at or past the 8000h offset mark.. Dammit, Mike, where are you!?