This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Which is better, DOS or uvision?

I recently inherited a pile of software from another division.
The code was developed several years ago using only DOS.
I am curious to know if I will hurt myself in anyway by using the GUI IDE. uvision 1.13
The files were originally developed using ver 4 of the compiler, L51, and Symantec smake.
Additionally, where could I look to find info on smake?

I do appreciate any suggestions....

Parents
  • On WinNT and 2000 it's not DOS, it's a full 32-bit console without filename limitations. Make is easy to use and allows one to call it from CodeWright (a very good Windows editor) and then parse any build errors within the editor. Why? Because the editor in uVision is weak compared to something like CodeWright.

    I do use uVision for builds but I use CodeWright to call C51.exe for compilation checks. I make uVision just big enough to see the Build button and the output of the build. It is my "make" utility only, I never use it for editing.

Reply
  • On WinNT and 2000 it's not DOS, it's a full 32-bit console without filename limitations. Make is easy to use and allows one to call it from CodeWright (a very good Windows editor) and then parse any build errors within the editor. Why? Because the editor in uVision is weak compared to something like CodeWright.

    I do use uVision for builds but I use CodeWright to call C51.exe for compilation checks. I make uVision just big enough to see the Build button and the output of the build. It is my "make" utility only, I never use it for editing.

Children