![]()
#WINDOWS 98 VIRTUALBOX MANUALS#The manuals I have to load this thing are written specifically for Procomm. Here's the problem with that, my knowledge of software like this is very limited. Sep 2008, 17:09 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Mostly XPĪnd btw: it really ought to be possible to reproduce the functionality with a modern Python script. mpack Site Moderator Posts: 37081 Joined: 4. It looks like the product was around until 2002, so there's a chance you can find a version that runs on modern Windows.Īnd btw: it really ought to be possible to reproduce the functionality with a modern Python script. I just did a quick Google and turned up the following Wikipedia article describing the fate of ProComm. Modern apps like PuTTY and Termite are very weak by comprison: the market simply isn't big enough to justify much effort. Then ADSL and fixed connection Internet killed them pretty dead. Windows bundled its own "HyperTerminal" back in the day, pretty shitty stuff, but people would rather struggle with that than buy quality, so ProComm and all similar software withered on the vine. I'd be surprised if ProComm didn't continue into the Windows era, and I'd be surprised if their scripts weren't backwards compatible. They had a C like script language which is, I assume, what is controlling your CNC machine. #WINDOWS 98 VIRTUALBOX SERIAL#ProComm is a standard serial terminal software app of the day, though on the pretty good end of the spectrum. I remember ProComm, in fact they were competitors of mine in their slightly later Procomm Plus days. Russell072009 wrote:The only way I know of to load it is using an old piece of software called procomm v2.01 Dec 2009, 20:14 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Windows, Linux scottgus1 Site Moderator Posts: 16614 Joined: 30. And be aware that getting a VM to talk to a robot correctly may not work well due to timing issues. ![]() #WINDOWS 98 VIRTUALBOX DRIVERS#A websearch in that said it may still be possible, though generic drivers may be needed.īut, we should first confirm that the CNC and the VM OS can communicate. #WINDOWS 98 VIRTUALBOX INSTALL#One other concept, see if 98 might still install enough on a newer but still older PC, perhaps from late 2000's. Try making a new VM, running the command, then start the VM and fresh-install 98, then try the CNC machine.Īlso see our 98 tutorial: viewtopic.php?f=28&t=9918 More web-searching on "change CPU type site:" might help.Ī fresh install of Windows 98 might be necessary for the CPU change to set up correctly. There is a way to restrict the CPU type, see viewtopic.php?t=84423. How does the CNC machine and the controlling computer connect? Serial port, parallel port, USB? If anyone has some advice for me about this it would be greatly appreciated. From what I have found you can specify some hardware in the VM and you can specify a processor but I can't figure out how exactly to do it. The only thing I can think of is change the VM processor to emulate an old 386. I even tried copying the files directly from the desktop to the VM, put everything in exactly the same spot but still get the same error. All I get is a runtime error R6003 divide by 0. Problem I am running in to is it will not run. I created a windows 98 VM and found a copy of the software online. I would like to get this program running on a laptop so I at least have a backup if the PC dies. I currently have it running on a VERY old windows 98 desktop which I also inherited with the controller. ![]() The only way I know of to load it is using an old piece of software called procomm v2.01. I inherited this problem and am looking for a way out of it using VB. ![]() I have a specific problem and am trying to figure out a way to resolve it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |