The reason I want to use DOS is that I need to develop scientific computing programs. Some years ago I did this with watcom c. The reason I chose this compiler was that it could break through the memory limits of tc and the like, so I could allocate very large arrays.
Now I need to write this kind of program again, but I haven't used VC, so I don't know whether the old problem is still there. Besides, Windows has always been a huge resource hog. The operating system itself takes up a lot of memory, so how much is left for applications? So I decided to go back to DOS.
But the PC I'm using is a mobile PC, the computer acts up from time to time, and it only has a USB mouse, so this is troublesome. Debugging and writing programs without a mouse would drive anyone crazy. So I searched on Google and finally found this great place, and it even has an introduction on how to drive a mouse under DOS.
I spent the whole day messing with it today, and the results were not ideal. Early in the morning, I first installed dos71, using the boot disk recommended by the moderator, but right after installing it I saw that it didn't support long filenames or Chinese. Wasn't it said these were no problem at all? Fortunately this is not a big issue and doesn't affect my application. I immediately installed the usbdrv driver package, and with just
DEVICE=USBASPI1.SYS
DEVICE=DI1000DD.SYS
these two lines, I easily got my USB flash drive and mobile hard disk working, though the boot speed became much slower. Next I went straight to the main topic---the mouse problem. Right away I ran into terms like OHCI/UHCI/EHCI. I don't know which type my machine is (it has four USB ports), but never mind, I tried OHCI first, because I saw the word OHCI in XP's hardware manager. The lines were roughly these two: DEVICE=OHCI.EXE, and DEVICE=ASPIOHCI.SYS. But if I boot with these two lines, the machine hangs. Helpless, I switched to UHCI. The machine could boot, but in the end it showed no adapter present. After entering edit and taking a look, the mouse had no response at all. Then I looked around online again and learned that 4dos can also solve this kind of problem, but unfortunately it seems to be paid software.
That's today's result. Don't be fooled by just these two lines; I spent the whole day going back and forth between two operating systems. In the end the problem is still not solved. I'd like to ask the experts here, did I make a mistake somewhere? I think there must be many people like me who only have a USB mouse.
Waiting for an expert to come to the rescue!!!
One more question: what was the final DOS version of watcom C? I'm using 9.0. I used to have 10.0, but I don't know where I misplaced it. I can't download it online now either.
Now I need to write this kind of program again, but I haven't used VC, so I don't know whether the old problem is still there. Besides, Windows has always been a huge resource hog. The operating system itself takes up a lot of memory, so how much is left for applications? So I decided to go back to DOS.
But the PC I'm using is a mobile PC, the computer acts up from time to time, and it only has a USB mouse, so this is troublesome. Debugging and writing programs without a mouse would drive anyone crazy. So I searched on Google and finally found this great place, and it even has an introduction on how to drive a mouse under DOS.
I spent the whole day messing with it today, and the results were not ideal. Early in the morning, I first installed dos71, using the boot disk recommended by the moderator, but right after installing it I saw that it didn't support long filenames or Chinese. Wasn't it said these were no problem at all? Fortunately this is not a big issue and doesn't affect my application. I immediately installed the usbdrv driver package, and with just
DEVICE=USBASPI1.SYS
DEVICE=DI1000DD.SYS
these two lines, I easily got my USB flash drive and mobile hard disk working, though the boot speed became much slower. Next I went straight to the main topic---the mouse problem. Right away I ran into terms like OHCI/UHCI/EHCI. I don't know which type my machine is (it has four USB ports), but never mind, I tried OHCI first, because I saw the word OHCI in XP's hardware manager. The lines were roughly these two: DEVICE=OHCI.EXE, and DEVICE=ASPIOHCI.SYS. But if I boot with these two lines, the machine hangs. Helpless, I switched to UHCI. The machine could boot, but in the end it showed no adapter present. After entering edit and taking a look, the mouse had no response at all. Then I looked around online again and learned that 4dos can also solve this kind of problem, but unfortunately it seems to be paid software.
That's today's result. Don't be fooled by just these two lines; I spent the whole day going back and forth between two operating systems. In the end the problem is still not solved. I'd like to ask the experts here, did I make a mistake somewhere? I think there must be many people like me who only have a USB mouse.
Waiting for an expert to come to the rescue!!!
One more question: what was the final DOS version of watcom C? I'm using 9.0. I used to have 10.0, but I don't know where I misplaced it. I can't download it online now either.
