Hi all,
2015-01-02 15:15 GMT+01:00 Jim Hall :
> 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 lapt
Hi,
On Fri, Jan 9, 2015 at 5:16 PM, Eric Auer 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 driv
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
>> wit
Hi,
On Thu, Jan 8, 2015 at 7:11 PM, Eric Auer 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 zipp
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).
>
>
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 upd
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
wrote:
> So, the installer will automatically extract BASE from the .ZIP of
> packages to a RAM disk when booting liv
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 wrote:
> Let's keep this discussion on the mailing list.
>
> Elsewhere in the discussion, I t
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 ex
>
> [...]
> > 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 r
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!
Go
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
cou
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 g
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 schrieb am Do., 1. Jan. 2015 13
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 lik
On Wed, Dec 31, 2014 at 3:16 PM, Mercury Thirteen
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
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
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
"Gopheru
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.
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 FreeD
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
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,
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
> 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.
---
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 i
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
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 some
On Wed, Dec 31, 2014 at 8:54 AM, Matej Horvat
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 mTC
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
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 s
On Wednesday, December 31, 2014, Matej Horvat
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 p
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
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.
33 matches
Mail list logo
