Re: [Freedos-user] Print via network
I hate to even suggest this, but are you using the /B option on the file copy to indicate that a binary copy is needed? Otherwise, the first Ctrl-Z in the file will end the file copy prematurely. On Wed, Jun 16, 2021 at 3:37 PM Frantisek Rysanek wrote: > Dear gentlemen, > > on and off, with Bryan we've been playing with Ubuntu, Samba, CUPS > and the MS Network Client running in FreeDOS. And we're facing a dead > end - same symptoms observed by me and by Bryan: > > We can load the MS stack, to the point that we can "net use" network > disk volumes = map a local drive letter to an ARC path from the > server. And the disk is perfectly accessible. > > But, printing is giving us an interesting misbehavior. > We can ask for > net use LPT2: \\server\printqueue > That does succeed. But, whatever we copy to the redirected LPT2 > (we've also tried LPT1 for that matter), we only get a couple lines > printed. Like 4 to 6 lines, if we try to print plain text. > > I've observed the problem with Wireshark. The MS client connects a > TCP session to Samba, they negotiate the protocol version, the client > starts a print request, sends the first packet with an actual > payload, gets a TCP ACK, and the very next TCP packet from the client > to the server has a FIN flag - and the TCP session get gracefully > ended. Interestingly, the client produces one extra packet with an > ACK for the session, after the FIN / FIN+ACK coordinated handshake > has closed the session. Wireshark's TCP tracing marks that extra ACK > packet as a duplicate... > > I have no clue why this is happening. I've tried loading all the > drivers "low" (instead of "high" or UMB). No joy. > > I'm wondering, which of the bunch of drivers and executables (about 8 > of them) is specifically responsible for the printer port redirection > function. And, what could make it close the TCP session prematurely. > Does it perhaps expect a different "pattern of data writes" on the > hooked LPT port service? Which a plain "copy" command does not > satisfy? > > Any ideas are welcome :-) > > Frank > > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Print via network
Dear gentlemen, on and off, with Bryan we've been playing with Ubuntu, Samba, CUPS and the MS Network Client running in FreeDOS. And we're facing a dead end - same symptoms observed by me and by Bryan: We can load the MS stack, to the point that we can "net use" network disk volumes = map a local drive letter to an ARC path from the server. And the disk is perfectly accessible. But, printing is giving us an interesting misbehavior. We can ask for net use LPT2: \\server\printqueue That does succeed. But, whatever we copy to the redirected LPT2 (we've also tried LPT1 for that matter), we only get a couple lines printed. Like 4 to 6 lines, if we try to print plain text. I've observed the problem with Wireshark. The MS client connects a TCP session to Samba, they negotiate the protocol version, the client starts a print request, sends the first packet with an actual payload, gets a TCP ACK, and the very next TCP packet from the client to the server has a FIN flag - and the TCP session get gracefully ended. Interestingly, the client produces one extra packet with an ACK for the session, after the FIN / FIN+ACK coordinated handshake has closed the session. Wireshark's TCP tracing marks that extra ACK packet as a duplicate... I have no clue why this is happening. I've tried loading all the drivers "low" (instead of "high" or UMB). No joy. I'm wondering, which of the bunch of drivers and executables (about 8 of them) is specifically responsible for the printer port redirection function. And, what could make it close the TCP session prematurely. Does it perhaps expect a different "pattern of data writes" on the hooked LPT port service? Which a plain "copy" command does not satisfy? Any ideas are welcome :-) Frank ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Catching up on FreeDOS articles at OpenSource.com
Hello. Freedos is a the alternative to MS-DOS/PC-DOS in a modern computer and also old or older computer. There are some will use Freedos to run some program and other for games. The problem, for me is hardware. Sure i have some old hardware, i don't discard old stuff unless is trash/damaged beyond repair. I have a EEE PC with windows xp and last year i deleted windows xp and installed Freedos 1.2 and i'm sure i did some thing wrong because i end up with 2gb partions. The first limitation i encountered was how to copy games, usb pendrive 2.0, no support for usb 3 and then i ran a game and for stupid face no sound... speaker/sound blaster. My solution was very simple, u ran Dosbox-X for DOS so that i can have sound on games. You don't need sound to run wordperfect or lotus 123. So Freedos is good but the user is dependent on hardware. On Wed, Jun 16, 2021 at 9:13 AM Bryan Kilgallin wrote: > Thanks, Jim: > > > > > Q: What are the advantages of using FreeDOS over alternative ways of > > running DOS applications (e.g., DOSBox)? > > A: Using DOSBox to run DOS applications in Linux is a great way to run > > certain DOS applications. But DOSBox is really intended to launch a > > single DOS program, like a game. The DOS command line is pretty > > limited in DOSBox. In contrast, FreeDOS provides a full DOS command > > line. > > My Polar Sport Tester PE4000 software just wouldn't work properly under > emulation. I couldn't get a USB serial link to go! So I was unable to > upload heart rate data to a more modern PC. But I have a working 32 bit > PC with a built-in hardware serial port! And that works fine with the > Polar DOS software. > > > > Q: Why work on DOS in 2021? > > A: [I talk about a few things, but mostly about how programming in DOS > > is not the same as programming on Linux. You can't just "load > > everything into memory" because you don't have a lot of memory to use, > > ... and that makes programming more challenging and interesting.] > > I thought that I would keep my brain alive! > > > > Q: How big is the FreeDOS community? > > A: FreeDOS was a very popular project throughout the 1990s and into > > the early 2000s, but the community isn’t as big these days. But it’s > > great that we are still an engaged and active group. > > I have especially appreciated detailed help from Europe! > > [I also mention > > the virtual get-togethers.] > > > > Q: How does someone get involved in the community? > > A: I think our community is very welcoming, so anyone is free to join. > > We communicate via an email list, which you can find on the FreeDOS > > website. Join the freedos-user email list if you want to talk about > > FreeDOS or ask for help. > > I greatly appreciate this welcoming and helpful character. > -- > members.iinet.net.au/~kilgallin/ > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [Freedos-devel] game protections (was: Tracking bug s...)
> I think it would be easier for both the game owners > and me to let me help them to break some individual > features in copies of their OAKCDROM (UPC, subchannel) > and then ask them whether it made their game fail. > > That way, I only have to send a debug script or file > to modify their OAKCDROM driver and no physical game > CD or DVD have to be sent around. > > When we know which of the 2 features (or maybe others) > are relevant for the copy protection, only then can > we start thinking about implementing those features. I would take the opposite approach. I would start by adding the standard features we know are missing in Jack's drivers and see if it fixes anything. Those features should be there anyway, and (at least to me) it doesn't really matter if they are actually used by existing applications or not. If that doesn't fix the copy protection then some further investigation would be required. You can either do this by breaking things or by monitoring the calls that get sent to the device driver. I admit it would be kind of nice to know how the copy protection works, if for no other reason than to try and avoid something like this again in the future. I think the first thing to do is fix Jack's driver to make it a 100% driver, not try to figure out ahead of time whether making it a 95% or 100% driver will fix a specific problem. As you've also pointed out with the DOSBox code, sometimes there's enough ambiguity in the different specs (like the between the SCSI commands and the MSCDEX spec) that it's not always clear what the correlation is. For example, "Audio Sub-channel" vs. "Audio Q-channel" -- I'm not 100% sure what the difference is and the existence of the sub-channels isn't related to whether the CD contains audio or not. It could be that Jack's implementation of one of the (supposedly) working IOCTL calls is somehow faulty in some respect and is returning incorrect data. I doubt that's the case, but it could be. I know I get confused when reading the different specs and looking at specific implementation code from others and wondering if they really did it correctly or not. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [Freedos-devel] game protections (was: Tracking bugs...)
Hi Tom, > may be Paul can be convinced to send you one of these failing games, Paul? I thought Lukas? Anybody with a game which does fail with UDVD2 and works with OAKCDROM is welcome to help with this question. I suggest to move this thread to freedos-user :-) > or better several games as they might use different copy protection > methods. possibly the worst/least missed ones as long as they fail > (and work in OAKCDROM). I think it would be easier for both the game owners and me to let me help them to break some individual features in copies of their OAKCDROM (UPC, subchannel) and then ask them whether it made their game fail. That way, I only have to send a debug script or file to modify their OAKCDROM driver and no physical game CD or DVD have to be sent around. When we know which of the 2 features (or maybe others) are relevant for the copy protection, only then can we start thinking about implementing those features. Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Catching up on FreeDOS articles at OpenSource.com
Thanks, Jim: Q: What are the advantages of using FreeDOS over alternative ways of running DOS applications (e.g., DOSBox)? A: Using DOSBox to run DOS applications in Linux is a great way to run certain DOS applications. But DOSBox is really intended to launch a single DOS program, like a game. The DOS command line is pretty limited in DOSBox. In contrast, FreeDOS provides a full DOS command line. My Polar Sport Tester PE4000 software just wouldn't work properly under emulation. I couldn't get a USB serial link to go! So I was unable to upload heart rate data to a more modern PC. But I have a working 32 bit PC with a built-in hardware serial port! And that works fine with the Polar DOS software. Q: Why work on DOS in 2021? A: [I talk about a few things, but mostly about how programming in DOS is not the same as programming on Linux. You can't just "load everything into memory" because you don't have a lot of memory to use, ... and that makes programming more challenging and interesting.] I thought that I would keep my brain alive! Q: How big is the FreeDOS community? A: FreeDOS was a very popular project throughout the 1990s and into the early 2000s, but the community isn’t as big these days. But it’s great that we are still an engaged and active group. I have especially appreciated detailed help from Europe! [I also mention the virtual get-togethers.] Q: How does someone get involved in the community? A: I think our community is very welcoming, so anyone is free to join. We communicate via an email list, which you can find on the FreeDOS website. Join the freedos-user email list if you want to talk about FreeDOS or ask for help. I greatly appreciate this welcoming and helpful character. -- members.iinet.net.au/~kilgallin/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Catching up on FreeDOS articles at OpenSource.com
Hi Jim: How to copy files between Linux and FreeDOS František (Frank) has been helping me with a project. That is printing from FreeDOS via Ubuntu. -- members.iinet.net.au/~kilgallin/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
