I know everyone is just barely tolerating tdavis and his LoseThos ramblings, hoping that he will get bored and go away, but do I have some news for you! No, he won't leave through boredom. He'll keep on making his crackpot posts until you, me, and the Sussman have gone mad. He must be motivated to leave. He must chained behind the back of a pickup truck and dragged through the proverbial streets. His body needs to be dismembered, his remains torched with gasoline, and his ashes scattered into the dust of the Universe before he'll stop.
Name:
n3n7i2011-09-14 22:50
*getting a bit carried away... =) settle*
It is no-doubt a huge feat to build an OS,
I'm just finding the terms almost as impressive in how silly they are...
Name:
n3n7i2011-09-14 23:23
There must be a few proper 'Expert' programmers lurking around here once in a blue-moon...
Perhaps they could 'salvage' sethOS for anonix-OS...?
100,000 loc...... hmm maybe..? Build a code-reverse-engineering code first? =) huhwaht
Yeah,it would be difficult to do adware. I guess I'm stuck with site advertising. I thought I heard YouTube pays a penny a view. I got 74,000 views on my video. $740 in a year is not going to do me much good except hassle my tax filing.
Looks grim, quite honestly.
Everything points toward VMWare in the future and that really ruins everything. Makes OS just an app.
How about it anon? >> first to the reverse-engineering code =)
Build a program which first, identifies function declarations in a piece of code, secondly maps functions to their 'parent/caller function(s)?' and third outputs the overall structure in a readable fashion.... ?
I did an unassembler in addition to the compiler/assembler. Go have fun. It's 100% open source -- you sound confused. You want me to make hacking tools? It boots from a CD, can read/write hard drive blocks and has my unassembler. I don't want to gain notoriety--I'd rather you did harmless video games with it, but have fun. When I was a kid, I did that on my C64 -- that's how you learn. It's really nasty, today, for kids.
I have no respect for reverse engineers -- I had a job doing that once and viewed it as a humiliation. I'd rather be architect of a new OS.
It would be a non-harmful type hacking tool =)
...Operating on the (Open? / otherwise sourced..?) source-code rather than compiled / disassembling stuff...
Name:
n3n7i2011-09-15 0:25
=) heeheehee! ...
... I am a witty kid. heeheehee
... I smell like piss... =) heeheehee!
You are speaking of an uncompiler, I think they're called. that's in my realm of expertise, but not at all needed in LoseThos since it's 100% open source... and no code enters which hasn't been compiled by my compiler, in all likelyhood. You might entertain yourself by unassembling BIOSes, but my 16-bit unassembler quality is poor.
Why don't you try to be an engineer instead of reverse engineer? Go architect something.
10 i = i + 1
15 IF i > 99999 THEN PRINT ".";: i = 0
20 IF INKEY$ = "" THEN 10
30 PRINT "King James Bible, Line:", i
God says...
Line: 95035
righteousness which is in the law, blameless.
3:7 But what things were gain to me, those I counted loss for Christ.
3:8 Yea doubtless, and I count all things but loss for the excellency
of the knowledge of Christ Jesus my Lord: for whom I have suffered the
loss of all things, and do count them but dung, that I may win Christ,
3:9 And be found in him, not having mine own righteousness, which is
of the law, but that which is through the faith of Christ, the
righteousness which is of God by faith: 3:10 That I may know him, and
the power of his resurrection, and the fellowship of his sufferings,
being made conformable unto his death; 3:11 If by any means I might
attain unto the resurrection of the dead.
aul had
adjured the people, saying, Cursed be the man that eateth any food
until evening, that I may be avenged on mine enemies. So none of the
people tasted any food.
14:25 And all they of the land came to a wood; and there was honey
upon the ground.
14:26 And when the people were come into the wood, behold, the honey
dropped; but no man put his hand to his mouth: for the people feared
the oath.
14:27 But Jonathan heard not when his father charged the people with
the oath: wherefore he put
reverse-engineering might've been the wrong term...?
If you're given 100,000 lines of code, which you know very little about.... it's close enough to reverse engineering just to figure out what that code does.. is this illegal?
>>56
LoseThos is public domain -- no strings attached. The look-up feature brings you to source code where the header for functions might have some documentation. My thought was it's for programmers, so the code would explain many things. There is documentation and demo examples. There's a tour.
tdavis, please go to /g/. They all love your operating system and talk about it all the time. I am sure they would appreciate it if you made threads there.
Name:
Anonymous2011-09-16 8:16
terry, if LoseThos is opensource, why is half the source missing?
Why don't you release the source of your compiler?
Why don't you release the source as proper archive, zip or tar, as other people do?
Why do you insist that people could possibly give a fuck about your own archive implementation, when there are already perfectly fine archive implementations around, like zip and tar?
I wisely chose 640x480x4 because it's incredibly responsive. If you change the graphics resolution it will be a dog.
lol, tdavis is a complete idiot. How come any decent operating system can run 1080p and beyond without being 'a dog'? Enjoy your shit programming skills.
Name:
Anonymous2011-09-16 8:53
More shit from tdavis...
>1) LoseThos will always run everything in kernel mode, ring 0. All programs will have full access to memory, I/O ports, instructions, etc.
Enjoy your no security.
>2) LoseThos will always "identity map" virtual memory. (Virtual addresses are set equal to physical addresses with a single map for all tasks on all cores.) It's as though paging is not used.
That is very primitive.
>3) LoseThos will always be for one platform -- x86_64 PC compatibles.
Your non-portable OS is next to useless.
>4) LoseThos will never have networking.
Why not?
>5) LoseThos will always have one video mode, 640x480 by 16 colors, unless this mode becomes unavailable on computers in the future. See LoseThos Graphics.
And this is evidently only because you're incapable of writing a video driver that is decent at a higher resolution (see my last post).
>6) The LoseThos operating system will be free. I might sell applications, support, or, possibly, adware.
Adware is a bad thing.
>7) LoseThos will be 100% open source with all source included, unless device drivers or something can only be included with non-disclosure agreements.
Who cares? No one will want to use this shitty OS anyway.
>8) All function args and returns will be 64-bit. No plans for C++.
Why would you return a 64-bit value, if, for example, you know you're dealing with bytes in a certain situation? Forcing yourself to always deal in 64-bit quantities is utterly stupid.
>9) LoseThos documents are not for printing. They're dynamic and intended for the screen. There will always be just one font, a fixed-width font. No Unicode, just ASCII.
No Unicode? Why the fuck not?
>10) LoseThos is not for multimedia. Games will be created by programmers, not artists. Sounds and images will be, primarily, calculated in real-time, not fetched.
Who says you can tell us how we will use your OS? Of course, we won't, but nevertheless my point still stands.
>11) All functions, variables and class members will be accessible. There are no C++ public/private protections and all functions, even secondary ones in the kernel, can be called.
Enjoy your no security.
>12) Backward compatibility is NOT guaranteed. You are safest working with JIT compilation instead of AOT static binaries because I can add members to classes, reorder members in classes, add default args to existing functions, change #define values, etc. all without breaking compatibility.
Enjoy going against principles defined in computer science for the last two decades.
Name:
Anonymous2011-09-16 8:56
[fixed quotes]
More shit from tdavis...
1) LoseThos will always run everything in kernel mode, ring 0. All programs will have full access to memory, I/O ports, instructions, etc.
Enjoy your no security. 2) LoseThos will always "identity map" virtual memory. (Virtual addresses are set equal to physical addresses with a single map for all tasks on all cores.) It's as though paging is not used.
That is very primitive. 3) LoseThos will always be for one platform -- x86_64 PC compatibles.
Your non-portable OS is next to useless. 4) LoseThos will never have networking.
Why not? 5) LoseThos will always have one video mode, 640x480 by 16 colors, unless this mode becomes unavailable on computers in the future. See LoseThos Graphics.
And this is evidently only because you're incapable of writing a video driver that is decent at a higher resolution (see my last post). 6) The LoseThos operating system will be free. I might sell applications, support, or, possibly, adware.
Adware is a bad thing. 7) LoseThos will be 100% open source with all source included, unless device drivers or something can only be included with non-disclosure agreements.
Who cares? No one will want to use this shitty OS anyway. 8) All function args and returns will be 64-bit. No plans for C++.
Why would you return a 64-bit value, if, for example, you know you're dealing with bytes in a certain situation? Forcing yourself to always deal in 64-bit quantities is utterly stupid. 9) LoseThos documents are not for printing. They're dynamic and intended for the screen. There will always be just one font, a fixed-width font. No Unicode, just ASCII.
No Unicode? Why the fuck not? 10) LoseThos is not for multimedia. Games will be created by programmers, not artists. Sounds and images will be, primarily, calculated in real-time, not fetched.
Who says you can tell us how we will use your OS? Of course, we won't, but nevertheless my point still stands. 11) All functions, variables and class members will be accessible. There are no C++ public/private protections and all functions, even secondary ones in the kernel, can be called.
Enjoy your no security. 12) Backward compatibility is NOT guaranteed. You are safest working with JIT compilation instead of AOT static binaries because I can add members to classes, reorder members in classes, add default args to existing functions, change #define values, etc. all without breaking compatibility.
Enjoy going against principles defined in computer science for the last two decades.
Amateur OS developers don't actually bother to write applications like flight simulators. They just putz around, maybe run Doom at 320x200
Name:
Anonymous2011-09-16 9:16
>>76
Did you know that 640x480x4 is no true limitation; you only think you are limited to it because you are too poor of a programmer to support a higher resolution? Did you know that there is a standard called "VESA" that allows you to write an essentially universal video driver that will drive monitors at higher resolutions and bit depths?
Name:
FrozenVoid2011-09-16 9:25
Unlimited Detail point-cloud engine will make the GPUs obsolete. Keep on working on the OS, terry, The graphics can be always fixed later, the OS itself isn't something which should satisfy every whim of game industry it always a conceptual creation with graphics serving as filler. If the OS gives direct access to hardware(and losethos at cursory glance allow very low-level interrupt/memory access), another renderer can be written and since its opensource everyone should stop whining and code their "1080p real-time" graphic engine.