Re: [Freedos-devel] Working on FreeDOS 1.2 - iso sizes and diskimage mounts
Hi, On Fri, Jan 9, 2015 at 5:16 PM, Eric Auer e.a...@jpberlin.de wrote: PS: Dropping the image mount sub-topic again, pending Rugxulo's reply. I'm not sure exactly what you want here. I don't know of any (obvious) The question (in another thread) was if there was a disk image backed mountable drive driver which supports writing back changes to disk. I only know that the SHSUCD suite has a disk image backed read-only ISO (CD/DVD) image mount driver. The idea in the other thread was to add encryption between mounted drive and disk image, allowing several DOS users to share one computer but not see each other's data, decrypting only the home disk of the current user each time. Of course this is assuming that they are polite enough to not delete each other's disk. I'm not aware of any drivers. Any such users will have to find and use encryption manually. Or maybe just do something else like hide logical drive (extended partition?) via boot manager (with password). -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. www.gigenet.com ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
Hi all, 2015-01-02 15:15 GMT+01:00 Jim Hall jh...@freedos.org: I haven't tried putting the FreeDOS 1.1 installer on a USB fob drive, but it would probably work if the ISO image was written using liveusb-creator. https://fedorahosted.org/liveusb-creator/ I use this to every time I upgrade Linux on my laptop, because my laptop doesn't have a CDROM drive. It's great! I tried Fedora's LiveUSB-Creator, but after fixing checking MD5 sum it reports: Unable to find LiveOS on ISO. In this case it was fd11src.iso. What's working is Rufus (https://rufus.akeo.ie/). I am able to boot the laptop but I cannot install FreeDOS because the installer recognizes the harddisk as drive D: and the USB stick as drive C:. First I tried to create drive C: The USB stick is here drive C: with 2 Gigs, the harddisk has 500 MB: I changed the primary DOS partition to D: And set this drive to active: But when I now try to install FreeDOS 1.1 to harddisk the installer chooses drive C: the USB stick: I cannot install to harddisk from USB stick with the current installer. Or am I to stupid? If I am right, maybe we can fix this in the next installer? Maybe with a new entry in isolinux.cfg? Maybe it is possible to create an option in the live mode, which is currently hidden, like this? --- label live menu label Use FreeDOS 1.2 in ^Live Environment mode text help Experiment with FreeDOS without affecting your regular drives that hold one or more operating systems and user data. endtext linux /isolinux/memdisk initrd /isolinux/fdliveboot.img append nopassany --- Best regards Christian -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. www.gigenet.com___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2 - iso sizes and diskimage mounts
Hi Rugxulo, That would be a good compromise - basically BASE is a similar set of tools as you would get with plain MS DOS, which only takes a few megabytes in pre-unzipped live style. The rest, which easily takes more than 100 MB even in zipped, CAN still go live together with a little installer trick to use a ramdisk as install target to use FreeDOS on modern computers. A ramdisk of 200 or 500 MB easily fits most of the installable packages AND works on most newer PCs. However, some rare setups (and tools) choke on too much RAM (as opposed to not enough). This may not be flawless. Of course we should pick XMS drivers and ramdisks which do not have that issue. Otherwise, they will have the issue even without ramdisk. So I would be happy if a ramdisk can be loaded before the installer and can be used by it, of course as user selectable optional step :-) FYI, for simplicity, you may like something like Jack's RDISK, but as mentioned before, it lacks a few features (that I guess he considered rarely used). If unloading is important or something like XMSv2 compatibility, you'll have to (also) have something else available. RDISK sounds like a good plan. Together with a good XMS 3 driver, that should give a smoothly working large ramdisk. Unloading is not needed. Cheers, Eric PS: Dropping the image mount sub-topic again, pending Rugxulo's reply. I'm not sure exactly what you want here. I don't know of any (obvious) The question (in another thread) was if there was a disk image backed mountable drive driver which supports writing back changes to disk. I only know that the SHSUCD suite has a disk image backed read-only ISO (CD/DVD) image mount driver. The idea in the other thread was to add encryption between mounted drive and disk image, allowing several DOS users to share one computer but not see each other's data, decrypting only the home disk of the current user each time. Of course this is assuming that they are polite enough to not delete each other's disk. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2 - iso sizes and diskimage mounts
Hi, On Thu, Jan 8, 2015 at 7:11 PM, Eric Auer e.a...@jpberlin.de wrote: That would be a good compromise - basically BASE is a similar set of tools as you would get with plain MS DOS, which only takes a few megabytes in pre-unzipped live style. The rest, which easily takes more than 100 MB even in zipped, CAN still go live together with a little installer trick to use a ramdisk as install target to use FreeDOS on modern computers. A ramdisk of 200 or 500 MB easily fits most of the installable packages AND works on most newer PCs. However, some rare setups (and tools) choke on too much RAM (as opposed to not enough). This may not be flawless. Then again, nothing is, so the only way to know for sure is test. So I would be happy if a ramdisk can be loaded before the installer and can be used by it, of course as user selectable optional step :-) FYI, for simplicity, you may like something like Jack's RDISK, but as mentioned before, it lacks a few features (that I guess he considered rarely used). If unloading is important or something like XMSv2 compatibility, you'll have to (also) have something else available. From my off-list reply: The fdfullcd ISO was 150 MB and if I remember correctly, that was the size with zipped packages: Installing all packages to directories and then turning the result into an ISO could be 100s of megabytes. Regards, Eric PS: Dropping the image mount sub-topic again, pending Rugxulo's reply. I'm not sure exactly what you want here. I don't know of any (obvious) useful tools for this case. Sorry. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2 - iso sizes and diskimage mounts
Hi Jim, Harold / Mercury, Elsewhere in the discussion, I think we talked about unzipping the packages. I'm not sure what the live part of the ISO would be, but maybe that only needs to boot up the BASE packages (it doesn't make sense to have DEVEL on the live part, for example). That would minimize the size of the ISO, because the live part would be fairly small, and the packages to install would be zipped. That would be a good compromise - basically BASE is a similar set of tools as you would get with plain MS DOS, which only takes a few megabytes in pre-unzipped live style. The rest, which easily takes more than 100 MB even in zipped, CAN still go live together with a little installer trick to use a ramdisk as install target to use FreeDOS on modern computers. A ramdisk of 200 or 500 MB easily fits most of the installable packages AND works on most newer PCs. So I would be happy if a ramdisk can be loaded before the installer and can be used by it, of course as user selectable optional step :-) As mentioned earlier, I would also appreciate the possibility to install to USB disks or USB sticks, keeping the main harddisk of the PC safely ignored :-) From the thread: I think too big is relative here. The fd11src.iso is less than 40MB That is base + live base + zipped sources, I believe? Note that keeping the sources zipped is always okay. The main question is how much of the binaries to pre-install versus kept zipped. From my off-list reply: The fdfullcd ISO was 150 MB and if I remember correctly, that was the size with zipped packages: Installing all packages to directories and then turning the result into an ISO could be 100s of megabytes. Regards, Eric PS: Dropping the image mount sub-topic again, pending Rugxulo's reply. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2 - iso sizes and diskimage mounts
More specifically, the live part would be pre-loaded with the packages from BASE. It wouldn't unzip the packages at boot-time. On Thu, Jan 8, 2015 at 3:33 PM, Mercury Thirteen mercury0x0...@gmail.com wrote: So, the installer will automatically extract BASE from the .ZIP of packages to a RAM disk when booting live? Will this affect how I structure things on the .ISO? On Thu, Jan 8, 2015 at 4:10 PM, Jim Hall jh...@freedos.org wrote: Let's keep this discussion on the mailing list. Elsewhere in the discussion, I think we talked about unzipping the packages. I'm not sure what the live part of the ISO would be, but maybe that only needs to boot up the BASE packages (it doesn't make sense to have DEVEL on the live part, for example). That would minimize the size of the ISO, because the live part would be fairly small, and the packages to install would be zipped. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2 - iso sizes and diskimage mounts
Okay, I'll note that. BASE gets added to the .ZIP as well as copied as an actual folder structure in the ISO. I recall someone mentioning that they wanted to put a few finishing touches on their software before 1.2 gets released. Maybe we should establish a freeze date before which all pending updates have to be made? On Thu, Jan 8, 2015 at 4:41 PM, Jim Hall jh...@freedos.org wrote: More specifically, the live part would be pre-loaded with the packages from BASE. It wouldn't unzip the packages at boot-time. On Thu, Jan 8, 2015 at 3:33 PM, Mercury Thirteen mercury0x0...@gmail.com wrote: So, the installer will automatically extract BASE from the .ZIP of packages to a RAM disk when booting live? Will this affect how I structure things on the .ISO? On Thu, Jan 8, 2015 at 4:10 PM, Jim Hall jh...@freedos.org wrote: Let's keep this discussion on the mailing list. Elsewhere in the discussion, I think we talked about unzipping the packages. I'm not sure what the live part of the ISO would be, but maybe that only needs to boot up the BASE packages (it doesn't make sense to have DEVEL on the live part, for example). That would minimize the size of the ISO, because the live part would be fairly small, and the packages to install would be zipped. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
Hi Jim, Harold / Mercury13, FreeDOSers, Harold (AKA Mercury Thirteen) and I have been discussing creating a FreeDOS 1.2 distribution. He's volunteered to put together the new distribution. I thought we should share that with freedos-devel to see if anyone else wants to help with this! Good idea, thanks :-) Based on Mateusz' collection of FreeDOS style packaged DOS software, I assume? Sharing new packaging results with his repository? :-) FreeDOS 1.2 is planned to be a refresh to FreeDOS 1.1, using updated packages, although it will also use a new version of the installer and a simplified install process. Simplified sounds good. My thoughts for the simpler installation process: 1. *Boot the FreeDOS Install CDROM.* This is basically a live FreeDOS, which happens to boot into an automated install process. Or install USB stick, of course! On most systems, you could unzip all packages into a ramdisk to get full functionality. Having all packages fully installed on CD would make the CD too big. It would be nice to have some choices here: For example on old systems, do not do the ramdisk step. A set of equivalents of all the tools coming with MS DOS would be only a few megabyte in pre-installed form on the CD, while other, bigger, packages would not be available until you unzip them to ramdisk or harddisk or USB. There could also be an alternate, bigger, download of a CD which has all the packages pre-installed live, but with no or with a different install process as it will not contain zips to install from. I would vote for NO install process in that variant - it is safer. As a third download, there could be some tool which puts DOS on your USB disk or stick directly, for use with for example a few popular Windowses and Linuxes. - If you Exit the process at any time, you go back to a DOS prompt. (This is useful for people who just want to run FreeDOS from CD without installing it.) Makes sense. 2. *Does the C: drive exist?* - If not, prompt the user to run FDISK. Reboot to re-read the partition table. Dangerous! There should be an alternative where the CD installs DOS to USB stick instead. 3. *Is the C: drive usable?* - If not, prompt the user to run FORMAT. As above: Dangerous, allow other drives as install target. Modern BIOSes often have a boot from which device menu. 4. *Start the INSTALL program.* - This installs everything, using the new install program. 5. *Run SYS to make the C: drive bootable.* Not to forget checking for the C: partition to be bootable in the partition table. You can proceed even if it is not, but then the user has to know that they have to edit their hopefully existing boot menu to add an item to boot C: 6. *Do any follow-up steps* (such as creating a default CONFIG.SYS and AUTOEXEC.BAT, set language, etc). 7. *Done* Regards, Eric PS: Happy new year everybody! -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
[...] My thoughts for the simpler installation process: 1. *Boot the FreeDOS Install CDROM.* This is basically a live FreeDOS, which happens to boot into an automated install process. Or install USB stick, of course! On most systems, you could unzip all packages into a ramdisk to get full functionality. Yes, as I mentioned elsewhere in this discussion: *I haven't tried putting the FreeDOS 1.1 installer on a USB fob drive, but it would probably work if the ISO image was written using liveusb-creator.* *https://fedorahosted.org/liveusb-creator/ https://fedorahosted.org/liveusb-creator/* Having all packages fully installed on CD would make the CD too big. It would be nice to have some choices here: For example on old systems, do not do the ramdisk step. A set of equivalents of all the tools coming with MS DOS would be only a few megabyte in pre-installed form on the CD, while other, bigger, packages would not be available until you unzip them to ramdisk or harddisk or USB. I think too big is relative here. The fd11src.iso is less than 40MB, which is still quite small. The Fedora 21 Workstation install DVD image is 1.4GB. I think the option of having a live image of FreeDOS would be very helpful for many people, as you could boot FreeDOS without having to actually install it. We've needed to do that in our offices a few times (boot FreeDOS without installing) and I imagine many others have done the same. There could also be an alternate, bigger, download of a CD which has all the packages pre-installed live, but with no or with a different install process as it will not contain zips to install from. I would vote for NO install process in that variant - it is safer. As a third download, there could be some tool which puts DOS on your USB disk or stick directly, for use with for example a few popular Windowses and Linuxes. I'm not convinced that having two versions of FreeDOS 1.2 would be helpful to people. From our FreeDOS 1.0 download stats, when we had fdbase and fdfull, most people downloaded fdfull anyway, since that had all the utilities and everything on it. With FreeDOS 1.2, I want to make things simple for people who want to download and use FreeDOS. I think a single image is the best way to do that. At install-time, you can decide if you want to install everything (or just BASE) and if you want to include source code. But one install image would make things simpler. And FreeDOS isn't that big anyway. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2 - iso sizes and diskimage mounts
Let's keep this discussion on the mailing list. Elsewhere in the discussion, I think we talked about unzipping the packages. I'm not sure what the live part of the ISO would be, but maybe that only needs to boot up the BASE packages (it doesn't make sense to have DEVEL on the live part, for example). That would minimize the size of the ISO, because the live part would be fairly small, and the packages to install would be zipped. On Thu, Jan 8, 2015 at 2:58 PM, Eric Auer e.a...@jpberlin.de wrote: Hi Jim, Rugxulo, I think too big is relative here. The fd11src.iso is less than 40MB The fdfullcd ISO was 150 MB and if I remember correctly, that was the size with zipped packages: Installing all packages to directories and then turning the result into an ISO could be 100s of megabytes. Adding source codes will increase size further, but for the sources the zipped version will be totally sufficient even on a live iso :-) Regarding the driver to mount encrypted disks, I think there is a tool in the SHSUCD suite which mounts (of course read-only) ISO disk images as if they were CD or DVD disks. I am not aware of any disk backed ramdisk tool, not even without encryption, but I would not be surprised if Rugxulo had something in his collection. For example the memdisk tool can unpack and mount, but it cannot write back data. Regards, Eric -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2 - iso sizes and diskimage mounts
So, the installer will automatically extract BASE from the .ZIP of packages to a RAM disk when booting live? Will this affect how I structure things on the .ISO? On Thu, Jan 8, 2015 at 4:10 PM, Jim Hall jh...@freedos.org wrote: Let's keep this discussion on the mailing list. Elsewhere in the discussion, I think we talked about unzipping the packages. I'm not sure what the live part of the ISO would be, but maybe that only needs to boot up the BASE packages (it doesn't make sense to have DEVEL on the live part, for example). That would minimize the size of the ISO, because the live part would be fairly small, and the packages to install would be zipped. On Thu, Jan 8, 2015 at 2:58 PM, Eric Auer e.a...@jpberlin.de wrote: Hi Jim, Rugxulo, I think too big is relative here. The fd11src.iso is less than 40MB The fdfullcd ISO was 150 MB and if I remember correctly, that was the size with zipped packages: Installing all packages to directories and then turning the result into an ISO could be 100s of megabytes. Adding source codes will increase size further, but for the sources the zipped version will be totally sufficient even on a live iso :-) Regarding the driver to mount encrypted disks, I think there is a tool in the SHSUCD suite which mounts (of course read-only) ISO disk images as if they were CD or DVD disks. I am not aware of any disk backed ramdisk tool, not even without encryption, but I would not be surprised if Rugxulo had something in his collection. For example the memdisk tool can unpack and mount, but it cannot write back data. Regards, Eric -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
I thought to try something new with the updated installer. Rather than have one big program that does everything, why not create a few simple tools that can be used in an INSTALL.BAT to install FreeDOS? Enhanced Batch File tools already exist, I suppose, but I wanted free software tools. And of course, I prefer to stamp FreeDOS 1.2 at the top of the screen. :-) (If you want to point me to such Enhanced Batch File tools, with source code under some free license like the GNU GPL, please let me know.) Before I go much further, I wanted to see what people thought. Let's say we have a small utility that checks whether or not the C: partition exists - and if it does, it also checks if the C: drive is formatted (i.e. writable). This utility might be called CHECKC.EXE and return these errorlevels: 0 - C: partition exists and drive is writable 1 - C: partition does not exist 2 - C: partition exists but drive is *not* writable So the first step of the INSTALL.BAT would simply run CHECKC.EXE and then run FORMAT if errorlevel 2, or run FDISK if errorlevel 1, or proceed normally if errorlevel 0. @ECHO OFF CLS CHECKC.EXE IF ERRORLEVEL 2 GOTO *FORMAT* IF ERRORLEVEL 1 GOTO *FDISK* GOTO *CONTINUE* :*FORMAT* ECHO Ready to format the C: drive and make it bootable! PAUSE FORMAT C: SYS C: GOTO *CONTINUE* :*FDISK* ECHO The C: drive does not exist yet. Please run FDISK to set it up, then reboot. PAUSE FDISK GOTO *REBOOT* :*CONTINUE* (and so on) To make things look prettier as the INSTALL.BAT prompts the user, we might use a few enhanced batch file tools such as these: - VCLS (a visual CLS program, which clears the screen with a FreeDOS 1.2 header on a standard, colorful background) example: VCLS - VECHO (a visual ECHO program, which displays some text in a window on the screen) example: VECHO Please wait ... installing packages - VPAUSE (a visual PAUSE program, which displays a prompt, and waits for the user to press a key) example: VPAUSE Press any key to begin the install ... - VCHOICE (a visual CHOICE program, which lets the user select an item from a list of options) example: VCHOICE Do you want to include source code? Yes No I wrote the first three programs using conio. I could write the fourth (VCHOICE) but I figured it would be easier to manage a long list of options (for example: selecting a default language) if I used a TUI toolkit instead. So I'm looking into txwin. Here's a quick screenshot of the VPAUSE program: (attached PNG, 2.6kb) -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
I haven't tried putting the FreeDOS 1.1 installer on a USB fob drive, but it would probably work if the ISO image was written using liveusb-creator. https://fedorahosted.org/liveusb-creator/ I use this to every time I upgrade Linux on my laptop, because my laptop doesn't have a CDROM drive. It's great! On Jan 2, 2015 4:19 AM, Christian Imhorst christian.imho...@gmail.com wrote: Hi all, I agree with Tom M. I would like to have a better installer, too. If I could use this installer to install FreeDOS 1.2 from USB stick instead of floppy and/or CD that would be really great. :-) Best regards and thank you very much Christian Thomas Mueller mueler6...@twc.com schrieb am Do., 1. Jan. 2015 13:18: One thing I'd like to see in the next FreeDOS is a better installer. Installer should be writable to a USB stick or be bootable and runnable from a disk image; there is a rather outdated FreeDOS runnable quasi-floppy image on the System Rescue CD, though this image has no installer. I would like to see an installer (not necessarily bootable) that could run from Linux or FreeBSD, since many computer users these days have no DOS system, and running from Linux or FreeBSD would give the user more control than booting FreeDOS and not knowing which partition or disk is which. I have big hard drives, 3 TB or bigger, partitioned GPT, so the only place I could install FreeDOS to is a USB stick. Even on a modern system, FreeDOS can be useful for hardware diagnostic tools or BIOS/UEFI flash update. Tom -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
Hi all, I agree with Tom M. I would like to have a better installer, too. If I could use this installer to install FreeDOS 1.2 from USB stick instead of floppy and/or CD that would be really great. :-) Best regards and thank you very much Christian Thomas Mueller mueler6...@twc.com schrieb am Do., 1. Jan. 2015 13:18: One thing I'd like to see in the next FreeDOS is a better installer. Installer should be writable to a USB stick or be bootable and runnable from a disk image; there is a rather outdated FreeDOS runnable quasi-floppy image on the System Rescue CD, though this image has no installer. I would like to see an installer (not necessarily bootable) that could run from Linux or FreeBSD, since many computer users these days have no DOS system, and running from Linux or FreeBSD would give the user more control than booting FreeDOS and not knowing which partition or disk is which. I have big hard drives, 3 TB or bigger, partitioned GPT, so the only place I could install FreeDOS to is a USB stick. Even on a modern system, FreeDOS can be useful for hardware diagnostic tools or BIOS/UEFI flash update. Tom -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
One thing I'd like to see in the next FreeDOS is a better installer. Installer should be writable to a USB stick or be bootable and runnable from a disk image; there is a rather outdated FreeDOS runnable quasi-floppy image on the System Rescue CD, though this image has no installer. I would like to see an installer (not necessarily bootable) that could run from Linux or FreeBSD, since many computer users these days have no DOS system, and running from Linux or FreeBSD would give the user more control than booting FreeDOS and not knowing which partition or disk is which. I have big hard drives, 3 TB or bigger, partitioned GPT, so the only place I could install FreeDOS to is a USB stick. Even on a modern system, FreeDOS can be useful for hardware diagnostic tools or BIOS/UEFI flash update. Tom -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Working on FreeDOS 1.2
Harold (AKA Mercury Thirteen) and I have been discussing creating a FreeDOS 1.2 distribution. He's volunteered to put together the new distribution. I thought we should share that with freedos-devel to see if anyone else wants to help with this! FreeDOS 1.2 is planned to be a refresh to FreeDOS 1.1, using updated packages, although it will also use a new version of the installer and a simplified install process. My thoughts for the simpler installation process: 1. *Boot the FreeDOS Install CDROM.* This is basically a live FreeDOS, which happens to boot into an automated install process. - If you Exit the process at any time, you go back to a DOS prompt. (This is useful for people who just want to run FreeDOS from CD without installing it.) 2. *Does the C: drive exist?* - If not, prompt the user to run FDISK. Reboot to re-read the partition table. 3. *Is the C: drive usable?* - If not, prompt the user to run FORMAT. 4. *Start the INSTALL program.* - This installs everything, using the new install program. 5. *Run SYS to make the C: drive bootable.* 6. *Do any follow-up steps* (such as creating a default CONFIG.SYS and AUTOEXEC.BAT, set language, etc). 7. *Done* I had started work on the new install program a while back, but stopped development before it was fully ready. The latest code is in SVN on our SourceForge project. I'll see if I can update it for FreeDOS 1.2, although helpers are welcome! If you would like to help put together the FreeDOS 1.2 distribution, please email Harold at Mercury Thirteen mercury0x0...@gmail.com -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
I agree that a better installer is needed (the one in 1.1 seemed to be slow and generated broken AUTOEXEC.BAT files for non-US(?) keyboard layouts). I think we should adapt FDNPKG so it can be compiled with Open Watcom and use mTCP so it can be 8086-compatible. After installation, it could immediately update packages if newer versions are available. It would be also very cool if we could have some kind of autodetection of network cards and install a driver automatically (and generate WATTCP and mTCP configuration files?). Packet drivers are the easiest to install (we'd probably only need a table of PCI IDs - any volunteers? - and the driver filenames associated with them), but ODI and NDIS drivers might require some more work. And finally, it would be nice if my Slovene translations (not 100% complete yet though) could be included in the distribution. :) -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
On Wednesday, December 31, 2014, Matej Horvat matej.hor...@guest.arnes.si wrote: (...) And finally, it would be nice if my Slovene translations (not 100% complete yet though) could be included in the distribution. :) Hi Matej It's usually best to send translations of program strings (i.e. KITTEN or CATS) to the program maintainers so they can be included in the next release. If there isn't an active maintainer, or you aren't getting a response from the maintainer, email those KITTEN files to me and I can do a one-off update of those programs with your Slovene translations. Jim -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
I was actually working on a feature like this for my GUI so that it could automatically load drivers, which does a simple scan of the PCI bus and reports the devices it finds. There is already a list of PCI device IDs available at pcidatabase.com, which may be useful to us. I could extract my PCI scanner routines into their own application which performs the lookup and DEVLOADs the appropriate drivers. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
Hi all, The latest Slovene translations of everything are available here (with many other translations): http://freedoslocal.sourceforge.net/ I appeal to anyone having any translation updates to send them to me, so I will add them there. I can also provide svn rights to whoever would like to work on translating parts of FreeDOS. All translations shall be submitted in UTF8, the freedos localization project handles the conversion to whatever the final encoding should be. cheers, Mateusz On 12/31/2014 06:29 PM, Jim Hall wrote: On Wednesday, December 31, 2014, Matej Horvat matej.hor...@guest.arnes.si mailto:matej.hor...@guest.arnes.si wrote: (...) And finally, it would be nice if my Slovene translations (not 100% complete yet though) could be included in the distribution. :) Hi Matej It's usually best to send translations of program strings (i.e. KITTEN or CATS) to the program maintainers so they can be included in the next release. If there isn't an active maintainer, or you aren't getting a response from the maintainer, email those KITTEN files to me and I can do a one-off update of those programs with your Slovene translations. Jim -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
On Wed, Dec 31, 2014 at 8:54 AM, Matej Horvat matej.hor...@guest.arnes.si wrote: [SNIP] I agree that a better installer is needed (the one in 1.1 seemed to be slow and generated broken AUTOEXEC.BAT files for non-US(?) keyboard layouts). I think we should adapt FDNPKG so it can be compiled with Open Watcom and use mTCP so it can be 8086-compatible. After installation, it could immediately update packages if newer versions are available. I like the idea of standardizing on mTCP, especially if the openssl and ssh/sftp packages could be made to depend on it. However believe that the code hasn't yet been ported to djgpp or Watcom 32-bit so that would be an impediment to my ssl interests. It would be also very cool if we could have some kind of autodetection of network cards and install a driver automatically (and generate WATTCP and mTCP configuration files?). Packet drivers are the easiest to install (we'd probably only need a table of PCI IDs - any volunteers? - and the driver filenames associated with them), but ODI and NDIS drivers might require some more work. [SNIP] Dunfield Potthast already have PCI bus/NIC sniffers [0][1] and a collections of NIC packet drivers as well [2][3]. [0] http://www.classiccmp.org/dunfield/dos/pcinic.zip [1] http://www.georgpotthast.de/sioux/pktdrv/nicscan.zip [2] http://www.classiccmp.org/dunfield/dos/pktdrv.zip [3] http://www.georgpotthast.de/sioux/packet.htm -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
FDNPKG: I can help you with the changes to FDNPKG to allow it to compile under Open Watcom and to use mTCP. I would certainly like to see more people using mTCP to build their applications. However, is moving to mTCP going to improve FDNPKG enough to make it worth the effort? (That is just something to think about. I can tell you about what I think the advantages of Open Watcom and mTCP are offline.) Hardware support and installers: This is just some food for thought ... There are a lot of old systems running around. FreeDOS should be able to run on anything from an XT all of the way up to a modern PCI system, assuming the BIOS is reasonable. (And one day I'll add PCjr support.) An installer can certainly be PCI aware. But assuming PCI or doing something that makes the installer unusable on an earlier system would be a regression. I think that you can assume that a CD-ROM is present. But you should not assume that a machine is capable of booting from a CD-ROM. We should support installing from CD-ROM, but be careful to ensure that booting from CD-ROM is not a requirement. I think a reasonably good installer would have the following form: - A bootable CD-ROM image for machines that support it. - A bootable floppy image with enough support to load the CD-ROM device driver for machines that have CD-ROM, but can not boot from it. - Instructions for how to create boot media and diskettes for machines that do not have CD-ROM. This may assume that the user doing the install has access to an already installed FreeDOS. (It would be nice if FreeDOS provided official images, but your typical hobbyist with an XT can follow directions.) What is the timeframe for a 1.2 release? I would like to make some additions to mTCP before another FreeDOS release goes out into the wild. I was thinking of a utility to make it easier to configure mTCP and diagnose packet driver problems. I also have the HTTP server, which is not open source yet but could be if there was sufficient interest. Mike -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
Another thing we could do, in the same vein as the suggestions by Matej, would be to make an app store of sorts which would function as a package manager. When run, this program would search the user's hard drive to see what components are installed, determine their version and see if there is an update available, download said updates using mTCP calls and update items as necessary. Or, maybe I'm going too ambitious here and we should leave the fancier features to FreeDOS 2.0? -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
On 12/31/2014 08:02 PM, Mercury Thirteen wrote: Another thing we could do, in the same vein as the suggestions by Matej, would be to make an app store of sorts which would function as a package manager. When run, this program would search the user's hard drive to see what components are installed, determine their version and see if there is an update available, That's exactly what FDNPKG is for. download said updates using mTCP calls Not gonna happen until mTCP becomes 32bit-friendly. Mateusz -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
Dunfield Potthast already have PCI bus/NIC sniffers [0][1] and a collections of NIC packet drivers as well Georg has some useful stuff there, but the bus scanner isn't (currently, at least) open source software and couldn't be included in FreeDOS. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
As much as I like my 16 bit machines, I'm open to making mTCP 32 bit friendly. The code is very careful with data types - I never use int when the number of bits matters. The trouble spots are going to be the IP checksum routine which is hand-optimized assembly, my time of day code which looks at BIOS ticks, and some bits of ASM I have sprinkled in the applications to avoid using the Watcom runtime equivalents. But the base library code itself reasonably clean. If somebody has a good FAQ or how to get started that introduces me to 32 bit DOS extenders I'm willing to do the work. 32 bit would improve the code generation quite a bit and make it even faster. On Wed, Dec 31, 2014 at 11:04 AM, Mateusz Viste mate...@viste.fr wrote: On 12/31/2014 08:02 PM, Mercury Thirteen wrote: Another thing we could do, in the same vein as the suggestions by Matej, would be to make an app store of sorts which would function as a package manager. When run, this program would search the user's hard drive to see what components are installed, determine their version and see if there is an update available, That's exactly what FDNPKG is for. download said updates using mTCP calls Not gonna happen until mTCP becomes 32bit-friendly. Mateusz -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
So far as a tutorial, I'm afraid nothing jumps to mind. However, in my tests I found that the DOS4GW extender which ships with Watcom is the fastest. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
Aha, and here I thought I was being original lol The version of FreeDOS I use for development is a premade image with VirtualBox networking already set up. It doesn't include your software, so I guess its existence slipped my mind. Sorry about that. On Wed, Dec 31, 2014 at 2:04 PM, Mateusz Viste mate...@viste.fr wrote: On 12/31/2014 08:02 PM, Mercury Thirteen wrote: Another thing we could do, in the same vein as the suggestions by Matej, would be to make an app store of sorts which would function as a package manager. When run, this program would search the user's hard drive to see what components are installed, determine their version and see if there is an update available, That's exactly what FDNPKG is for. download said updates using mTCP calls Not gonna happen until mTCP becomes 32bit-friendly. Mateusz -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
i made a custom version of fdpkg that simply updates the directory creating mechanics of it i wish it has mtcp support so we can have a 16 bit answer to fdnpkg -- View this message in context: http://freedos.10956.n7.nabble.com/Working-on-FreeDOS-1-2-tp21507p21524.html Sent from the FreeDOS - Dev mailing list archive at Nabble.com. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
As the old year is passing and you mention FDNPKG I would like to point to my website at https://www.lazybrowndog.net/freedos/virtualbox2/ I worked on the website in September but wasn't able to polish it as much as I hoped for. I would like to add another image for networking with ms client. And a howto. Then it will replace my old resource for Vbox freedos. But anyone, who is interested in checking out FDNPKG may just install the freedos 1.1plus image... Best wishes and the best start to the new year! Cheers Ulrich Am 31.12.2014 um 20:04 schrieb Mateusz Viste mate...@viste.fr: On 12/31/2014 08:02 PM, Mercury Thirteen wrote: Another thing we could do, in the same vein as the suggestions by Matej, would be to make an app store of sorts which would function as a package manager. When run, this program would search the user's hard drive to see what components are installed, determine their version and see if there is an update available, That's exactly what FDNPKG is for. download said updates using mTCP calls Not gonna happen until mTCP becomes 32bit-friendly. Mateusz -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
On 12/31/2014 08:17 PM, Michael Brutman wrote: As much as I like my 16 bit machines, I'm open to making mTCP 32 bit friendly. That would be great! When it happens, I will be happy to port my DOS networking software to mTCP (that is, the FDNPKG package manager and my gopher client Gopherus). cheers, Mateusz -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
Jim, will your installer still need the .LSM files?If so, do you need them for each .EXE or just for each package? -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Working on FreeDOS 1.2
On Wed, Dec 31, 2014 at 3:16 PM, Mercury Thirteen mercury0x0...@gmail.com wrote: Jim, will your installer still need the .LSM files?If so, do you need them for each .EXE or just for each package? The LSM needs to be present (it goes in APPINFO, I think) but the new installer doesn't read LSM files. It just reads a list of package files that need to be installed, and installs them. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
