Page 20 of 55
Re: When your OS goes crazy - Screenshots
Posted: Fri Jan 17, 2014 4:51 am
by VolTeK
Edit, i have made a mistake. I have found the returned Troy Martin on here, and he is not you.
However, do make an OS that at least has 20% your code.
Re: When your OS goes crazy - Screenshots
Posted: Fri Jan 17, 2014 9:37 am
by Bender
@VolTek Thanks for the insult!
PS. I feel insults aren't bad, they are just encouragements that are like a little bit extreme, like
"Copy-Pasters can't implement multitasking, sid123's OS will never have it" - Insult (giving the reader more inspiration)
"Hey! How about multitasking?" - Encouragement, Just a little polite version of the Insult
You'd better smarten up. That bull**** isn't tolerated here.
Yes I would. Experience has told me that when you're new the experienced ones will
have a problem when interacting with you, and I think that I have learnt from my mistakes, I myself accept the fact that I've asked too many dumb questions on this board, which could be easily answered by a bit of googling, until Combuster had no option rather than an insult, (see my last question) and thanks to him which made me get onto the right track, after all "We all learn from our painful mistakes", Combuster's insult made me feel that I had left something behind, something very
important, which I now call "knowledge", I spent a month and a half on my
assembly skills. I prefer calling my OS as a test bed for my assembly skills, rather that a real OS. And now your insult has inspired me to write a multitasking system.
I feel we're going OT, let's keep this thread to where it belongs.
Re: When your OS goes crazy - Screenshots
Posted: Fri Jan 17, 2014 11:15 am
by Vijfhoek
Me trying to implement a TerminalWriteString:
- 2014-01-17-185755_1440x900_scrot.png (7.34 KiB) Viewed 5954 times
Re: When your OS goes crazy - Screenshots
Posted: Sun Jan 19, 2014 5:43 pm
by PearOs
Color Blend equation gone wrong.
Re: When your OS goes crazy - Screenshots
Posted: Mon Jan 20, 2014 2:42 am
by Bender
@PearOS Great Dude! I have been following your project, sad to see the website removed. It's in C# right?
Re: When your OS goes crazy - Screenshots
Posted: Mon Jan 20, 2014 3:39 am
by PearOs
sid123 wrote:@PearOS Great Dude! I have been following your project, sad to see the website removed. It's in C# right?
Thank you! I removed it because Codeplex kinda has a slow SVN at times and its really buggy. I'm not quite sure if I will make PearOs5 (the current version of PearOs) open source yet. I have a lot to work on and finish, yes its still in C# but this time with my own Compiler and tools. I moved away from Cosmos a long time ago and started my own Kernel.
- Matt
Re: When your OS goes crazy - Screenshots
Posted: Sat Jan 25, 2014 7:34 am
by Bender
Things "CAN" get messed up sometimes you know.......
Btw My OS is in Real Mode and the size of this file was 349 KB! (Nah, I just used the DOS MZ Format........)
I was "trying" to display in BMP image (340 KB in size) with my OS.......
Of course I'm now in Protected Mode.
This also runs under DOS-Box, So yeah DOS-Compatibility, DOS Compatibility, Yeah, DOS!
Re: When your OS goes crazy - Screenshots
Posted: Sat Jan 25, 2014 5:25 pm
by Vijfhoek
Yet another f***-up, this time when writing terminal scrolling:
Re: When your OS goes crazy - Screenshots
Posted: Tue Jan 28, 2014 4:37 am
by no92
This is my OS going crazy with failed console scrolling:
Re: When your OS goes crazy - Screenshots
Posted: Tue Jan 28, 2014 5:45 pm
by sortie
I recently read the book Nineteen Eighty-Four. The good people at the English Socialist Party has really revolutionized core concepts such as truth. Inspiring stuff. This naturally makes my realize how ungoodthinkwise I've been coding until now. In particular, I haven't been using ministry-approved addition tables. But really, the core issue is that I have not been upsubing my boolean constants at runtime for ministry inquiry, in case the party officials have rectified the truth. Naturally, there's a considerable amount of work converting my existing code to a model where the truth is not known until it has been verified at runtime. Nonetheless, I have rectified the <stdbool.h> header with the following oldproglang compatibility:
Code: Select all
bool __minitrue_verify_truth(void);
#define true (__minitrue_verify_truth())
#define false (!__minitrue_verify_truth())
Code: Select all
bool __minitrue_verify_truth(void)
{
/* TODO: Connect to the ministry of truth and ask for the current value of true. */
time_t now;
time(&now);
return (now ^ rand()) % 100 == 50;
}
As expected, rectifying the truth caused trasitionwise issues. For instance, the kernel didn't boot and heap assertions went volatility explosive. Addressing these issues caused my system to boot up successwise. The latest feature is that the ministry of truth is now able to mandate the behaviour of the ls program at runtime:
I'm not entirely sure what the party policy did to my editor, but I don't doubt the comrades at Ingsoc surely had intended something goodthinkful to happen:
Re: When your OS goes crazy - Screenshots
Posted: Wed Jan 29, 2014 2:40 am
by qw
sortie
Re: When your OS goes crazy - Screenshots
Posted: Wed Jan 29, 2014 4:46 am
by Combuster
I recently read the book
Is there camera support in here?
Re: When your OS goes crazy - Screenshots
Posted: Wed Jan 29, 2014 7:18 am
by shikhin
The Party is satisfied.
Re: When your OS goes crazy - Screenshots
Posted: Fri Jan 31, 2014 2:17 am
by Bender
Trying to enter VGA ModeX,
Don't know if I really entered as the Text should read 'This is ModeX, Woo!'
This is probably the largest problem with undocumented stuff like Unreal Mode, ModeX, and other hacks, that you can't
expect reliable behaviour
Btw Thinking of throwing a party, shifted my development system to Ubuntu
(because MingW had huge problems while compiling OpenGL and SDL
programs, who cares anyway?) =_=
And please don't blame me for that huge whitespace around the image, I am a MS-Paint guy
, GIMP's quite complicated though
Re: When your OS goes crazy - Screenshots
Posted: Fri Jan 31, 2014 2:25 am
by Combuster
sid123 wrote:This is probably the largest problem with undocumented stuff like Unreal Mode, ModeX, and other hacks, that you can't expect reliable behaviour
Are you seriously going to pick up on RDOS' worst traits? Based on that screenshot I can tell you
exactly what you did wrong. I have not seen any VGA frontend that didn't do Mode X - including all emulators which get Mode X right all the time even though they do tend to have problems with all sorts of more elaborate hacks.
Same goes for unreal mode being perfectly predictable.