I have followed a tutorial and it does not work: Difference between revisions
| [unchecked revision] | [unchecked revision] |
Glauxosdever (talk | contribs) |
(Rewrite, more info.) |
||
| Line 1: | Line 1: | ||
There are multiple reasons that an operating system based on a tutorial may not work. |
|||
There are many tutorials related to OS development out there. While there exist a few that are good in quality, we only get to see the poor ones. In fact it always boils down to these problems: |
|||
== You forgot a step == |
|||
* The author wasn't aware of best practices, or worse, willfully ignored it, which also happens. |
|||
This is most common if you copied and pasted the code without reading the explanation of what that code does. Re-reading the tutorial may help solve the problem. |
|||
* We can't edit tutorials that are not part of the wiki, so we can't fix the issue. |
|||
== Your tools are too old or too new == |
|||
The end result is that practically all foreign tutorials have at least one nagging issue, and quite often, several. With people recreating tutorials at an increasing rate, there's no chance we can discover them all, and eventually suffer their backlash. |
|||
Features are added and removed from devtools all the time. If the tutorial is outdated it may be written for users of an outdated tool like [[TurboC]] or [[DOS]]. If it is too new then you may have be using tools which don't have features that the tutorial uses. If the tutorial is too old then you should find a newer tutorial or write it yourself without using a tutorial. If the tutorial is too new you should update your tools to the latest version and check the "Prerequisites" section in the tutorial if there is one. |
|||
== Tutorial bugs == |
|||
The solution is simple: They were wrong, you can't trust them, so stop bothering with them and use the [[Bare Bones]] instead. |
|||
There is always the chance that the tutorial might have bugs in it. If the tutorial has not been updated ever, the chance for bugs is higher than if the tutorial is updated regularly. If the tutorial is on the OSDev Wiki, you should check the Discussion tab and also check if the article is disputed. However, tutorial bugs are less common than you think so you should make sure that you did not screw up before you blame the tutorial author. |
|||
[[Category:FAQ]] |
[[Category:FAQ]] |
||
Revision as of 00:43, 10 September 2018
There are multiple reasons that an operating system based on a tutorial may not work.
You forgot a step
This is most common if you copied and pasted the code without reading the explanation of what that code does. Re-reading the tutorial may help solve the problem.
Your tools are too old or too new
Features are added and removed from devtools all the time. If the tutorial is outdated it may be written for users of an outdated tool like TurboC or DOS. If it is too new then you may have be using tools which don't have features that the tutorial uses. If the tutorial is too old then you should find a newer tutorial or write it yourself without using a tutorial. If the tutorial is too new you should update your tools to the latest version and check the "Prerequisites" section in the tutorial if there is one.
Tutorial bugs
There is always the chance that the tutorial might have bugs in it. If the tutorial has not been updated ever, the chance for bugs is higher than if the tutorial is updated regularly. If the tutorial is on the OSDev Wiki, you should check the Discussion tab and also check if the article is disputed. However, tutorial bugs are less common than you think so you should make sure that you did not screw up before you blame the tutorial author.