Expand on your bootloader
Re: Expand on your bootloader
This should really be wiki-fied.
It needs to be indexed properly as people searching for tutorials go to the wiki and not the forums.
I didn't fully review the tutorial, but it seems like some nice work.
It needs to be indexed properly as people searching for tutorials go to the wiki and not the forums.
I didn't fully review the tutorial, but it seems like some nice work.
Website: https://joscor.com
Re: Expand on your bootloader
not really... technically (i know, it doesnt really make much difference, but...) it is the BIOS that switches into RMode, not the CPU -- the CPU does start in 16bit mode, but its UMode, not RMode (unreal mode being a "mutation" between RMode and PMode) -- well i guess 88/86/286 do start in actual RMode, but 386 and beyond actually start up in UMode (which was not a 'bug later supported for compatibility' as many people claim, but rather an intentional side-affect of how PMode works, and actually used in the boot process), the BIOS then first switches to PMode to do most of its work, then returns to RMode before jumping to the bootsectorAs you know, the x86 processor boots into a 16 bit envirement. What is this mode? (Hint: Its not Real Mode) ... Okay, it is
What is so real abut real mode, anyway? Real Mode...
reference: 3A:9.1.4
Re: Expand on your bootloader
Hi,
Cheers,
Brendan
Technically, unreal mode is real mode with modified data segment limits, and the startup state for modern 80x86 CPUs is real mode with a modified code segment base (but the same 64 KiB limits for all segments) - they aren't quite the same...JAAman wrote:not really... technically (i know, it doesnt really make much difference, but...) it is the BIOS that switches into RMode, not the CPU -- the CPU does start in 16bit mode, but its UMode, not RMode (unreal mode being a "mutation" between RMode and PMode) -- well i guess 88/86/286 do start in actual RMode, but 386 and beyond actually start up in UMode (which was not a 'bug later supported for compatibility' as many people claim, but rather an intentional side-affect of how PMode works, and actually used in the boot process), the BIOS then first switches to PMode to do most of its work, then returns to RMode before jumping to the bootsectorAs you know, the x86 processor boots into a 16 bit envirement. What is this mode? (Hint: Its not Real Mode) ... Okay, it is
What is so real abut real mode, anyway? Real Mode...
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
Re: Expand on your bootloader
Im confused...This looks like a copy+paste from the text in one of my tutorials...
(In fact, both of your posts contain it. Please remember that it is copyrighted work. I am fine if some of the text is wikified though. I am unable to check your website atm)
(In fact, both of your posts contain it. Please remember that it is copyrighted work. I am fine if some of the text is wikified though. I am unable to check your website atm)
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
Re: Expand on your bootloader
Hi,
Cheers,
Brendan
You're right - it's a direct copy from this web page, complete with the same spelling mistakes ("envirement").neon wrote:Im confused...This looks like a copy+paste from the text in one of my tutorials...
Copyright law typically allows for a certain amount of the original work to be quoted and/or used for reference - see "Copyrights: fair use" in Wikipedia.neon wrote:(In fact, both of your posts contain it. Please remember that it is copyrighted work. I am fine if some of the text is wikified though. I am unable to check your website atm)
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
Re: Expand on your bootloader
Hi,
Just a quick update - the original poster cut & pasted "part II" (which I deleted), and the only reason I can think of for doing this (either accidentally or deliberately) is to get people to click on the link in the original poster's signature. I've banned the original poster (until they can explain their actions)....
Cheers,
Brendan
Just a quick update - the original poster cut & pasted "part II" (which I deleted), and the only reason I can think of for doing this (either accidentally or deliberately) is to get people to click on the link in the original poster's signature. I've banned the original poster (until they can explain their actions)....
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
Re: Expand on your bootloader
I am fine with thatBrendan wrote:Copyright law typically allows for a certain amount of the original work to be quoted and/or used for reference - see "Copyrights: fair use" in Wikipedia.
I actually kind of encourage it a little. I dont like anyone taking the series and claiming it as their own, however.I was informed that the entire series was copied+pasted to the site (here) which (from my understanding) breaks copyright law. I emailed the site owners requesting for the content to be removed within 24 hours.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
Re: Expand on your bootloader
Hi,
Cheers,
Brendan
IMHO, even "fair use" should be accompanied by "fair attribution"....neon wrote:I am fine with thatBrendan wrote:Copyright law typically allows for a certain amount of the original work to be quoted and/or used for reference - see "Copyrights: fair use" in Wikipedia.
Doh. That web site is the same website as the one in the original poster's signature. I wouldn't be surprised if "angeln123" is the person who's violated your copyright in both cases, which makes me wonder if "angeln123" has posted it anywhere else...neon wrote:I was informed that the entire series was copied+pasted to the site (here) which (from my understanding) breaks copyright law. I emailed the site owners requesting for the content to be removed within 24 hours.
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
Re: Expand on your bootloader
Hi,
That's a bit low! It's not just Neon's tutorials, there are loads of other tutorials (driver / embedded development...) that are suffixed with the same note. I just tried posting a nice comment to this effect, but unfortunately the captcha doesn't seem to work.
Good luck getting it removed, Neon.
Cheers,
Adam
angeln123's site wrote:（Author：angeln123）
That's a bit low! It's not just Neon's tutorials, there are loads of other tutorials (driver / embedded development...) that are suffixed with the same note. I just tried posting a nice comment to this effect, but unfortunately the captcha doesn't seem to work.Good luck getting it removed, Neon.
Cheers,
Adam
Re: Expand on your bootloader
Hm... Perhaps I should just contact his web hosting company do to him using his website for illegal activities (which breaks my sites Terms of Use, and I am sure many others...) as well as copyright law.AJ wrote:Hi,
angeln123's site wrote:（Author：angeln123）
ThanksAJ wrote:Good luck getting it removed, Neon.
Any suggestions on getting this guy's site taken down would be great 
*edit: Yey! Theres a link to the Wiki from the forums now.
Last edited by neon on Fri Apr 03, 2009 5:33 am, edited 1 time in total.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
Re: Expand on your bootloader
DDoS? [/joke] 
Re: Expand on your bootloader
It was with a hugely selfish sigh of relief that I read his site and noticed that he hadn't ripped off my tutorials too. To be honest, noone's going to read them on that site - he's *literally* copy-pasted - no formatting or anything. Ridiculous.neon wrote:AJ wrote: Thanks
*edit: Yey! Theres a link to the Wiki from the forums now.
And the forum template update was by me, due to popular demand.
-
Troy Martin
- Member
- Posts: 1686
- Joined: Fri Apr 18, 2008 4:40 pm
- Location: Langley, Vancouver, BC, Canada
- Contact:
Re: Expand on your bootloader
Fixed!AJ wrote:DDoS? [/nojoke]
I wish I could add more texSolar wrote:It keeps stunning me how friendly we - as a community - are towards people who start programming "their first OS" who don't even have a solid understanding of pointers, their compiler, or how a OS is structured.
Re: Expand on your bootloader
Okay...still no response from my two warnings to the OP sent through email to take down the content. I contacted the sites registrar to see if they can do anything to either have the illegal content removed, or site taken down do to illegal activity.
Lets hope it doesn't get further then this. I rather the site taken down as I am betting most of the content on the site, if not all, breaks copyright.
Thanks for the support
Lets hope it doesn't get further then this. I rather the site taken down as I am betting most of the content on the site, if not all, breaks copyright.
Thanks for the support
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}