Just to finally add :
cheers for pointing me in the direction of a good next step lord mage , I must admit Im actually starting to see how people could get lots out of os dev ! Getting good info like the brokenthorn guide for myself has been a must, Im going to check out the guide you suggested, hopefully those guides together give me as good a start as possible. (Time to get reading again
)
Edit:
The file demo 4.zip on the broken thorn tutorial works perfectly
Im going to just start making sure to get to grips with inline assembly, assembly and C and start adding my own content with whats in that zip as a base(God help us all lol) . Anyway this is probably nothing to worry about but Its either stage 2 or 3 on the page that you can download demo4 well the nasm batch file executed command gives a dwords bounds warning. So Im thinking say I wanted to do something simple like print my name with a really un-standard print c function, which uses memcpy,memset , maybe I will lump all these functions plus 1 execution - print hello test all in a file called myprint_test.c next I create a linker script , compile the src file myprint_test.c , link the myprint_test.o file to stage3.asm from neons tutorial
Im hoping the good practice of the way the stack & such is setup from neons tutorial and his stage 3 will be able to have part of brans c files integrated. I followed all the tutorial great but its the visual c part, even though I managed to get the menus filled in correctly I didnt follow some of the VC unique naming conventions MCX:A or something strange like that so I figured I would be better getting gcc with ld working at this point.
I think VC must only be good if youve worked in the OS dev industry or know the software inside out , but I dont want to be fighting with 100s of ide settings, I would rather be learning by my coding as much as poss. (Plus as mentioned those naming conventions at the end of the VC tutorial are whack lol , they dont seem to stand for anything that makes sense)
I better be clear about what Im reffering to actually
Ok this page:
http://www.brokenthorn.com/Resources/OSDevMSVC.html
Go down to MS Naming conventions
The section names used in MSVC++ are very strange. Serously--.CRT$XCU? What were they thinking!?
Yeah neon I would like to know that also
from that statement on I was lost and Im not talking about the cdecl calling convention but microsofts naming
I reckon VC must be good but I just want to be able to compile and link as lightweight as possible minimum garbage and add stuff slowly, maybe adding more C standards as I know what Im doing, just seems with VC it adds a big overhead at the start, which I feel Im going to have most of my time just taken up comprehending the coding so I am going to try making my own c functions with gcc.
(Still awsome guide , but bringing VC in with all the considerations it beings to the table would probably require a huge guide in itself, I dont envy you having to write guides like that hehe)