Re: [Freedos-user] printing to USB
Hi Christian, Well, 17 lines of Assembly and 5000 of C, It would interest me where he stated these numbers. He did not. I just did unzip -p the-sources.zip *.a* | wc :-) Who will ever be able to understand and update Georg's host driver? Certainly not anyone except him, since it's closed source. The interface is well-documented and you write software for Windows, Linux, DOS without reading their source, too. I'm not interested about that. Even if Georg's drivers are faster, I trust Bret's work more Why that? What do you mean by compatibility? Support for most different USB controllers and USB devices. If they both give access to the packet layer (the Georg Potthast one does, afair) through their APIs in some way, it should be possible to write a wrapper: Then you could use device drivers made for one of the 2 USB stacks with the respectively other USB stack :-). I would prefer if a single host driver would become a standard - making such wrappers, which could potentially cause a lot of bugs, unnecessary. If X gets more popular than Y, we can give Y a wrapper to provide the API of X. That is what I meant. By what I've read from Bret's documentation, the wrapper thing might be impossible anyway - Bret's host driver is designed for interrupt-driven background execution. (Since it's modular too, meaning that the main module only contains the host driver, the specific device drivers for things such as disks and pen drives have access to the USB packets using the API.) Apart from IRQ support (good idea) the modularity is similar in both. Last time someone provided a FreeDOS special licensing (I'm thinking of 4DOS) it wasn't really accepted. Why? Because FreeDOS seems to imply... I think the 4DOS case was some sort of misunderstanding which later got clarified into a more universal license. It doesn't state that it has XYZ's license, but the provided explanation clearly states how the programs are meant to be used. Okay, still XYZ license is a good thing to have :-) All of these programs, as well as their documentation and source code, are freely available to anyone who wants them. Maybe add BSD or Artistic license then :-) You also cannot distribute the programs, documentation, or source code and charge (even indirectly) for their distribution. Similar to shareware days - do not charge for distribution. Eric PS Johnson: SOME examples are in Basic, some are in Assembly or even Pascal or C. You can use any language of your choice to talk to the well-documented closed-source USB stack to support the USB devices of your choice :-). The stack and some of the drivers ARE small because they ARE already written in ASM. Just some of the examples are in BASIC maybe because that could be easier to read. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
Well, 17 lines of Assembly and 5000 of C, It would interest me where he stated these numbers. He did not. I just did unzip -p the-sources.zip *.a* | wc :-) So you don't know how many of that 17 lines are commentary only or blank. This is something I'm interested in, so I wrote me a program that counts the total lines of NASM source files, but also showing how many lines contained nothing (blank), only a comment (with ; or as block with %if 0) or actual code (labels or instructions). Who will ever be able to understand and update Georg's host driver? Certainly not anyone except him, since it's closed source. The interface is well-documented and you write software for Windows, Linux, DOS without reading their source, too. And if the people that own the Windows source decide to abandon that Windows version, you aren't able to understand and update it proper either. (understanding means to understand the internal working, i.e. the source code's operation, because I write in response to your might not understand large project.) My point isn't not to write drivers for either software, it's that closed-source software is abandoned if the ones having the source don't update and support it. This doesn't affect users of the software or using it directly. I'm not interested about that. Even if Georg's drivers are faster, I trust Bret's work more Why that? As mentioned, I looked into some of his work. Plus I'm annoyed at how long it took Georg to understand a simple issue of his drivers I asked him to fix. What do you mean by compatibility? Support for most different USB controllers and USB devices. When Bret's finished with UHCI support, both drivers will support the same host controllers. Support for devices depends on which drivers are available for that host software. I think both currently support disks/drives, mice, keyboards and some ports. Apart from IRQ support (good idea) the modularity is similar in both. Are the host controller drivers modular too? This is the part of the host driver which interacts with either EHCI, UHCI or OHCI hardware. I think the 4DOS case was some sort of misunderstanding which later got clarified into a more universal license. Which didn't contain much of the FreeDOS exception stuff anymore I think. All of these programs, as well as their documentation and source code, are freely available to anyone who wants them. Maybe add BSD or Artistic license then :-) BSD doesn't have Copyleft, and it allows turning the program into commercial software. Which Bret doesn't want. Please read through the full reply and discard inapplicable answers then. You also cannot distribute the programs, documentation, or source code and charge (even indirectly) for their distribution. Similar to shareware days - do not charge for distribution. Only that shareware is different - it disallows charging because the author wants to sell it, and doesn't want to lose profit by others selling his stuff. The stack and some of the drivers ARE small because they ARE already written in ASM. I worry that Georg isn't really good in Assembly. Just some of the examples are in BASIC maybe because that could be easier to read. BASIC easier to read than Assembly or C? Than both the Assembly and C code must be obfuscated a lot first. How could BASIC be easy to read? Note also that the low-level calls to the API are almost inline Assembly anyway, working with specific registers and interrupts. Linking an external object module is much better if Assembly parts are required. Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
Hi Johnson, PS: Have you tested the drivers from http://bretjohnson.us/ yet? That one is more open source but only does UHCI USB 1.1. :-). Finally someone did the job: Code USB programs with assembly language. Well, 17 lines of Assembly and 5000 of C, who will ever be able to understand and update that code? I hope at least Bret still understands it :-). By the way, what is the license? I am really curious about performance and compatibility comparisons between the Bret Johnson USB drivers and the Georg Potthast drivers. Did anybody try them both yet? URLs: http://bretjohnson.us/ - www.auersoft.eu/dosusb14.zip If they both give access to the packet layer (the Georg Potthast one does, afair) through their APIs in some way, it should be possible to write a wrapper: Then you could use device drivers made for one of the 2 USB stacks with the respectively other USB stack :-). As said, the FreeDOS OEM edition of the G.P. drivers is free for any use with FreeDOS and has public domain device drivers but a closed source freeware USB stack, while the B.J. drivers are completely source available but I could not find the license details for that one. Eric -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
Finally someone did the job: Code USB programs with assembly language. Well, 17 lines of Assembly and 5000 of C, It would interest me where he stated these numbers. who will ever be able to understand and update that code? Who will ever be able to understand and update Georg's host driver? Certainly not anyone except him, since it's closed source. I hope at least Bret still understands it :-). What's your point? Good code is easier to maintain than bad code, and by what I've read from him (I previously looked at some of his other programs, before he released the USB stuff) his code is very good, commented a lot and easily understood by anyone able to write in that programming language. I am really curious about performance and compatibility comparisons between the Bret Johnson USB drivers and the Georg Potthast drivers. I'm not interested about that. Even if Georg's drivers are faster, I trust Bret's work more and think he's faster and better regarding support. What do you mean by compatibility? If they both give access to the packet layer (the Georg Potthast one does, afair) through their APIs in some way, it should be possible to write a wrapper: Then you could use device drivers made for one of the 2 USB stacks with the respectively other USB stack :-). I would prefer if a single host driver would become a standard - making such wrappers, which could potentially cause a lot of bugs, unnecessary. By what I've read from Bret's documentation, the wrapper thing might be impossible anyway - Bret's host driver is designed for interrupt-driven background execution. (Since it's modular too, meaning that the main module only contains the host driver, the specific device drivers for things such as disks and pen drives have access to the USB packets using the API.) As said, the FreeDOS OEM edition of the G.P. drivers is free for any use with FreeDOS and has public domain device drivers but a closed source freeware USB stack, Last time someone provided a FreeDOS special licensing (I'm thinking of 4DOS) it wasn't really accepted. Why? Because FreeDOS seems to imply that it can be used on FreeDOS systems only, but not on those running MS-/PC-/DR-/EDR-/PTS-/RxDOS instead. (Whether a system is defined by the kernel only or by a set of distributed programs doesn't matter in this case, it's bad either way.) while the B.J. drivers are completely source available but I could not find the license details for that one. Read the documentation. It doesn't state that it has XYZ's license, but the provided explanation clearly states how the programs are meant to be used. I'll cite USBINTRO.DOC a bit: All of these programs, as well as their documentation and source code, are freely available to anyone who wants them. Should be less difficult to understand. You can use the programs without restriction, but you cannot directly or indirectly use the executable programs, documentation, or source code to create or distribute new programs that are not also freely available. It contains some sort of Copyleft. You also cannot distribute the programs, documentation, or source code and charge (even indirectly) for their distribution. From this, and what I've read from Bret elsewhere, it seems that you aren't allowed to sell the program/documentation/source itself, but usage in a business shouldn't be restricted. (Just ask Bret if in doubt, it's his work.) Note that the cited parts aren't the full license as stated in USBINTRO.DOC. There you'll find some more text with clarifications and such. Essentially, the license is mostly similar to the GPL [version 2] (with emphasis on the mustn't-sell-it-itself point) but MUCH shorter and easier to understand. Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
On Wed, 22 Jul 2009 23:43:05 +0200, you wrote: Eric, Well, 17 lines of Assembly and 5000 of C, who will ever be able to understand and update that code? I hope at least Bret still understands it :-). By the way, what is the license? There're always SOMEONE can do it, if HE wish. I am really curious about performance and compatibility comparisons between the Bret Johnson USB drivers and the Georg Potthast drivers. Did anybody try them both yet? Not yet, but I'm sure Phtthast's version have almost no room for improvement, except he do it himself, the sample code is in strange BASIC that few people can understand, and code drivers in high-level language usually is not recommended. If they both give access to the packet layer (the Georg Potthast one does, afair) through their APIs in some way, it should be possible to write a wrapper: Then you could use device drivers made for one of the 2 USB stacks with the respectively other USB stack :-). But the driver need to be small and solid, otherwise neither take a lot of memory or conflict with others. As said, the FreeDOS OEM edition of the G.P. drivers is free for any use with FreeDOS and has public domain device drivers but a closed source freeware USB stack, while the B.J. drivers are completely source available but I could not find the license details for that one. Bret Johnson seems have no details, should be public domain or GPL, you can ask him if you wish to improve his driver. Rgds, Johnson. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
On Fri, 17 Jul 2009 19:02:59 +0200, you wrote: Hi, PS: Have you tested the drivers from http://bretjohnson.us/ yet? That one is more open source but only does UHCI USB 1.1. :-). Finally someone did the job: Code USB programs with assembly language. Rgds, Johnson. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
This drivers are free and open source , and contain drivers for printing via usb... http://bretjohnson.us/ Roberto iw2evk Johnson Lam wrote: On Thu, 16 Jul 2009 15:19:33 -0300, you wrote: Hi, Unfortunately it is only free for personal use... Too bad, it's coded in BASIC, also it's not free. Jack did thinking of a small and beautiful USB driver for DOS (with BIOS call), but he have no sample code (I don't think Intel will have sample code in assembly). And information (how to code for EHCI or UHCI ... just drop the OHCI, it's slow and outdated). If anyone can help to gather these information, please update me. Rgds, Johnson. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- View this message in context: http://www.nabble.com/printing-to-USB-tp24508902p24529116.html Sent from the FreeDOS - User mailing list archive at Nabble.com. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
Hi Alain, In fact this (http://www.georgpotthast.de/usb) is a full USB driver for DOS, with both UHCI and OHCI. It has drivers for Parallel and Serial devices, plus pendrive. Unfortunately it is only free for personal use... Actually there is a new FreeDOS OEM edition which is free for ANY use in combination with FreeDOS. It is also meant to be put into our FreeDOS 1.1 distro. The USB stack itself is closed source, but most drivers are open source and even in public domain. Some examples are in ASM or C, but several are written in BASIC, too :-) If somebody has the right compiler: It would be nice to modify the drivers to let them check whether the interrupt handler exists (is not a NULL pointer) before calling the USB stack API. Thanks :-). We should also put a copy on IBIBLIO :-). Sorry for being so slow with publishing this news, I had been hoping to get around to add this null pointer check first... The URL of the DOSUSB OEM edition is: www.auersoft.eu/dosusb14.zip (supports USB 1.0 OHCI and 1.1 UHCI but not yet USB 2.0 EHCI) Cheers, Eric PS: Have you tested the drivers from http://bretjohnson.us/ yet? That one is more open source but only does UHCI USB 1.1. :-). -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
For solve the problem you can download the free software dosusb http://www.georgpotthast.de/usb/dosusb.zip in the package are insert some utlities for printing via usb port on DOS see for documentation : 3.1 Printer driver There are two printer drivers available. LPT1USB.SYS installs as a LPT1: device while PRNUSB.SYS installs as the PRNUSB: device. So you with the latter driver you can use LPT1: for other printers if needed, while with LPT1USB.SYS you can print from the DOS Editor or other application programs directly. Both are printer device drivers which use DosUSB to print to USB printers. They will work with a HP 2420d Laserprinter, a HP 880C, a HP 5940 and a HP 460C inkjet printer. They will also work with parallel to USB adapters. Check the endpoints and use the setalt utility to set the interface before printing here. LPT1USB.SYS and PRNUSB.SYS are loaded with a device= statement in the config.sys file or with the DEVLOAD utility. Load DosUSB then, do not use the /L command line option here! The default device address is one, the default device endpoint is two. Use the command line options e.g. /D2 /E1 to select device address two and endpoint number one. Use USBView to determine the right settings for your printer. These drivers cannot be used with low cost GDI printers, since these do not accept ASCII code for printing. They expect data which controls their print head directly. This protocol is vendor specific and usually not available. If a printer accepts ASCII code via its parallel interface, it usually can also do this via its USB interface. Use type dosusb.txt lpt1 or type dosusb.txt prnusb to print the file dosusb.txt from the DOS prompt. Or open lpt1 or prnusb as a file in your application program Michael Potter-4 wrote: Hi, I have googled and googled and googled this question and have not found an easy answer. That is strange because this seems like something that would be a common problem. I have an old DBase application that I am reviving to run under FreeDOS. It prints to a parallel printer when running on real hw, but when running in FreeDOS in VirtualBox I want it to print to a USB printer. What is the best way to do that? The printer shows up in the Devices-USB menu in Virtual box. Here is the advise I received from a friend how to do it under DOS running within XP: a) Setup the printer in Windows, then SHARE the printer. Then in DOS, one can do this: b) NET USE lpt1: \\windowspc\printershare What would be the equivalent of that in FreeDOS? -- Michael Potter -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- View this message in context: http://www.nabble.com/printing-to-USB-tp24508902p24510670.html Sent from the FreeDOS - User mailing list archive at Nabble.com. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
Hi, In fact this (http://www.georgpotthast.de/usb) is a full USB driver for DOS, with both UHCI and OHCI. It has drivers for Parlel and Serial devices, plus pendrive. Unfortunately it is only free for personal use... Alain iw2evk escreveu: For solve the problem you can download the free software dosusb http://www.georgpotthast.de/usb/dosusb.zip in the package are insert some utlities for printing via usb port on DOS see for documentation : 3.1 Printer driver There are two printer drivers available. LPT1USB.SYS installs as a LPT1: device while PRNUSB.SYS installs as the PRNUSB: device. So you with the latter driver you can use LPT1: for other printers if needed, while with LPT1USB.SYS you can print from the DOS Editor or other application programs directly. Both are printer device drivers which use DosUSB to print to USB printers. They will work with a HP 2420d Laserprinter, a HP 880C, a HP 5940 and a HP 460C inkjet printer. They will also work with parallel to USB adapters. Check the endpoints and use the setalt utility to set the interface before printing here. LPT1USB.SYS and PRNUSB.SYS are loaded with a device= statement in the config.sys file or with the DEVLOAD utility. Load DosUSB then, do not use the /L command line option here! The default device address is one, the default device endpoint is two. Use the command line options e.g. /D2 /E1 to select device address two and endpoint number one. Use USBView to determine the right settings for your printer. These drivers cannot be used with low cost GDI printers, since these do not accept ASCII code for printing. They expect data which controls their print head directly. This protocol is vendor specific and usually not available. If a printer accepts ASCII code via its parallel interface, it usually can also do this via its USB interface. Use type dosusb.txt lpt1 or type dosusb.txt prnusb to print the file dosusb.txt from the DOS prompt. Or open lpt1 or prnusb as a file in your application program Michael Potter-4 wrote: Hi, I have googled and googled and googled this question and have not found an easy answer. That is strange because this seems like something that would be a common problem. I have an old DBase application that I am reviving to run under FreeDOS. It prints to a parallel printer when running on real hw, but when running in FreeDOS in VirtualBox I want it to print to a USB printer. What is the best way to do that? The printer shows up in the Devices-USB menu in Virtual box. Here is the advise I received from a friend how to do it under DOS running within XP: a) Setup the printer in Windows, then SHARE the printer. Then in DOS, one can do this: b) NET USE lpt1: \\windowspc\printershare What would be the equivalent of that in FreeDOS? -- Michael Potter -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
I'm assuming that this driver won't work if I'm using a USB card in my laptop pcmcia slot? --- On Thu, 7/16/09, Alain Mouette ala...@pobox.com wrote: From: Alain Mouette ala...@pobox.com Subject: Re: [Freedos-user] printing to USB To: freedos-user@lists.sourceforge.net Date: Thursday, July 16, 2009, 12:19 PM Hi, In fact this (http://www.georgpotthast.de/usb) is a full USB driver for DOS, with both UHCI and OHCI. It has drivers for Parlel and Serial devices, plus pendrive. Unfortunately it is only free for personal use... Alain iw2evk escreveu: For solve the problem you can download the free software dosusb http://www.georgpotthast.de/usb/dosusb.zip in the package are insert some utlities for printing via usb port on DOS see for documentation : 3.1 Printer driver There are two printer drivers available. LPT1USB.SYS installs as a LPT1: device while PRNUSB.SYS installs as the PRNUSB: device. So you with the latter driver you can use LPT1: for other printers if needed, while with LPT1USB.SYS you can print from the DOS Editor or other application programs directly. Both are printer device drivers which use DosUSB to print to USB printers. They will work with a HP 2420d Laserprinter, a HP 880C, a HP 5940 and a HP 460C inkjet printer. They will also work with parallel to USB adapters. Check the endpoints and use the setalt utility to set the interface before printing here. LPT1USB.SYS and PRNUSB.SYS are loaded with a device= statement in the config.sys file or with the DEVLOAD utility. Load DosUSB then, do not use the /L command line option here! The default device address is one, the default device endpoint is two. Use the command line options e.g. /D2 /E1 to select device address two and endpoint number one. Use USBView to determine the right settings for your printer. These drivers cannot be used with low cost GDI printers, since these do not accept ASCII code for printing. They expect data which controls their print head directly. This protocol is vendor specific and usually not available. If a printer accepts ASCII code via its parallel interface, it usually can also do this via its USB interface. Use type dosusb.txt lpt1 or type dosusb.txt prnusb to print the file dosusb.txt from the DOS prompt. Or open lpt1 or prnusb as a file in your application program Michael Potter-4 wrote: Hi, I have googled and googled and googled this question and have not found an easy answer. That is strange because this seems like something that would be a common problem. I have an old DBase application that I am reviving to run under FreeDOS. It prints to a parallel printer when running on real hw, but when running in FreeDOS in VirtualBox I want it to print to a USB printer. What is the best way to do that? The printer shows up in the Devices-USB menu in Virtual box. Here is the advise I received from a friend how to do it under DOS running within XP: a) Setup the printer in Windows, then SHARE the printer. Then in DOS, one can do this: b) NET USE lpt1: \\windowspc\printershare What would be the equivalent of that in FreeDOS? -- Michael Potter -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos
Re: [Freedos-user] printing to USB
On Thu, 16 Jul 2009 15:19:33 -0300, you wrote: Hi, Unfortunately it is only free for personal use... Too bad, it's coded in BASIC, also it's not free. Jack did thinking of a small and beautiful USB driver for DOS (with BIOS call), but he have no sample code (I don't think Intel will have sample code in assembly). And information (how to code for EHCI or UHCI ... just drop the OHCI, it's slow and outdated). If anyone can help to gather these information, please update me. Rgds, Johnson. -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
Michael Potter escreveu: Here is the advise I received from a friend how to do it under DOS running within XP: a) Setup the printer in Windows, then SHARE the printer. Then in DOS, one can do this: b) NET USE lpt1: \\windowspc\printershare That is good advice for freedos too... but not easy :( NET USE is part of a package Microsoft client, which you can use in FreeDOS. BUT you will need an emulator that has a NIC, VMware, Qemu and VirtualPC have. Then you will need MSClient. Either you find one and fight to install it, or you install from netbootdisk.com which is that with auto intalation. It is not easy, but it works. I know for sure. I have done it. I can help, step by step.. on one condition: you will have to document it and put it anywhere in the web. Alain -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
