Re: [Freedos-devel] Testing evaluating the 1.1 release
On 7/15/2011 11:33 AM, Bernd Blaauw wrote: Op 15-7-2011 5:08, Michael B. Brutman schreef: - How do I use the new installer that Jim has been working on? It's in the new ISO that I plan to upload by Sunday evening. Still need to work out some things to make it a smoother experience. The initial menu showing which CD drives were found for example (which I also should add plain directories to, but that's more difficult). Good - I await the next revision. I'm trying to do my part here by testing it .. - Are all of the binaries always put into the one bin dir? I expected the optional packages to be separated into subdirectories, not lumped in with the critical OS commands. All is together. Nothing is preventing an additional directory called EXTRA, putting subdirectory PACKAGES below it and a BASE directory below that, and then install from that location, allowing a 2nd directory. The following is just a matter of personal preference and/or opinion .. On all of my machines (DOS, Windows and Unix) I try to keep the optional packages separate from the core OS functions. So DOS will live in /DOS and nothing else will be in that directory. Smaller utilities wind up in something like /utils/text, /utils/disk, /utils/zip, etc. If something has a lot of files that deserves it's own directory. mTCP usually lives in /mtcp or /packet/mtcp depending on what other networking code I have installed. I can see where DHCP, FTP, PING, SNTP, and TELNET could be considered core OS functions so I'm not entirely opposed. It's just different than what I'm used to seeing, not just on DOS. - I noticed the PCNet packet driver, which was a happy coincidence because I was installing under VMWare. Has their been any thought to including other common packet drivers? FreeDOS 1.0 has lots of packet drivers, I didn't include them so far to keep the CD minimalistic. Rebuilding for every change on batchfiles can be a pain :) Does this mean that they will be put on the CD later, or that the user has to find a different way to get them on the machine? I think that every packet driver known to man probably fits within 1MB of space. :-) (Ok, maybe 2 ...) Is the intent of the CD to provide a minimal install? - Did I miss the option to install the WATTCP based programs? See above, minimising things. WATTCP programs are usually compiled as DJGPP programs, having kind of huge disk footprint compared to your drivers for example. Same question as above - the capacity of a CD is quite large, and 12MB for an OS install image is tiny. As an end user I would much prefer that what I need is on the CD already even if it means a larger download size. (Or give me a choice of ISO images to use.) I'm new to this, so if this is already addressed in some way then forgive me and just point me on my way ... - Do I have time to do a minimal mTCP configuration program that can be used to walk users through setting up the configuration file? Ofcourse, knock yourself out :) I noticed the problem with the improper CR/LF in the mTCP configuration file that you reported a week or two ago, and I assume that we can just fix the original file. Depending on your time table I can either fix DHCP to be more tolerant of improper new lines in files or I can try to do something more comprehensive that looks like an installer. In a perfect world the installer would just prompt for a few things like the IRC user name, FTP buffer sizes, MTU size, etc. If that doesn't happen in time having those fields in the mTCP config file (but commented out as I do in the sample) would be a reasonable substitute. BTW, I'm happy/honored to be part of the group. I just want to ensure that the mTCP code looks/behaves more like the OS so that it doesn't cause usability problems or stick out too much. It's not a full networking stack, but the idea of a coherent set of networking utilities available at install time with the OS is very appealing. Mike -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Updates to software list
Based on discussions with Bernd as we prepare for FreeDOS 1.1, I've done some cleanup on the Software List. The major edits: * COUNTRY: edited to reflect that it is part of KERNEL * DOSFSCK: moved Util - Base * DEVLOAD: moved Util - Base * EMM386: deleted (replaced by JEMM386) * FDSHIELD: moved Base - Util (similar to FDAV, which is already in Util) * HIMEM: deleted (use HIMEMX) * KERNELDEV deleted (use KERNEL) * MTCP: added to Net * UIDE: added to Base (removed GCDROM) * VOL: edited to reflect that is is part of COMMAND * XMGR: added to Base (removed FDXMS, FDXMS286) Please have a look and let me know if I need to update anything else.http://www.freedos.org/software/ Keeping the software list up-to-date is a community effort. If you see anything there that looks out of place, or out of date, etc please let me know. Just send me an email and I'll update it. We use an online tool to edit the software list via a web browser, and several admin folks have the ability to update the software list in this way. You can also contact Pat, Aitor, Eric, Rugxulo, Mateusz, or Jeremy. -jh -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Updates to software list
Op 16-7-2011 19:44, Jim Hall schreef: * XMGR: added to Base (removed FDXMS, FDXMS286) I'd keep FDXMS286 if possible, it's the only XMS-driver for 286 machines. Please have a look and let me know if I need to update anything else.http://www.freedos.org/software/ UTIL: you could delete UDMA, XCDROM, XDMA from the software list so people won't download them again except directly from Ibiblio if they happen to stumble upon it. Jack R Ellis opensourced those drivers back then, but all have been replaced by a much more bugfree and functional UIDE driver, acting as CD driver for SATA/IDE drives, meanwhile also providing readcache for IDE/SATA harddisks and those CD drives. Keeping the software list up-to-date is a community effort. If you see anything there that looks out of place, or out of date, etc please let me know. Just send me an email and I'll update it. I'd suggest adding Syslinux (4.04) to the BOOT section, due to its capabilities and the now opensourced ELTORITO driver. Flashrom program could be added as well to UTIL, but it's a dangerous program to mess around with. BIOS chip with wrong contents -- no functioning computer. We use an online tool to edit the software list via a web browser, and several admin folks have the ability to update the software list in this way. You can also contact Pat, Aitor, Eric, Rugxulo, Mateusz, or Jeremy. Mirroring to Ibiblio has to improve still, might want to doublecheck that. Kernel, SHSUCDX and Edlin (what's a binary?) are easy examples of being outdated. Anyone got experience with the watcom port of FreeCOM yet? Or too experimental / work-in-progress? Bernd -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Updates to software list
On Sat, Jul 16, 2011 at 1:07 PM, Bernd Blaauw bbla...@home.nl wrote: Op 16-7-2011 19:44, Jim Hall schreef: * XMGR: added to Base (removed FDXMS, FDXMS286) I'd keep FDXMS286 if possible, it's the only XMS-driver for 286 machines. Ok, I restored FDXMS286 back on the software list (Base). Please have a look and let me know if I need to update anything else.http://www.freedos.org/software/ UTIL: you could delete UDMA, XCDROM, XDMA from the software list so people won't download them again except directly from Ibiblio if they happen to stumble upon it. Jack R Ellis opensourced those drivers back then, but all have been replaced by a much more bugfree and functional UIDE driver, acting as CD driver for SATA/IDE drives, meanwhile also providing readcache for IDE/SATA harddisks and those CD drives. Thanks, forgot to clean those up. I've removed UDMA/UDMA/XCDROM from the software list. Keeping the software list up-to-date is a community effort. If you see anything there that looks out of place, or out of date, etc please let me know. Just send me an email and I'll update it. I'd suggest adding Syslinux (4.04) to the BOOT section, due to its capabilities and the now opensourced ELTORITO driver. Done! Also mirrored 4.04 to ibiblio. Flashrom program could be added as well to UTIL, but it's a dangerous program to mess around with. BIOS chip with wrong contents -- no functioning computer. I don't want to include this in the software list just yet. It's a very specific tool for a very specific purpose. Let's leave off for 1.1. Mirroring to Ibiblio has to improve still, might want to doublecheck that. Kernel, SHSUCDX and Edlin (what's a binary?) are easy examples of being outdated. Yes, this seems to have been (mostly) ignored while I was away from FreeDOS. Some things were updated, but most items were not. This is next on my to-do list, when I'm not writing updates for Install, or goofing off on the weekend. :-) -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Testing evaluating the 1.1 release
Op 16-7-2011 16:30, Michael B. Brutman schreef: Good - I await the next revision. I'm trying to do my part here by testing it .. great, thanks. On all of my machines (DOS, Windows and Unix) I try to keep the optional packages separate from the core OS functions. So DOS will live in /DOS and nothing else will be in that directory. That's fine. Rather than adding loads of programs in a single directory, I'll probably add an option to the setup batchfiles to provide a directory from which you can add EXTRA files through the FreeDOS installer (requiring PACKAGES\BASE subdirectory). Perhaps call it EXTRA or CUSTOM. So: \ \FREEDOS \FREEDOS\PACKAGES \FREEDOS\PACKAGES\BASE\*.ZIP but also \FREEDOS\EXTRA\PACKAGES\BASE Does this mean that they will be put on the CD later, or that the user has to find a different way to get them on the machine? I think that every packet driver known to man probably fits within 1MB of space. :-) (Ok, maybe 2 ...) I'll add packet drivers again, and VMware is my test platform (besides real hardware at times). The more difficult part is understanding the network-related scripts Jeremy wrote (PCISLEEP/PCISCAN) and extracting the correct packet driver and options to be added to autoexec.bat (plus setting up configuration files mtcp.cfg/wattcp.cfg). A very simple bootdisk with all packet drivers and your MTCP programs would be cool. You've got a networked 8088..which capacities/sizes do your floppies have, how much available harddiskspace? As no XMS, no Ramdisk for storing downloads, thus will have to use harddisk space temporarily. Just a demo bootdisk + tiny ISO. Is the intent of the CD to provide a minimal install? My current intent is to get a decent base working, then adding everything else. I've got nothing automated, so minimizing things at first. FreeDOS 1.0 has several sized versions available at: ftp://ftp.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/ Some might argue even 10MB or so is already huge when all basic content fits on a bootdisk (fdisk/format/sys/kernel/shell) Same question as above - the capacity of a CD is quite large, and 12MB for an OS install image is tiny. As an end user I would much prefer that what I need is on the CD already even if it means a larger download size. (Or give me a choice of ISO images to use.) You'll get that choice. See above link though it uses the 1.0 distro. With unlimited time, no download limits, enough free diskspace etc a huge FreeDOS distro is fine, if intended to burn to optical disk anyway. However the minimal base-only CD should be as small as possible for fast downloads and limited harddisk space. I'm new to this, so if this is already addressed in some way then forgive me and just point me on my way ... All discussion is welcomed, I'd better speed up releasing more though to prevent arguing over the same topics/issues over and over :) I noticed the problem with the improper CR/LF in the mTCP configuration file that you reported a week or two ago, and I assume that we can just fix the original file. Depending on your time table I can either fix DHCP to be more tolerant of improper new lines in files or I can try to do something more comprehensive that looks like an installer. In a perfect world the installer would just prompt for a few things like the IRC user name, FTP buffer sizes, MTU size, etc. If that doesn't happen in time having those fields in the mTCP config file (but commented out as I do in the sample) would be a reasonable substitute. I'll need to look into your sample to see what the syntax for commented out stuff is, be it ; (config.sys), # , # (syslinux), or anything else (like ignoring anything not recognised). BTW, I'm happy/honored to be part of the group. I just want to ensure that the mTCP code looks/behaves more like the OS so that it doesn't cause usability problems or stick out too much. It's not a full networking stack, but the idea of a coherent set of networking utilities available at install time with the OS is very appealing. I think FDUPDATE is fully depending on WGET and/or CURL, both with their respective (and or generic URL) syntax. Your download program currently depends on real FTP-script-syntax instead of URLs. In due time there might be a MTCP WGET, who knows. Just as a remark: Making something opensource is good but unfortunately can't always expect more people to help improve things. Many FreeDOS programs are experiencing this issue. If we integrate MTCP properly in FD1.1 your software might inspire people to write more networking programs based on your stack. Something to be proud of, hehe :) -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas
[Freedos-devel] provox dos screen reader
The provox screen reader for dos which I would like to have added to the freedos ftp site is currently located at: http://www.thesiegelsnest.us/provox/provox7.zip I don't (currently) have access to my other computer where I modified the documentation, and created a .lsm file. I will have this in a couple weeks. The program was put under the gpl, and I had contacted the original author some time ago asking permission to try to get it included in the freedos distribution, as well as take over development. Both requests were granted, and now that I have a sourceforge developer account, I'll likely upload the program there for initial distribution, after I get back to the machine with the modifications on it. The program currently only works with hardware synthesizers (since there weren't any software synths for dos. However, since finding one of these devices is relatively easy, since most folks who have them no longer use them with a few exceptions such as myself and a couple others I'm aware of, this shouldn't be a show stopper. If a software synth could be developed, provox could easily be extended to support such a synth, though I doubt such a program would be useful, because of the amount of memory it would require, and under dos, that's generally not practical. So, If there are any other folks on list who use screen readers under dos, feel free to grab this one and give it a try. Adding additional synths is (relatively) simple, so if anyone has one that isn't supported other than artic synths, I'm already working on those, I'd be happy to try to add them. Of course, artic synths can already be made to work by using either the porttalk or accent sa options, but both modes lack some useful features supported directly by the artic synthesizers themselves. Included with this zip file is the a86 assembler used to compile the code, which obviously would need to be removed for the freedos distribution copy, since it's a completely separate application. Otherwise, it's ready to go, and can be added at any time after I get my version with updated docs and lsm file off the other machine. hth. -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Testing evaluating the 1.1 release
Hi, On 7/16/11, Bernd Blaauw bbla...@home.nl wrote: Op 16-7-2011 16:30, Michael B. Brutman schreef: Does this mean that they will be put on the CD later, or that the user has to find a different way to get them on the machine? I think that every packet driver known to man probably fits within 1MB of space. :-) (Ok, maybe 2 ...) I'll add packet drivers again, and VMware is my test platform (besides real hardware at times). So VMware needs PCNET? VirtualBox needs AMDPD? QEMU needs NE2000? Anybody know BOCHS? (Yes, I'm assuming more re: emulation than real hardware here, isn't that reasonable?) Some might argue even 10MB or so is already huge when all basic content fits on a bootdisk (fdisk/format/sys/kernel/shell) Well, what exactly can you do with kernel + shell? Not much! At least throw a compiler, a text editor, a game, *something useful*, in there! ;-) Most attractive to average users (rough guess): Mpxplay Bret's USB CuteMouse mTCP + common packet drivers Arachne WGET Mined GNU Emacs Perl Python OpenGem OpenWatcom + NASM FreeDoom + Eternity Engine HXRT + HXGUI p7zip DJGPP (GCC + GPP + Watt-32) UIDE + XMGR + RDISK + SHCDX33E DOSLFN Odi's LFNtools LTOOLS TestDisk + PhotoRec xpdf (or Ghostscript?) Doszip (or DN/2?) 4DOS (or Bash?) Keyb + CPI (+ mode + nlsfunc), etc. etc. Unsurprisingly, most of this was already included in 1.0 (older versions, natch). Of course, a CD has tons of space, so to speak, so you can afford to waste, heh, unlike floppies *sniff*. You'll get that choice. See above link though it uses the 1.0 distro. With unlimited time, no download limits, enough free diskspace etc a huge FreeDOS distro is fine, if intended to burn to optical disk anyway. However the minimal base-only CD should be as small as possible for fast downloads and limited harddisk space. Yes, minimal is (sometimes) good, but full with everything and the kitchen sink wouldn't fit on a CD anyways. And we'd argue to death over what to cram anyways. Jim has been pretty open to people making their own distros. So far not many have bothered. It's tedious, that's probably why. The only thing worse than that is annoying bugs or stuff that constantly gets updated (which means upgrading ad nauseum). Perfectionism doesn't help either (not that anything is every perfect). :-/ I think FDUPDATE is fully depending on WGET and/or CURL, both with their respective (and or generic URL) syntax. Your download program currently depends on real FTP-script-syntax instead of URLs. In due time there might be a MTCP WGET, who knows. There's an easy (obvious?) answer to that: include common packet drivers (see above), and let mTCP's FTP grab WGET itself from iBiblio! Bam, problem solved! ;-) Of course, they need a way to find what they want. So someone either has to make a VERY long list in .txt or else we have to give them some sort of web browser (presumably Arachne, which isn't perfect but good enough). If we integrate MTCP properly in FD1.1 your software might inspire people to write more networking programs based on your stack. Something to be proud of, hehe :) Somebody always comes out with something awesome (DOS-related) and surprises us all. There are so many good authors out there. Bernd, I don't envy your having to thank them all !!! ;-)) Yeah, maybe I'll make a list of them (alphabetically), heheh, gimme six months -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] provox dos screen reader
Hi, On 7/16/11, Travis Siegel tsie...@softcon.com wrote: The provox screen reader for dos which I would like to have added to the freedos ftp site is currently located at: http://www.thesiegelsnest.us/provox/provox7.zip Looks good so far. So, If there are any other folks on list who use screen readers under dos, feel free to grab this one and give it a try. IIRC, there were two or three around here. The only name that comes to mind is Jude DeShell (sp?). But I'd have to dig up his e-mail (if you really really wanted). I assume he can find out by himself. Included with this zip file is the a86 assembler used to compile the code, which obviously would need to be removed for the freedos distribution copy, since it's a completely separate application. Just for the record, A86 is shareware, so in theory it's fine including it (though obviously NASM would be better). Of course, I find it funny that you use an ancient copy (3.22 from 1990!) when even latest 4.05 has been stable for 10 years!! ;-)I assume there's no hard dependency on that particular version. Oh well, it doesn't matter right now, I just find it funny. ;-) -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Updates to software list
Hi, On 7/16/11, Jim Hall jh...@freedos.org wrote: Based on discussions with Bernd as we prepare for FreeDOS 1.1, I've done some cleanup on the Software List. The major edits: * DOSFSCK: moved Util - Base While I agree this is better, it's still nice to have CHKDSK for 16-bit cpus (since DOSFSCK is DJGPP / 386+). * HIMEM: deleted (use HIMEMX) * XMGR: added to Base (removed FDXMS, FDXMS286) Was this intentional? We don't need two (though it's nice to have both in case one has bugs with something). These days I tend to prefer XMGR. HIMEMX (AFAICT) has no maintainer (and/or we really need to push out that jmp $+2 fix for old 386s, i.e. unofficial version 3.33, been procrastinating that for years!). Please have a look and let me know if I need to update anything else.http://www.freedos.org/software/ To be completely honest, please don't take this the wrong way, but some of those I literally never use (or can't remember how!): * append * assign * comp * choice * edit (but do keep this, I guess, though I prefer others) * exe2bin (really? anybody use that? then where's link? heh) * fasthelp (does this even do anything?) * graphics (apparently my hardware hates it) * lbacache (still good but UIDE makes it and TICKLE and CDRCACHE redundant) * mirror * nlsfunc (broken with 2040??) * print (doesn't work for me) * recover * share * tree * undelete (FAT32 buggy?) * unformat Something I would maybe? add is whats-his-face's Restore, but it's for non-military use, heh, aka not GPL friendly. Then again, that's another rare util I don't personally need. But it's classic BASE, IMHO. I mean, if we want to mirror MS-DOS, we should include BWBasic (or Regina Rexx for similarity to PC-DOS). But I don't figure anybody would agree to that. Heck, if you want to be different, include XPL0 !!;-) Almost forgot, yeah, I would (personally) add sed, specifically cheap sed, which already is GPL and has a DOS 16-bit binary: http://lvogel.free.fr/sed.htm It's basically a cleaned up version of hhsed which was derived from Eric Raymond's version. I also see that even ESR now only points to (other dude's) minised as the proper replacement. Surprisingly, it's still dead simple (!) to compile that (and I tested with DJGPP yesterday), but I haven't built it with OpenWatcom, so I don't know if it's 16-bit friendly. http://www.exactcode.de/site/open_source/minised/ Perhaps we should include Awk (old Mawk 1.2.2? old 16-bit Gawk 3.0.6?) instead? Or maybe you think that's too *nix-y? I don't even grok Awk (heh), just saying, it's at least as useful as sed (though I heavily use sed almost exclusively). Oh, I forgot, one guy tweaked BWK's Awk a few months ago to compile with OW (even for DOS 16-bit). So that would be a good alternative too, if you prefer a more recent (and hopefully less buggy) version. http://www.gknw.net/mirror/awk/ Keeping the software list up-to-date is a community effort. If you see anything there that looks out of place, or out of date, etc please let me know. Just send me an email and I'll update it. I guess I'm one of the updating fiends. But even I've slowed down (somewhat, stupid computer problems). It's hard to find everything, even harder to keep track of versions, what works, what doesn't, etc. We use an online tool to edit the software list via a web browser, and several admin folks have the ability to update the software list in this way. You can also contact Pat, Aitor, Eric, Rugxulo, Mateusz, or Jeremy. No offense, but most of this stuff is unmaintained. In fact, that reminds me, MOVE still needs the +R bug fixed. (And a lot of these should be upgraded to support LFNs, for DOSEMU if nothing else.) Ah well, always more to do. :-/ P.S. I know we're all tired of having to do everything ourselves and also tired of waiting for 1.1 to finally come out. But hey, that's life, everybody's off doing ten different other projects too, even me (barely). Oh well, if we just do a little at a time, we'll get there one day -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Updates to software list
Hi, On 7/16/11, Bernd Blaauw bbla...@home.nl wrote: Anyone got experience with the watcom port of FreeCOM yet? Or too experimental / work-in-progress? Bart said it works pretty well, but it's only in SVN (and I don't have a client installed on this machine), so you'll have to grab and build it by yourself. -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Updates to software list
Hi, On 7/16/11, Jim Hall jh...@freedos.org wrote: Mirroring to Ibiblio has to improve still, might want to doublecheck that. Kernel, SHSUCDX and Edlin (what's a binary?) are easy examples of being outdated. Yes, this seems to have been (mostly) ignored while I was away from FreeDOS. Some things were updated, but most items were not. This is next on my to-do list, when I'm not writing updates for Install, or goofing off on the weekend. :-) I did a few updates a month or two ago. But my mistake was blindly assuming that Murphy's Law didn't exist. (Nah, why have ssh key on two computers? This one is brand new. What could go wrong?) Worse is that then I assumed my laptop would work fine ... and while it does, the router doesn't (or at least I haven't barely a clue how to set it up, yet again, and I have to pore over some Dummies books [literally!] one of these days to figure it out!) So unless I want to beg Jim, yet again, to install *yet another* ssh key for me for this computer (not that I have any decent ssh tools, would have to *yet again* install Cygwin), it's not going to happen until I become router-savvy (ugh). And even I (barely) have a life with other junk to do (barely!). Face it, Jim has done a lot for FreeDOS, maybe too much, so when he runs off with real life, sometimes nobody steps up. Hey, they've (almost all) got the real life disease too! Well, ssh, it happens. ;-) -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
