Printable View
does anyone know ,how did MS tested the windows .
i mean you test your program on lets say windows platform
,so how did they test their program"operating system" ?
what sort of compilers they used or was part of the code machine language?is the IO.SYS and MSDOS.SYS andSYSINI and CONFIG.SYS written in machine language does anyone know?
The vast majority of windows is written in C with a small amount of asm. I wouldnt be surprised if they used a fair bit of c++ too especially on the gui side of things.
The basic operating system would not have been written on visual c. I have no idea which compiler they used but visual c is not suitable for operating system programming.
As for building and testing an operating system you can find details at Flashdaddees where they have an active operating systems forum.Read the stickies there for some good links.
pretty much what coder said is right. its hard telling what compilers/linkers microsoft used because they arent too big on giving out too much information. but me personally to write my own os i'm using NASM (form of assembly) and for C i'm using the gcc.
> The basic operating system would not have been written on visual c. I have no idea which compiler they used but visual c is not suitable for operating system programming.
Apparently they used VC++ scroll down about half-way to where it says Microsoft
-Futura
No way.
I will go out on a limb here and say that no flavours of windows have been fully written in visual c. It is NOT POSSIBLE to compile an operating system with it. They could not have used it to do the operating system. They could on the other hand have used visual c to do the gui side of things once the operating system was written and in place.
iv read a couple of places that says ms used vc++ to build windows xp, they even go further saying the bootloader was written in vc++ using asm inside the vc++ enviroment, dont know if that is true, but will try to find the links when i get home from work today
vc++ is just that...an environment. it doesnt matter if you write the code in notepad (which i personally do) or if you write it in vc++. as long as the files and output is the same it makes no difference.
imo, notepad is nice and simple and the perfect thing for os coding.
The IDE is not the real item under discussion here. It is the compiler, CL.EXE. (When you press F7, the IDE runs the necessary executables to compile your resources, code etc., and then the linker as necessary to build your .exe, .dll, .lib etc...).
>>> notepad is nice and simple and the perfect thing for os coding.
So you've typed in your code - how do you compile it?
> No way.
I'm not arguing, but I'm not really in a position to argue with Bjarne Stroustrup either and he seems to think most versions of Windoze were written in VC++.
over & out.
to assemble it i use nasm, to compile the c code i use gcc. that's pretty much the standard for this sort of thing. and just link with any linker you can get your hands on.Quote:
Originally posted by adrianxw
The IDE is not the real item under discussion here. It is the compiler, CL.EXE. (When you press F7, the IDE runs the necessary executables to compile your resources, code etc., and then the linker as necessary to build your .exe, .dll, .lib etc...).
>>> notepad is nice and simple and the perfect thing for os coding.
So you've typed in your code - how do you compile it?
i test with bochs. it's a great and powerful tool. you can run your os while still in windows. reports errors, register values, eip, and all other goodies. :)
>>> to assemble it i use nasm, to compile the c code i use gcc.
Ah, so not VC++.
This isn't going anywhere is it. It all seems to hinge on a statement by Stroustrup that, in the same article, ha says he can only accept others word for it being true.
Well, I havent written any part of windows, so I dont really know.Quote:
Originally posted by Stoned_Coder
No way.
I will go out on a limb here and say that no flavours of windows have been fully written in visual c. It is NOT POSSIBLE to compile an operating system with it. They could not have used it to do the operating system. They could on the other hand have used visual c to do the gui side of things once the operating system was written and in place.
I have noticed that in a WDM text that the author condones linking to the Visual-C std functions (msvcrt##.dll) in some situations......He then goes on to say that VC++ is the only guaranteed compiler for WDM (but its a M$Press book....so no real suprises)
For stuff like bootstraps and other "tight" situations then I dont know if you can use anything but ASM........but for a lot of other stuff, I dont see why they cant use VC++...they have to use something......
But then as I say, I havent written any part of windows, so I cant know for sure.
<edit>Also, I wouldnt be suprised how in how many of the ActiveX led components of a windows system are written in VB!</edit>
visual c cant do flat binary format( com files) or anything 16bit. If you write an os then your computer will start in real mode and need 16bit addressing. You cant write a boot sector using inline asm in vis c because you cannot link to a 512 byte flat binary using the microsoft linker.
GCC and NASM seem to be the preferred os dev environments.
Yeah...I dont disagree...but after the mode is switched to protected, then I suppose lots of stuff can be done with VC++....Quote:
Originally posted by Stoned_Coder
visual c cant do flat binary format( com files) or anything 16bit. If you write an os then your computer will start in real mode and need 16bit addressing. You cant write a boot sector using inline asm in vis c because you cannot link to a 512 byte flat binary using the microsoft linker.
You can write in flat binary with MASM using the right model and processor directives.....and also, the early versions of LINK.exe (the M$ linker) can link create raw binary code (a copy of this linker is available for download on the web....Iczelion's site has it)
I managed to write a bootstrap using MASM a while ago (using compuboy's walkthrough for NASM)......sat on a floppy disk & worked pretty well.......I was going to try add FAT support for the disk too...but I lost interest