|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
I have a customer that runs a program through Basic. The routine will not
run in XP. I would like to get this converted over to another 'language' such as VB. Is there a conversion routine available to convert the lines of code? or is this a rewrite situation? Bruce Stiles wrote:
> I have a customer that runs a program through Basic. The routine will not There probably isn't a 100% solution. How close it comes to that depends on how > run in XP. I would like to get this converted over to another 'language' > such as VB. Is there a conversion routine available to convert the lines of > code? or is this a rewrite situation? well it was written originally, and what sort of things it did. It's possible to load and run "business logic" code directly from GWBASIC to VB6. There were only about three statements (iirc) that died -- READ, DATA, and SWAP. If it uses any of those, alternatives will need to be coded. That said, nearly all the i/o code (screen, keyboard, mouse, memory) will need to be rewritten. "Bruce Stiles" <jb2***@knology.net> wrote in message Besides what Karl said, there IS (I suppose) what could be considered an news:C3A6C1F9-024E-48B0-98CD-95DACE18CC8F@microsoft.com... >I have a customer that runs a program through Basic. The routine will not >run in XP. I would like to get this converted over to another 'language' >such as VB. Is there a conversion routine available to convert the lines of >code? or is this a rewrite situation? interim solution until you get the program re-written as a Windows app. If you can get a hold of something like QuickBasic, Basic PDS, VBDOS or pretty much any BASIC programming tool that can compile DOS exe files (QBasic won't work because it can't compile, although I can tell you that QBasic itself will run under WinXP, so I suppose it could be considered an option), you could take that GW-BASIC code and with probably minimal effort, compile a DOS executable that might run fine under XP (depending on exactly what the program does and assuming you're not talking about a 64 bit version of WinXP). But other than that, you're looking at re-writing the majority of it. As Karl said, if the "logic" code was well-written, that'd most likely work in VB6 with minimal re-writing and maybe none at all. However, if you're considering a .NET version of VB, even the "logic" code probably would need to be substantially re-written. The biggest things would be if your GW-BASIC program used READ and DATA. There's simply nothing close to that in VB6. The SWAP statement doesn't exist in VB6, but it's easy to write your own Swap sub. And of course like Karl mentioned, the UI, printing, etc. code from your GW-BASIC program can be thrown out the door. Actually, another interim option might be something like DOSBox or Virtual PC. Running programs that won't run under modern OSes is exactly what DOSBox and Virtual PC are designed to do. Virtual PC actually has many other uses while DOSBox really has just one: run old DOS programs (it's actually intended for DOS games though, and therefore lacks many DOS commands which typically weren't needed by most games). And the best news is that both are free. DOSBox is open source and can be downloaded at www.dosbox.com. Virtual PC is from Microsoft and can be downloaded at http://www.microsoft.com/downloadS/details.aspx?FamilyID=04d26402-3199-48a3-afa2-2dc0b40a73b6&displaylang=en (sorry if that link is broken by word-wrapping). DOSBox is a DOS emulator (it reports MS-DOS 5.0 as the version but does not fully emulate MS-DOS 5.0 as it does not include all MS-DOS 5.0 commands, mostly the external commands in the DOS directory). Virtual PC, on the other hand, emulates (or virtualizes) an entire computer. You even have to install the OS (which means that, legally, you need a legitimate license for the OS you're going to install). But that OS could be MS-DOS, Windows, Linux, OS/2, pretty much anything that runs on x86 computers (although only a few OSes are officially supported...for example, Virtual PC 2007 does not officially support MS-DOS or Windows 95, so for those OSes Virtual PC 2004 is actually better [but you can use the VMAdditions from Virtual PC 2004 for each of those OSes if you use Virtual PC 2007]). When you start a virtual machine, it goes through the entire boot process, you can enter into the BIOS setup, etc. However, all of these options should be considered soley as a way to "get by" until you can write a Windows app. -- Mike Since when is this a newsgroup about all kind of Basic versions beside VB6
including VB for Net. I also get the idea that somebody writes here about the newest VB versions without deeply knowing them. That let me think it will be the same for the rest of the reply. Cor Show quoteHide quote "MikeD" <nob***@nowhere.edu> wrote in message news:%23bOCIiz3JHA.5048@TK2MSFTNGP03.phx.gbl... > > "Bruce Stiles" <jb2***@knology.net> wrote in message > news:C3A6C1F9-024E-48B0-98CD-95DACE18CC8F@microsoft.com... >>I have a customer that runs a program through Basic. The routine will not >>run in XP. I would like to get this converted over to another 'language' >>such as VB. Is there a conversion routine available to convert the lines >>of code? or is this a rewrite situation? > > Besides what Karl said, there IS (I suppose) what could be considered an > interim solution until you get the program re-written as a Windows app. > > If you can get a hold of something like QuickBasic, Basic PDS, VBDOS or > pretty much any BASIC programming tool that can compile DOS exe files > (QBasic won't work because it can't compile, although I can tell you that > QBasic itself will run under WinXP, so I suppose it could be considered an > option), you could take that GW-BASIC code and with probably minimal > effort, compile a DOS executable that might run fine under XP (depending > on exactly what the program does and assuming you're not talking about a > 64 bit version of WinXP). > > But other than that, you're looking at re-writing the majority of it. As > Karl said, if the "logic" code was well-written, that'd most likely work > in VB6 with minimal re-writing and maybe none at all. However, if you're > considering a .NET version of VB, even the "logic" code probably would > need to be substantially re-written. The biggest things would be if your > GW-BASIC program used READ and DATA. There's simply nothing close to that > in VB6. The SWAP statement doesn't exist in VB6, but it's easy to write > your own Swap sub. And of course like Karl mentioned, the UI, printing, > etc. code from your GW-BASIC program can be thrown out the door. > > Actually, another interim option might be something like DOSBox or Virtual > PC. Running programs that won't run under modern OSes is exactly what > DOSBox and Virtual PC are designed to do. Virtual PC actually has many > other uses while DOSBox really has just one: run old DOS programs (it's > actually intended for DOS games though, and therefore lacks many DOS > commands which typically weren't needed by most games). And the best news > is that both are free. DOSBox is open source and can be downloaded at > www.dosbox.com. Virtual PC is from Microsoft and can be downloaded at > http://www.microsoft.com/downloadS/details.aspx?FamilyID=04d26402-3199-48a3-afa2-2dc0b40a73b6&displaylang=en > (sorry if that link is broken by word-wrapping). DOSBox is a DOS emulator > (it reports MS-DOS 5.0 as the version but does not fully emulate MS-DOS > 5.0 as it does not include all MS-DOS 5.0 commands, mostly the external > commands in the DOS directory). Virtual PC, on the other hand, emulates > (or virtualizes) an entire computer. You even have to install the OS > (which means that, legally, you need a legitimate license for the OS > you're going to install). But that OS could be MS-DOS, Windows, Linux, > OS/2, pretty much anything that runs on x86 computers (although only a few > OSes are officially supported...for example, Virtual PC 2007 does not > officially support MS-DOS or Windows 95, so for those OSes Virtual PC 2004 > is actually better [but you can use the VMAdditions from Virtual PC 2004 > for each of those OSes if you use Virtual PC 2007]). When you start a > virtual machine, it goes through the entire boot process, you can enter > into the BIOS setup, etc. > > However, all of these options should be considered soley as a way to "get > by" until you can write a Windows app. > > -- > Mike > Do you, like for other basics, have a better group to redirect the OP to?
/Henning Show quoteHide quote "Cor Ligthert[MVP]" <Notmyfirstn***@planet.nl> skrev i meddelandet news:ecm3ok13JHA.1716@TK2MSFTNGP03.phx.gbl... > Since when is this a newsgroup about all kind of Basic versions beside VB6 > including VB for Net. > > I also get the idea that somebody writes here about the newest VB versions > without deeply knowing them. > > That let me think it will be the same for the rest of the reply. > > Cor > > "MikeD" <nob***@nowhere.edu> wrote in message > news:%23bOCIiz3JHA.5048@TK2MSFTNGP03.phx.gbl... >> >> "Bruce Stiles" <jb2***@knology.net> wrote in message >> news:C3A6C1F9-024E-48B0-98CD-95DACE18CC8F@microsoft.com... >>>I have a customer that runs a program through Basic. The routine will not >>>run in XP. I would like to get this converted over to another 'language' >>>such as VB. Is there a conversion routine available to convert the lines >>>of code? or is this a rewrite situation? >> >> Besides what Karl said, there IS (I suppose) what could be considered an >> interim solution until you get the program re-written as a Windows app. >> >> If you can get a hold of something like QuickBasic, Basic PDS, VBDOS or >> pretty much any BASIC programming tool that can compile DOS exe files >> (QBasic won't work because it can't compile, although I can tell you that >> QBasic itself will run under WinXP, so I suppose it could be considered >> an option), you could take that GW-BASIC code and with probably minimal >> effort, compile a DOS executable that might run fine under XP (depending >> on exactly what the program does and assuming you're not talking about a >> 64 bit version of WinXP). >> >> But other than that, you're looking at re-writing the majority of it. As >> Karl said, if the "logic" code was well-written, that'd most likely work >> in VB6 with minimal re-writing and maybe none at all. However, if you're >> considering a .NET version of VB, even the "logic" code probably would >> need to be substantially re-written. The biggest things would be if your >> GW-BASIC program used READ and DATA. There's simply nothing close to that >> in VB6. The SWAP statement doesn't exist in VB6, but it's easy to write >> your own Swap sub. And of course like Karl mentioned, the UI, printing, >> etc. code from your GW-BASIC program can be thrown out the door. >> >> Actually, another interim option might be something like DOSBox or >> Virtual PC. Running programs that won't run under modern OSes is exactly >> what DOSBox and Virtual PC are designed to do. Virtual PC actually has >> many other uses while DOSBox really has just one: run old DOS programs >> (it's actually intended for DOS games though, and therefore lacks many >> DOS commands which typically weren't needed by most games). And the best >> news is that both are free. DOSBox is open source and can be downloaded >> at www.dosbox.com. Virtual PC is from Microsoft and can be downloaded at >> http://www.microsoft.com/downloadS/details.aspx?FamilyID=04d26402-3199-48a3-afa2-2dc0b40a73b6&displaylang=en >> (sorry if that link is broken by word-wrapping). DOSBox is a DOS emulator >> (it reports MS-DOS 5.0 as the version but does not fully emulate MS-DOS >> 5.0 as it does not include all MS-DOS 5.0 commands, mostly the external >> commands in the DOS directory). Virtual PC, on the other hand, emulates >> (or virtualizes) an entire computer. You even have to install the OS >> (which means that, legally, you need a legitimate license for the OS >> you're going to install). But that OS could be MS-DOS, Windows, Linux, >> OS/2, pretty much anything that runs on x86 computers (although only a >> few OSes are officially supported...for example, Virtual PC 2007 does not >> officially support MS-DOS or Windows 95, so for those OSes Virtual PC >> 2004 is actually better [but you can use the VMAdditions from Virtual PC >> 2004 for each of those OSes if you use Virtual PC 2007]). When you start >> a virtual machine, it goes through the entire boot process, you can enter >> into the BIOS setup, etc. >> >> However, all of these options should be considered soley as a way to "get >> by" until you can write a Windows app. >> >> -- >> Mike >> > "Cor Ligthert[MVP]" <Notmyfirstn***@planet.nl> wrote in message Cor, why do you have to be such an ass? At the rate you're going I can't news:ecm3ok13JHA.1716@TK2MSFTNGP03.phx.gbl... > Since when is this a newsgroup about all kind of Basic versions beside VB6 > including VB for Net. > > I also get the idea that somebody writes here about the newest VB versions > without deeply knowing them. > > That let me think it will be the same for the rest of the reply. > > Cor wait for your MVP status to be revoked. Idiot. Show quoteHide quote > > "MikeD" <nob***@nowhere.edu> wrote in message > news:%23bOCIiz3JHA.5048@TK2MSFTNGP03.phx.gbl... >> >> "Bruce Stiles" <jb2***@knology.net> wrote in message >> news:C3A6C1F9-024E-48B0-98CD-95DACE18CC8F@microsoft.com... >>>I have a customer that runs a program through Basic. The routine will not >>>run in XP. I would like to get this converted over to another 'language' >>>such as VB. Is there a conversion routine available to convert the lines >>>of code? or is this a rewrite situation? >> >> Besides what Karl said, there IS (I suppose) what could be considered an >> interim solution until you get the program re-written as a Windows app. >> >> If you can get a hold of something like QuickBasic, Basic PDS, VBDOS or >> pretty much any BASIC programming tool that can compile DOS exe files >> (QBasic won't work because it can't compile, although I can tell you that >> QBasic itself will run under WinXP, so I suppose it could be considered >> an option), you could take that GW-BASIC code and with probably minimal >> effort, compile a DOS executable that might run fine under XP (depending >> on exactly what the program does and assuming you're not talking about a >> 64 bit version of WinXP). >> >> But other than that, you're looking at re-writing the majority of it. As >> Karl said, if the "logic" code was well-written, that'd most likely work >> in VB6 with minimal re-writing and maybe none at all. However, if you're >> considering a .NET version of VB, even the "logic" code probably would >> need to be substantially re-written. The biggest things would be if your >> GW-BASIC program used READ and DATA. There's simply nothing close to that >> in VB6. The SWAP statement doesn't exist in VB6, but it's easy to write >> your own Swap sub. And of course like Karl mentioned, the UI, printing, >> etc. code from your GW-BASIC program can be thrown out the door. >> >> Actually, another interim option might be something like DOSBox or >> Virtual PC. Running programs that won't run under modern OSes is exactly >> what DOSBox and Virtual PC are designed to do. Virtual PC actually has >> many other uses while DOSBox really has just one: run old DOS programs >> (it's actually intended for DOS games though, and therefore lacks many >> DOS commands which typically weren't needed by most games). And the best >> news is that both are free. DOSBox is open source and can be downloaded >> at www.dosbox.com. Virtual PC is from Microsoft and can be downloaded at >> http://www.microsoft.com/downloadS/details.aspx?FamilyID=04d26402-3199-48a3-afa2-2dc0b40a73b6&displaylang=en >> (sorry if that link is broken by word-wrapping). DOSBox is a DOS emulator >> (it reports MS-DOS 5.0 as the version but does not fully emulate MS-DOS >> 5.0 as it does not include all MS-DOS 5.0 commands, mostly the external >> commands in the DOS directory). Virtual PC, on the other hand, emulates >> (or virtualizes) an entire computer. You even have to install the OS >> (which means that, legally, you need a legitimate license for the OS >> you're going to install). But that OS could be MS-DOS, Windows, Linux, >> OS/2, pretty much anything that runs on x86 computers (although only a >> few OSes are officially supported...for example, Virtual PC 2007 does not >> officially support MS-DOS or Windows 95, so for those OSes Virtual PC >> 2004 is actually better [but you can use the VMAdditions from Virtual PC >> 2004 for each of those OSes if you use Virtual PC 2007]). When you start >> a virtual machine, it goes through the entire boot process, you can enter >> into the BIOS setup, etc. >> >> However, all of these options should be considered soley as a way to "get >> by" until you can write a Windows app. >> >> -- >> Mike >> > Cor,
How come your english is so much better in "the other" group? Just devoted to be a pia, and fishing for points? /Henning Show quoteHide quote "Cor Ligthert[MVP]" <Notmyfirstn***@planet.nl> skrev i meddelandet news:ecm3ok13JHA.1716@TK2MSFTNGP03.phx.gbl... > Since when is this a newsgroup about all kind of Basic versions beside VB6 > including VB for Net. > > I also get the idea that somebody writes here about the newest VB versions > without deeply knowing them. > > That let me think it will be the same for the rest of the reply. > > Cor > > "MikeD" <nob***@nowhere.edu> wrote in message > news:%23bOCIiz3JHA.5048@TK2MSFTNGP03.phx.gbl... >> >> "Bruce Stiles" <jb2***@knology.net> wrote in message >> news:C3A6C1F9-024E-48B0-98CD-95DACE18CC8F@microsoft.com... >>>I have a customer that runs a program through Basic. The routine will not >>>run in XP. I would like to get this converted over to another 'language' >>>such as VB. Is there a conversion routine available to convert the lines >>>of code? or is this a rewrite situation? >> >> Besides what Karl said, there IS (I suppose) what could be considered an >> interim solution until you get the program re-written as a Windows app. >> >> If you can get a hold of something like QuickBasic, Basic PDS, VBDOS or >> pretty much any BASIC programming tool that can compile DOS exe files >> (QBasic won't work because it can't compile, although I can tell you that >> QBasic itself will run under WinXP, so I suppose it could be considered >> an option), you could take that GW-BASIC code and with probably minimal >> effort, compile a DOS executable that might run fine under XP (depending >> on exactly what the program does and assuming you're not talking about a >> 64 bit version of WinXP). >> >> But other than that, you're looking at re-writing the majority of it. As >> Karl said, if the "logic" code was well-written, that'd most likely work >> in VB6 with minimal re-writing and maybe none at all. However, if you're >> considering a .NET version of VB, even the "logic" code probably would >> need to be substantially re-written. The biggest things would be if your >> GW-BASIC program used READ and DATA. There's simply nothing close to that >> in VB6. The SWAP statement doesn't exist in VB6, but it's easy to write >> your own Swap sub. And of course like Karl mentioned, the UI, printing, >> etc. code from your GW-BASIC program can be thrown out the door. >> >> Actually, another interim option might be something like DOSBox or >> Virtual PC. Running programs that won't run under modern OSes is exactly >> what DOSBox and Virtual PC are designed to do. Virtual PC actually has >> many other uses while DOSBox really has just one: run old DOS programs >> (it's actually intended for DOS games though, and therefore lacks many >> DOS commands which typically weren't needed by most games). And the best >> news is that both are free. DOSBox is open source and can be downloaded >> at www.dosbox.com. Virtual PC is from Microsoft and can be downloaded at >> http://www.microsoft.com/downloadS/details.aspx?FamilyID=04d26402-3199-48a3-afa2-2dc0b40a73b6&displaylang=en >> (sorry if that link is broken by word-wrapping). DOSBox is a DOS emulator >> (it reports MS-DOS 5.0 as the version but does not fully emulate MS-DOS >> 5.0 as it does not include all MS-DOS 5.0 commands, mostly the external >> commands in the DOS directory). Virtual PC, on the other hand, emulates >> (or virtualizes) an entire computer. You even have to install the OS >> (which means that, legally, you need a legitimate license for the OS >> you're going to install). But that OS could be MS-DOS, Windows, Linux, >> OS/2, pretty much anything that runs on x86 computers (although only a >> few OSes are officially supported...for example, Virtual PC 2007 does not >> officially support MS-DOS or Windows 95, so for those OSes Virtual PC >> 2004 is actually better [but you can use the VMAdditions from Virtual PC >> 2004 for each of those OSes if you use Virtual PC 2007]). When you start >> a virtual machine, it goes through the entire boot process, you can enter >> into the BIOS setup, etc. >> >> However, all of these options should be considered soley as a way to "get >> by" until you can write a Windows app. >> >> -- >> Mike >> > Bruce,
I advice you for the newest VB version from this millennium to visit the newsgroup Microsoft.public.dotnet.languages.vb This newsgroup is only about VB versions from the previous century Cor Show quoteHide quote "Bruce Stiles" <jb2***@knology.net> wrote in message news:C3A6C1F9-024E-48B0-98CD-95DACE18CC8F@microsoft.com... >I have a customer that runs a program through Basic. The routine will not >run in XP. I would like to get this converted over to another 'language' >such as VB. Is there a conversion routine available to convert the lines of >code? or is this a rewrite situation? "Cor Ligthert[MVP]" <Notmyfirstn***@planet.nl> wrote in message In your own version of pidgin English, I advice you for the piss off news:e2HQ7l13JHA.2336@TK2MSFTNGP02.phx.gbl... > I advice you for the newest VB version > from this millennium to visit the newsgroup Ligthert. Your dotnet evangelism is not wanted here. If you wish to perpetuate the Micro$oft lie in payment for your MVP status then do so somewhere else. By the way, have you still got your head on upside down in your MVP photo? You look as though you've just had a wet dream. A very unsavoury looking character ;-) Mike Mike,
Thank you for helping me to inform Bruce. My thought was: there is not need to write about the behaviour of some persons in this newsgroup, at least Mike will do that. Cor Show quoteHide quote "Michael Williams" <M***@WhiskeyAndCoke.com> wrote in message news:etiClH33JHA.1416@TK2MSFTNGP04.phx.gbl... > "Cor Ligthert[MVP]" <Notmyfirstn***@planet.nl> wrote in message > news:e2HQ7l13JHA.2336@TK2MSFTNGP02.phx.gbl... > >> I advice you for the newest VB version >> from this millennium to visit the newsgroup > > In your own version of pidgin English, I advice you for the piss off > Ligthert. > > Your dotnet evangelism is not wanted here. If you wish to perpetuate the > Micro$oft lie in payment for your MVP status then do so somewhere else. By > the way, have you still got your head on upside down in your MVP photo? > You look as though you've just had a wet dream. A very unsavoury looking > character ;-) > > Mike > > > In my opinion, I would advice you to rewrite the entire program. The time
you're going to waste in adapting it to another Basic Language/Compiler in order to run under Xp, is not worth it. Most of the the code will be changed, specially screen output, printer output and eaven file I/O operations, which in the end will result in very few instructions to be used. Instructions such as Locate, PRINT and LPRINT have been removed or modified. File I/O has been changed. Variable declaration have suffered a few minor changes. Nevertherless you could try to find a compiler/converter for GWBASIC that could convert the program to Windows environment, try google-it... But consider my opinion.... NC Show quoteHide quote "Bruce Stiles" <jb2***@knology.net> wrote in message news:C3A6C1F9-024E-48B0-98CD-95DACE18CC8F@microsoft.com... >I have a customer that runs a program through Basic. The routine will not >run in XP. I would like to get this converted over to another 'language' >such as VB. Is there a conversion routine available to convert the lines of >code? or is this a rewrite situation?
Show quote
Hide quote
On Jun 1, 8:32 am, "Privado" <oceano.web***@netmadeira.com> wrote: GWBASIC Programs are easy to write, has limitation but if you can’t> In my opinion, I would advice you to rewrite the entire program. The time > you're going to waste in adapting it to another Basic Language/Compiler in > order to run under Xp, is not worth it. > > Most of the the code will be changed, specially screen output, printer > output and eaven file I/O operations, which in the end will result in very > few instructions to be used. Instructions such as Locate, PRINT and LPRINT > have been removed or modified. File I/O has been changed. Variable > declaration have suffered a few minor changes. > > Nevertherless you could try to find a compiler/converter for GWBASIC that > could convert the program to Windows environment, try google-it... > > But consider my opinion.... > > NC > > "Bruce Stiles" <jb2***@knology.net> wrote in message > > news:C3A6C1F9-024E-48B0-98CD-95DACE18CC8F@microsoft.com... > > >I have a customer that runs a program through Basic. The routine will not > >run in XP. I would like to get this converted over to another 'language' > >such as VB. Is there a conversion routine available to convert the lines of > >code? or is this a rewrite situation? find another ready to go program, GWBASIC is a problem solver. I’m not o programmer, but a start programming in GWBASIC since 1983 and me still making programs today. In windows 2000 and, XP DOSSHELL won’t let you to ran GWBASIC.EXE. You can go to command, type A: and you will get A:\> If you type DIR you will see the directory of Floppy disk A. COMMAND.COM GWBASIC.EXE SIMOPTIM.BAS Now try Run GWBASIC.EXE typing GWBASIC You will get: You can not SHELL to BASIC. To execute GWBASIC program you have to load DOS 3.3 – 7.0 The OS for window XP is Microsoft Windows XP [Version 5.1.2600] This OS cannot SHELL to BASIC. There are only two options. Find a PC or Note book with Floppy Drive. Format a Floppy disk with the system. Load GWBASIC.EXE and run GWBASIC Programs. or Load Quick Basic 4.5 in a formatted floppy disk, with system, and compile your GWBASIC program and get an #########.EXE file. This file transferred in a folder can be executed under XP with a click of a mouse. If you create a menu program under DOS to run multiple ####.EXE files the menu program will run, execute first file and stops, why … and don’t know and have no time to figure out why. Keep in mind that GWBASIC is an abandoned software, and there is no support anymore. I took a cd-rom to which I had backup my Windows 3.1x disk partitions.
In a command prompt window I loaded 02/09/1988 01:00a 80,592 GWBASIC.EXE D: cd\c-drive\dos gwbasic GW-BASIC 3.22 (C) Copyright Microsoft 1983,1984,1985,1986,1987 60300 Bytes free Ok 1LIST 2RUN? 3LOAD" 4SAVE" 5CONT? 6,"LPT1 7TRON? 8TROFF? 9KEY 0SCREEN I did have problems loading a program and got an error "Direct statement in file" no matter which bas file I typed to load. When I loaded 09/30/1993 07:20a 130,881 QBASIC.HLP 09/30/1993 07:20a 194,309 QBASIC.EXE I was able to load a program and run it to the point it stop on an error "File not found" which since the file was not there was a correct error to get. To the best of my memory QBASIC ran fine except of a few commands. Stan bluerose wrote: Show quoteHide quote > > On Jun 1, 8:32 am, "Privado" <oceano.web***@netmadeira.com> wrote: > > In my opinion, I would advice you to rewrite the entire program. The time > > you're going to waste in adapting it to another Basic Language/Compiler in > > order to run under Xp, is not worth it. > > > > Most of the the code will be changed, specially screen output, printer > > output and eaven file I/O operations, which in the end will result in very > > few instructions to be used. Instructions such as Locate, PRINT and LPRINT > > have been removed or modified. File I/O has been changed. Variable > > declaration have suffered a few minor changes. > > > > Nevertherless you could try to find a compiler/converter for GWBASIC that > > could convert the program to Windows environment, try google-it... > > > > But consider my opinion.... > > > > NC > > > > "Bruce Stiles" <jb2***@knology.net> wrote in message > > > > news:C3A6C1F9-024E-48B0-98CD-95DACE18CC8F@microsoft.com... > > > > >I have a customer that runs a program through Basic. The routine will not > > >run in XP. I would like to get this converted over to another 'language' > > >such as VB. Is there a conversion routine available to convert the lines of > > >code? or is this a rewrite situation? > > GWBASIC Programs are easy to write, has limitation but if you can’t > find another ready to go program, GWBASIC is a problem solver. > I’m not o programmer, but a start programming in GWBASIC since 1983 > and me still making programs today. > In windows 2000 and, XP DOSSHELL won’t let you to ran GWBASIC.EXE. > You can go to command, type A: and you will get A:\> > If you type DIR you will see the directory of Floppy disk A. > COMMAND.COM > GWBASIC.EXE > SIMOPTIM.BAS > Now try Run GWBASIC.EXE typing GWBASIC > You will get: > You can not SHELL to BASIC. > To execute GWBASIC program you have to load DOS 3.3 – 7.0 > The OS for window XP is Microsoft Windows XP [Version 5.1.2600] > This OS cannot SHELL to BASIC. > There are only two options. > Find a PC or Note book with Floppy Drive. > Format a Floppy disk with the system. Load GWBASIC.EXE and run GWBASIC > Programs. > or > Load Quick Basic 4.5 in a formatted floppy disk, with system, and > compile your GWBASIC program and get an #########.EXE file. > This file transferred in a folder can be executed under XP with a > click of a mouse. > If you create a menu program under DOS to run multiple ####.EXE files > the menu program will run, execute first file and stops, why … and > don’t know and have no time to figure out why. Keep in mind that > GWBASIC is an abandoned software, and there is no support anymore. 
Other interesting topics
|
|||||||||||||||||||||||
