Re: [Freedos-devel] slow FreeDOS install - was: FreeDOS 1.2-RC1 onHyper-V 2012 R2

[Jerome E. Shidel Jr.]

> On Nov 18, 2016, at 11:09 AM, Maarten Vermeulen  wrote:
> 
> Never mind! It was indeed a problem with only the booting CD's, I did 
> something wrong I guess….

No problem. It happens. 

Assuming I have the time, I will be looking into using the other bootable CD 
spec over the next couple days. I will be testing its compatibility with 
VirtualBox. If it goes well, we may switch over to using it instead of the El 
Torito Spec version. Unfortunately, that would require anyone using a 
pre-Pentium II to use the boot floppy. But, they should have one. Maybe, if 
testing goes well we will do two versions, FD12CD.iso and FD12LGCY.iso (for 
legacy hardware). We will see.

Jerome.
--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] slow FreeDOS install - was: FreeDOS 1.2-RC1 on Hyper-V 2012 R2

[Jerome E. Shidel Jr.]

> 
> @echo on in the batch files to the rescue. :)

That would be a very painful experience.

> 
> On Tue, Nov 15, 2016 at 1:43 PM Maarten Vermeulen  > wrote:
> Hi all,
> 
> Maybe it is good to give some extra information, if it helps:
> It hangs, the only thing it does is making the temporary folder. After it has 
> done that, it will
> sit an hour doing nothing (as far as I can see). That's why I think it hangs 
> at least.
> 
> I am using Virtualbox version 5.0.24 r108355, for if that's interesting... 
> Anyway, I tried to install it on a .vhd and a .vdi virtual harddrive it 
> happend on both. My system is just a single core CPU, with 32MB RAM and a 
> 500MiB hdd.

I assume you booted the the CD-ROM and on boot the installer through you 
straight to the command line with a message that warned you that you should not 
install it on that platform using that media.
Then you ran setup.bat manually. Then when you got to “Gathering information…” 
it froze. If you used another method, there may be an issue. Otherwise, this 
problem is known and is not a problem with the installer itself. It is a 
compatibility issue that only occurs under VirtualBox when booting FreeDOS 
using an El Torito based CD. It may not occur if the boot configuration used 
different drivers or memory managers. If you boot the floppy and just use the 
CD for packages, the problem vanishes. The issue does not occur under vmWare or 
other tested virtual machines. Beyond spending hours testing the installer to 
verify it was not a problem with it, little testing to find the exact cause has 
not been done. However, based on the behavior my best guess is it is a bug in 
VirtualBox, the Kernel, FreeCOM or one of the device drivers. 

Another symptom of the issue, boot the CD. From the command line, you can 
navigate the CD contents from the command prompt using the built-in FreeCOM 
shell internal commands (DIR, CD…). But, ANY program (Like FreeDOS Edit) that 
access the CD-ROM portion of the El Torito CD causes instant system lockup. 

I have thought about switching to the more modern HDD based boot CD format. 
But, both have problems. The El Torito spec is the original widely accepted 
method. Old machines that can boot this type may not be able to boot the later 
HDD spec version. The HDD type really wasn’t commonly used until post Pentium. 
I’ve got a functioning Pentium Pro that can not boot HDD version CDs. Now, on 
the other hand, once the HDD CD spec was long established, I doubt many vendors 
did much testing with the older spec. Maybe we could talk Jim into 2 CDs, one 
for pre-Pentium II, one post.

Maybe someday, VirtualBox will fix the problem. This is why the installer 
allows you to still launch manually.

Now, if you are having this issue when booting the Floppy or USB image in 
VirtualBox, it would be something new. But, I do a lot of testing using the 
latest version of VirtualBox on a Mac. My personal recommendation for a 
VirtualBox install is to use one of the USB stick images. It is about 10x 
faster than Floppy+CD. Basically, just create the VM like normal. Move the New 
drive to Primary/Slave. Connect Primary/Master to the USB stick. Do install. 
Swap USB Stick and HDD. Overall 30-60 second install.


> I will look if I can find a solution to this on my own.
> 
> This matches some observation by Maarten during a FreeDOS install:
> 
> The installation spends a LONG time while displaying the text
> "gathering information". Question about the installer: What
> does that step do and are there ways to optimize it?

The only thing that actually happens while the “Gathering information….” screen 
is displayed at present is locating installation package install media. (i.e., 
CD-ROM/USB Stick's drive & path).
That usually happens instantly when using a USB stick and usually under a 
second for the CD-ROM. But, I inserted a couple second delay so the message 
just would not flash on past. On a very slow system with lots of drives it 
could take a couple seconds to locate the packages. If they are not found, the 
system doesn’t see them and you get an error message.

Maybe, future versions will do more at “Gathering information.” But, for now 
that is all that happens there. The temp directory is made prior to the “GI” 
message.


> I could
> imagine that it tries to compare existing file versions to
> the to-be-installed versions. This could be made faster by
> making a directory listing of the old DOS installation once,
> then keeping it in RAM (or in a file) while checking which
> packages are up to date and which are not. Educated guesses.

The installer does not do version checking on files. 

Later on, during the install. It attempts to removes all packages that it will 
be installing. Then it saves the remaining installed package meta data files. 
Purges the DOS directory of any remaining files. Installs all fresh packages 
and restores the preserved package 

Re: [Freedos-devel] keyb us does not work

[Jerome E. Shidel Jr.]

Hello Paul, 

> On Nov 6, 2016, at 12:14 AM, Paul Dufresne  wrote:
> 
> After installing in french, I get french keyboard...
> you might find it strange, but here in Quebec, we are totally lost
> with french keyboard.

Are you certain you selected the US English when you were presented with the
“Select your keyboard layout” screen. The installer preselects a layout on the
short keyboard layout list that is based on the language you are using. 

EN —> US English (No keyboard layout, OS default QWERTY)
ES —> Spanish
FR —> French
DE —> German
NL —> Netherlands

So, if you selected French as your language in the beginning (or the installer 
detects it from a previous installation), it would preselect the French Keyboard
Layout. User language and keyboard layout do different things. 

Basically, the following happens during the installation.

Language selection causes:

LANG environment variable to be set to language code and sets this in
the AUTOEXEC.BAT as well.

If additional language settings are included in the language SETLANG.BAT 
for that language, those are activated immediately and are also embedded 
in the new AUTOEXEC.BAT. This is good for adding display settings and 
whatnot. However, at present, this capability is unused.

If a custom FreeCOM shell for that language is present it uses it to replace
the default COMMAND.COM.

Keyboard layout selection causes:

The appropriate entry from that languages KEYBOARD.LST file to be spliced 
into the AUTOEXEC.BAT file. In the list, items 1-9 are reserved for the short 
keyboard layout list and from 10 on are the big scrolling “More choices” list.

It is possible that future versions of the installer will activate an 
appropriate keyboard
layout during the installation and provide the user with a test and 
verification screen. 
However, since the topic did not come up until the release date was upon us, it 
will 
not be in 1.2 RC2 or Final. The community waited far to long to request the 
keyboard
layout selection feature. 

> US is much more usable for us.
> 
> But then, when I type
> keyb us

The keyboard layouts I added use mkeyb instead of keyb, Typing,

mkeyb US 

Will cause mkeyb to revert to US English QWERTY. This may not be the case for 
all
future keyboard layouts. If they were provided, the installer could also use 
xkeyb, 
keyb and any other layout solution as well as mkeyb. Although the community 
demanded the ability to select a keyboard layout in the installer, no-one has 
provided
any. So, the entries I made are limited to the ones I felt were the most 
popular and
were provided by mkeyb. I will not be making any more of them myself. It can be
a time consuming process and I have no way to test or verify any settings I 
devise 
are correct.

Thanks, Jerome

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 -- Whats Up?

[Jerome E. Shidel Jr.]

Have you wondered exactly what has been updated in the new FreeDOS release 
since version 1.1?

Check it out 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/previews/1.2-rc1/compare.html
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] VirtualBox and RC1 Networking

[Jerome E. Shidel Jr.]

Hello Louis, 

> Any idea how VirtualBox was configured for the user reporting the
> issue?  NAT, Internal Network, Bridged, Host-only?  This could answer
> the firewall question.

This was discovered to be an issue after the last VirtualBox update by Me 
during final testing just before the final RC1 release.

Basically, It is just a test virtual machine using VirtualBox standard 
defaults. This was fine in previous versions of VB. But, not now.

VirtualBox defaults to NAT. I’ve tried others like Bridged and different NICs. 
But those mostly don’t work at all. I see there is a “Port Forwarding” in VB 
advanced networking settings. I don’t know if it was there prior to the latest 
update to VB.
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] VirtualBox and RC1 Networking

[Jerome E. Shidel Jr.]

Hello All,

The latest release of VirtualBox seems to have broken networking support on 
that “hardware.” Under the previous version of VirtualBox, installing the FDNET 
package (included with RC1) would provide an automatic fully working networking 
support. Programs like FDNPKG, PING, WGET and such worked great. However, with 
this last VirtualBox update, this is not the case. PING appears to function 
properly. But, everything else seems to fail. FDNPKG throws “failed” messages, 
WGET says “Connection reset by server”, etc. I do see that VirtualBox seems to 
have configuration settings for an integrated firewall. But, I don’t know if 
they were there in the previous release when networking “just worked.” I have 
heard that this has also occurred with some Windows installs in VirtualBox. 
This leads me to think that it is probably not a problem with the packet drive 
or networking inside the VM.

So, does anyone know if it is a VirtualBox configuration issue or a VirtualBox 
bug? If it is a configuration issue, do you know how to remedy the problem?

Thanks, Jerome
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2

[Jerome E. Shidel Jr.]

Hello all,

Only one more day until FreeDOS 1.2-RC1. :-)

Also, I made some minor updates to the scripting that auto-generates the html 
pages for the online software repository. Among the improvements, the pages for 
packages now provide links to “previous" package versions for added 
convenience. A good example of that would be the devel/nasm package. To 
directly browse the repo online, just visit 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/
 


Jerome--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 - Keyboard Layouts

[Jerome E. Shidel Jr.]

Hello All,

Jim has been very busy over the last couple weeks and I have not heard back 
from him as of yet.  
His decisions on these matters are not yet known. However, I fully understand 
the pain involved 
with trying to use a command line that is mapped to a a language other than the 
one being used. 
Although I am in the US, I have experienced this with remote terminals and 
linux distributions
that are configured for languages other than English. 

So, I have implemented the following for the installer. I know it is not a 
perfect solution for all 
users. But, I think it solves most of the issues and best conforms to the 
(overall) easy and 
simplified installation process. Jim may or may not want the installer to 
always prompt for
keyboard layout selection.  I have no way of knowing and this may change once I 
hear from him.

If the user is in normal mode and English is the language, it will not prompt 
for keymap 
settings and assume default of a US English.

If the user is in advanced mode or picks a non-English language, it will prompt 
with a 
short list of 7 keymaps (US, UK, ES, FR, DE, DE-Alternate and NL). These mostly
match the current language selections available for the installer. The 
installer also 
preselects one of these keymaps based on the users language. For example, if 
they 
are using German, it will preselect a German keyboard. The user is able to 
change this
selection or choose the “More Keyboard Options…” (MKO). The MKO contains the 
same 7 keyboard selections (built-in) and 3 additional ones (Latin, Swiss 
French and 
Swiss German) at present. MKO is a scrollable dynamic list created at release 
time 
and has no set limit to the number of choices that can be provided. However, I 
will 
not be creating any additional keyboard options. There is no way for me to test 
them.

This is where all of you come into this. If you provide me with the complete 
data for an additional
keymap I will have the installer add it to the MKO section. Without any 
community provided 
submissions, there will only be 10 keyboard layout choices provided. 

These are the requirements:

Any comments that are to be included with the release must start with a ; 
(semi-colon).
Lines that are not Title Translations, Command Lines or Comments will be 
automatically 
stripped out during their concatenation in the release build process.

All major language translations are required. (English, Spanish, German, 
French, Dutch
and Esperanto) If a translation is missing, it will be EXCLUDED from that 
language as 
an option. 

The CMD field is the exact DOS command that will be embedded in the 
AUTOEXEC.BAT 
file. Technically, you could have multiple CMD entries for multiple lines. But, 
you
probably should avoid doing that. 

KEYB, KEYB_LAY and MKEYB packages are all installed with FreeDOS 1.2 BASE. 
So, mkeyb.exe, key.exe, xkeyb.exe and others are available to be used. You 
should test 
your command line under FreeDOS 1.2 Preview 23 (or soon later version) BASE 
Only 
installation to ensure it functions properly. 

Deadline for inclusion in FreeDOS 1.2-RC1 is 10/29/2016

Deadline for inclusion in FreeDOS 1.2 (Final) is 11/11/2016

Here is the Swiss German Keyboard layout definition file as an example.

[begin file SWISS-GR.KYB]

; Optional Swiss German Keyboard Layout Definition
; by Jerome Shidel

EN=Swiss German
ES=Suizo Alemán
DE=Schweizerdeutsch
FR=Suisse allemand
NL=Zwitserduits
EO=svislando germana

CMD=mkeyb.exe SV

[end of file]

Thanks,

Jerome

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

[Jerome E. Shidel Jr.]

Hello Juan,

First, thanks all the information. It definitely should be helpful.

> [..]
>> What host OS are you using?
> openSUSE 11.4

Love openSuSE. (My personal favorite distro!)

> [..]

Based on your information, I have been able to replicate the problem in
VirtualBox as well. Basically, this seems to be a summary of the issue.

A pre-formatted floppy image has no issue being formatted in any mode.

A zero’d image file for a floppy appears to be problematic. A simple test
is to create an a blank image by using “dd bs=512 count=2880 if=/dev/zero 
of=floppy.img”
Then attaching this to a virtual machine and simply formatting with “format a:” 
or 
“format /u a:” terminates with and error code.

However, telling format the image size appears to bypass the issue.
For example, “format /f:1440 a:” appears to always work.

Jerome

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

[Jerome E. Shidel Jr.]

> On Oct 22, 2016, at 1:11 PM, Antony Gordon  wrote:
> 
> Hi,
> 
> Host OS should not matter. If the "gold standard" of MS-DOS works in that 
> configuration with the disk images, there is definitely something that isn't 
> right in this release. For those having a problem, what happens in FreeDOS 
> 1.1.
> 
> Tony
> 
Absolutely, unless there is a Platform specific bug with the VM software, 
default configuration settings and other very OS specific issues. 

For example, image file marked as read-only or writable only by root but 
running as user. When doing testing and such, I once set one of 
the hard disk images to 644 (on purpose) on a Mac. This was a few months back 
and did not behave like I expected. I think it was in
VirtualBox. If I recall correctly, it would act like it was writing to the 
drive but after a while would start throwing errors.

Jerome.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

[Jerome E. Shidel Jr.]

Hello Juan,

> On Oct 22, 2016, at 7:55 AM, Juan Manuel Guerrero  
> wrote:
> 
> OFYI: I have tried to format a floppy image with a VMware Player 5.0.2 using
> FreeDOS 1.2-pre23 and I have observed the same issue as described for 
> VirtualBox.

The FreeDOS 1.2 preview releases are built under FreeDOS 1.2 build environment 
(BE),
The BE is running under VirtualBox and contains 2 floppy drive images and 3 
hard disk
drive images. The USB and CD releases of 1.2 contain a utility FDIDEV.BAT that 
will convert a (virtual) machine into a FreeDOS BE. Each preview release is 
built 
automatically using the mkFDI.bat utility that is installed and part of the BE. 
During the
build process performed by mkFDI, this utility reformats both Floppy images and 
two
of the hard disk images. It does this to zero out unused portions for better 
disk
image compression at release time. I have seen no issues formatting any of these
images from FreeDOS inside VirtualBox. Earlier builds (like preview 10 and 
earlier) 
were running inside VMware Fusion. But, VirtualBox performed the build many 
times
faster. I saw no issues under VMware Fusion either.

Now, just as a quick verification, I duplicated a 1.44 floppy image and booted 
a test
install of Preview 23 inside VirtualBox 5.0.28. Format reported no problems with
any of the various methods I used to reformat that floppy image.

Other than the errors you are getting towards the end. I see only line that 
differs
in my debug log.

[DEBUG]  Sector buffer at 0E17:6770, track buffer at 0E17:6B70

This is probably just due to the difference in the virtual machine BIOS. Or, 
possibly the booted configuration. 

> [..]
> [DEBUG]  Sector buffer at 1A3F:6770, track buffer at 1A3F:6B70
> [..]
> [DEBUG]  FAT Sectors: 1 to 18 ->
>   0% +**Drive_IO(WRITE 1, count 1 ) [FAT12/16] [drive A*]
> 
>  Critical error during DOS disk access
>  DOS driver error (hex): 01
>Description: unknown unit for driver
>  Program terminated.
> [DEBUG]  DOS 7+, UNLOCKing drive (by one level)
> [DEBUG]  DOS 7+, UNLOCKing drive (by one level)

Just as verification, I have a couple simple questions that you have probably 
already checked.

What host OS are you using?

If you booted the CD under VMware and installed FreeDOS, are you still booting 
the
El Torito CD?

Are you running the latest Version of VirtualBox (5.0.28)?

Have you made major changes from the default VirtualBox settings?

Have you modified the boot configuration of FreeDOS and is something 
conflicting?

Are you sure the actual floppy image is a valid size, exists and is writable by 
the host OS? 
(maybe download the FD12FLOPPY.zip and try formatting it’s image)

Jerome
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

[Jerome E. Shidel Jr.]

Hello Tom,

> On Oct 15, 2016, at 12:27 PM, Tom Ehlert  > wrote:
> […]
> I can understand that you - as a user of the BIOS standard US keyboard -
> have little understanding of the size of the problem.
> 
> we had recently a discussion about turkish keyboard layout.
> 
> to make you more aware of the problem, try to put
> 
> KEYB TR,,KEYBRD2.SYS /ID:440
> 
> for this http://ascii-table.com/keyboard.php/440 
>  keyboard, into
> AUTOEXEC.BAT.
> 
> Now try to edit AUTOEXEC.BAT and put REM into front of the KEYB line.

No need. I have used linux distributions that did not correctly map the keyboard
when US was selected or when logged in remotely. So, I know the pain of using 
a console that does not match your keyboard. But, this has been rare and I have 
never needed to mess around with it under DOS.

>> Unfortunately, I don’t see support for DE or EO in mkeyb 0.41. I do see NL 
>> and FR.
> 
> 
>> So, unfortunately I just can’t add this to the installed main config file:
> 
> 
>> if %LANG% == “EN” goto NoKeyb
>> mkeyb %LANG%
>> :NoKeyB
> 
> language != keyboard.

Ya, I know. It would be nice though. But, alas it is not practical. Let’s just 
consider US English Language. Just a couple possibilities, QWERTY, DVORAK,
Windows, Macintosh, 88-Key, 101-Key and so on and on.

> even as a german user, I always have used, use, and will use a US
> ASCII keyboard. Similar for NL, and the UK keyboard is different from
> US ASCII.

That is exactly why I feel that automatically setting the keyboard is just as 
bad as not setting it.

> you will have to add an additional dialog for keyboard selection.

I don’t know if that is going to happen or not. We really are getting down to 
being
a couple days from releasing RC1. This topic should have been brought up
several months ago when development of FDI became mostly idle and only
minor package changes for the release started being applied.

I don’t know wether or not Jim will give the OK to add that for non-US language 
installations. Depending on when I get an answer from him, I may not have 
sufficient time to implement it. 

All of that being said, It would not be difficult to add it to FDI. It has been 
designed to 
be expandable and fairly easy to add additional functionality and prompts. I 
will
probably be able to scrape up a few spare minutes to implement an additional
installer prompt for non-US language keyboard selection. Just depends on
what Jim decides and when.

Jerome--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

[Jerome E. Shidel Jr.]

Hello Eric, 

> On Oct 14, 2016, at 4:01 PM, Eric Auer  wrote:
> 
> 
> Hi Jerome, as said, I would recommend a little dialog in the
> installer for the MKEYB keyboard languages only, with a REM
> line in the config to let people enable other layouts with
> the bigger KEYB manually at a later moment. See the list here:

I don’t know if Jim would prefer an additional screen prompt or not.
I will ask him.

> 
>> C:\>mkeyb /L
>> mKEYB 0.34 [Sep 18 2002] - all languages Copyright (c) 2002 www.tomehlert.de
>> […]
>> HE - HEBREW - hebrew keyboard (by diego)
> 
> Cheers, Eric
> 


1.2 will be shipping with mkeyb 0.41 dated 2006. It contains (at a glance) a 
dozen or so
more languages. 

I see GR, GR2 and SG (Swiss German) keymaps available.

Being in the USA and using a US Keyboard, I have never messed with these. But,
MKEYB is easy to use. So, I will see what Jim wants to do. At worst, I will 
have it
include REM’d versions.

Unfortunately, I don’t see support for DE or EO in mkeyb 0.41. I do see NL and 
FR. 

So, unfortunately I just can’t add this to the installed main config file:

if %LANG% == “EN” goto NoKeyb
mkeyb %LANG%
:NoKeyB



Jerome--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

[Jerome E. Shidel Jr.]

Hello again Juan,

> On Oct 13, 2016, at 3:32 PM, Juan Manuel Guerrero  
> wrote:
> 
> Hello Jerome and Eric
> 
> Thank you for your comments.  IMHO the issue of having a working keyboard is
> essential.  DOS and its clones appear to their users as TUI thus if the
> keyboard does not allow to issue commands it makes the OS to become almost 
> useless.
> An user that has to hit around ten different keys until he finds the backslash
> key only to be capable to issue a "cd" command will lost interest quite soon.
> I had to mount the virtual disk to be capable to inspect it without getting
> crazy due to the keyboard and to figure out how to fix the issue.  30 years 
> ago
> I used to use MSDOS every day all day long and thus I was suprised how much 
> the
> directory structure and the available drivers and files differ from old DOS.
> So trying to fix this was not so straightforward as I expected at a first 
> glance.
> 
> IMO this issue could be tremendously alleviated by adding to FDCONFIG.SYS and
> AUTOEXEC.BAT, as comments, those lines that are required to select a 
> particular
> keyboard layout.  Having the required lines at the appropriate places together
> with some docs will allow those users that are experienced with DOS already to
> fix the issue by themselfs.  Please note that I am not expecting any kind of
> magic.  The MSDOS installer also did never offer any kind of magic but at 
> least
> it asked the user to specify some locale and deduced from this what keyboard
> specific lines to add to config.sys and autoexec.bat.
> Neitherless it should be remembered that outside the US, the US keyboard 
> layout
> is almost useless because crucial keys like backslash and colon are at 
> different
> places and thus not easily found frustrating the average user quite soon.
> 
> 
> Regards,
> Juan M. Guerrero
> 

FDI (the FreeDOS Installer) was designed to be able to handle stuff like 
language specific 
settings. But, no-one has provided me with keyboard or codepage settings. I 
have no way to 
test them and will not guess. We are now very close to the 1.2 release. So, 
having FDI setup 
language based keyboard customizations is not likely to happen in the current 
release.

However, if you provide me with the settings needed for the most likely (single 
or multiple)
settings for you language, I will have FDI embed them as REM statements when 
your
language is installed. Both the KEYB and MKEYB keyboard packages are installed
by default with base.

This is easily accomplished. When running FDI it automatically calls a 
SETTLANG.BAT 
file for specific languages. If it is not present for a specific language,  it 
falls back to
using the default one for English. The contents of this batch file are also 
embedded 
into the installed AUTOEXEC.BAT file. This file would be located in the 
FDSETUP\SETUP\%LANG% directory.

So, if you create one that looks like this:

@ECHO OFF 

REM LANGUAGE SPECIFIC KEYBOARD SETUP
REM FILE: FDSETUP\SETUP\GR\SETLANG.BAT

IF NOT EXIST %DOSDIR%\BIN\KEYB.EXE GOTO NoKeyb

keyb.exe ? ? ? ? ? ? ?

:NoKeyb

and place it in the appropriate directory on the floppy or usb stick it will 
automatically be
included in your autoexec.bat.

Jerome

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 Preview 23

[Jerome E. Shidel Jr.]

Just an FYI,

I noticed a minor cut & paste error in the mkFDI.bat build utility. 
This issue effected using FDIDEV.BAT to replicate the build environment. 
This issue also prevented FDI from installing source files when installing 
FreeDOS.

This issue has been resolved for the next release (RC1).

Jerome
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Road to Perdition

[Jerome E. Shidel Jr.]

Hello Tom, 


> On Sep 29, 2016, at 1:07 PM, Tom Ehlert  > wrote:
> 
>> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/base/command.zip
>>  
>> 
> 
>> If that's the correct new version (it should be the version from the
>> latest FreeDOS 1.2 pre-release) then we can copy this into the
>> ibiblio.../dos/command/ download area.
> 
> the binaries are  2006.
> 
> the source file modification dates were trashed on 17 august 2006.


That appears to be correct. This version reports:

FreeCOM version 0.84-pre2 XMS-Swap [Aug 28 2006 00:29:00]

0.84pre2 is from 2006. So, if there is a version from 2011, is it possible it 
is a
later version (something like 0.84pre2b)? Or, possible a custom fork of the
original 0.84pre2?

Jerome--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.2 Auto NET Config

[Jerome E. Shidel Jr.]

Hello Ulrich,

I will definitely look into it very soon. 
(Probably next weekend. Some changes at work have really limited my free time 
lately)

Rugxulo has also pointed me to a FreeDOS based release that MetaDOS. It 
seems to do the automatic networking setup pretty well. Under VirtualBOX,
it works with the default settings. But with VMware Fusion, you must change
the type of networking adapter. However, that is all the further that I have 
been able to look at it so far. I don’t know if there are any issues with 
porting 
it to the official FreeDOS release. I have not had the time to delve into it and
figure out exactly what needs to be done. 

https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/unofficial/metados/
 


Your solution will probably be easier for me to implement though. Especially, 
since
you have figured out all of the steps needed to get it working. 


> On Aug 21, 2016, at 8:20 AM, Ulrich Hansen  wrote:
> [..]
> are already in your AUTOEXEC.BAT. But there are bugs...
> 
> Bug 1
> In your AUTOEXEC.BAT you have a line:
> REM CHCP 858REM LH PCNTPK INT=0x60
> 
> So someone accidentally deleted a line break. It should read:
> REM CHCP 858
> REM LH PCNTPK INT=0x60

As it turns out, this is a minor installer bug I will fix. 

rem IF EXIST %DOSDIR%\BIN\DOSLFN.COM LH DOSLFN
$LANG_SET$
REM LH PCNTPK INT=0x60

Inserting the “REM” language settings drops the trailing CRLF. I 
never noticed it was doing that it will take care of it.

> 
> Bugs2
> The DHCP line won’t work as the C:\MTCP directory is not added to the PATH.
> The PCNTPK line will not work as C:\FDOS\DRIVERS\CRYNWR is not added to the 
> PATH.
> Would this be fixed in FDNPKG or in the installer?
> 
> Please add them to the PATH. Then remove the REM in both lines.

I think the best solution will be to relocate all networking stuff in the 
AUTOEXEC.BAT into
a separate batch file. Probably, NETSTART.BAT or STARTNET.BAT. Then, provide it 
as a 
separate package. 

Then in the AUTOEXEC, just test for its existence and run it if present. A user 
could easily
disable it by using a single REM or removing the package. 

> 
> Bug 3
> Loading high PCNTPK will not work with option 2. So remove the „LH“ in this 
> line.

Do you know why it won’t load high with option 2?

> 
> Bug 4
> DHCP will not work because there is no MTCP.CFG found in C:\FDOS\. 
> I suggest to copy the file SAMPLE.CFG in the MTCP.ZIP package from PROGS\MTCP 
> to the root as MTCP.CFG.
> This will make sure MTCP.CFG is installed in C:\FDOS. I have done that and 
> there is an updated version of MTCP.ZIP at: 
> https://www.lazybrowndog.net/freedos/files/mtcp.zip 
> 
> 
> 
> Now after "DHCP“ add another line for WATTCP autoconfiguration with DHCP
> C:\FDOS\BIN\M2WAT.COM 
> 
> Some things still have to be done manually by the user (configuring FTPSRV 
> password files, configuring VirtualBox to bridged networking) but it’s a big 
> step forward.

Thanks, 
Jerome

--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 Auto NET Config

[Jerome E. Shidel Jr.]

Hello all,

As you you may already know, we have been working on the FreeDOS 1.2 release. 
One thing I would like to see make it into the release is some networking. I 
don’t think it would be 
practical to have a universal setup for each and every machine and NIC at this 
time. But, it
may be possible to have the installer automatically do this for some of the 
known virtual machines.
For example, it may be feasible to setup and configure VMware, VirtualBOX and 
QEMU to do
networking. But, I don’t have the time to figure it all out. This is where all 
of you come in. 

If you can provide the detailed information for these platforms and Jim 
approves, I may then be 
possible to include it. 

Here are the main and mostly obvious requirements.

All files and drivers must have an acceptable license and can be 
redistributed. Public Domain, 
GPL, BSD or another open source or unrestricted license. No encumbered 
commercial drivers 
(such as NOVELL Netware, 3COM, NetGear, ….. ).

DHCP setup only.

Links to (or provide) any drivers and files that are required.
(It would be nice if they were in a FDNPKG compatible package)

Completely setup configuration files for the platform. (all INI, CFG 
files, etc)

List of any current 1.2 repo packages that may be needed (excluding 
BASE packages).

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/
 


Preferably, any files that are not in a package (like the config files) 
are placed under 
\NET\VMWARE, \NET\VBOX, \NET\QEMU or other appropriate directory for 
the platform.

Also, please do not provide a customized config.sys or autoexec.bat. It 
should be possible to
place all environment settings and load drivers from a 
\NET\STARTNET.BAT file. 

Thank you, Jerome

(Without your support, there is no way any type of pre-configured networking 
will make it into the next release.)--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] JEMM386

[Jerome E. Shidel Jr.]

> On May 17, 2016, at 7:08 AM, Tom Ehlert  wrote:
> 
>>> I saw in a recent post that JEMM386 has been removed from
>>> FreeDOS distributions, and perhaps from ibiblio, because 
>>> of license issues. 
>>> Would someone tell what is the problem with its licenses ?
>>> There may be some doubts about what part of it is GPL, 
>>> what is Public Domain and what is "artistic", but all sources 
>>> are available and any of the licenses allow  free copying, 
>>> distribution and modification.
> 
>> At present, JEMM386 has not been removed. It is part of the JEMM.ZIP package.
> 
>> However, there are possible issues that were mentioned regarding JLOAD and 
>> the *.JLM
>> files. Those parts need further review.
> 
> what are these issues? who did raise them?

Initial concerns were raised in these message:

https://sourceforge.net/p/freedos/mailman/message/35069920/
https://sourceforge.net/p/freedos/mailman/message/35088438/

> 
> review by whom?

This message discusses possible review and repair.

https://sourceforge.net/p/freedos/mailman/message/35088539/

> 
> 
> Tom


Jerome
--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] JEMM386

[Jerome E. Shidel Jr.]

> On May 16, 2016, at 7:51 PM, Jose Antonio Senna 
>  wrote:
> 
>  I saw in a recent post that JEMM386 has been removed from 
> FreeDOS distributions, and perhaps from ibiblio, because 
> of license issues. 
> Would someone tell what is the problem with its licenses ?
> There may be some doubts about what part of it is GPL, 
> what is Public Domain and what is "artistic", but all sources 
> are available and any of the licenses allow  free copying, 
> distribution and modification.

At present, JEMM386 has not been removed. It is part of the JEMM.ZIP package.

However, there are possible issues that were mentioned regarding JLOAD and the 
*.JLM
files. Those parts need further review.

> 
> 
> --
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Where are the FreeCOM Sources?

[Jerome E. Shidel Jr.]

Hello All, 

Jim said he wants all of the packages in FreeDOS 1.2 to include their sources.

Where are the latest 0.84 pre 2 (Or newer) FreeCOM sources?

The latest versions I see are on the old sourceforge site 0.82pl3.

Thanks, Jerome
--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 - Preview 17

[Jerome E. Shidel Jr.]

Hello all, 

I have just released Preview 17, http://up.lod.bz/FDI

This release contains:

* Minor package and data updates.
* Some internal improvements.
* Some VirtualBox compatibility updates.
* USB versions include FDIDEV.BAT to aid in 
  replicating the FDI Build Environment.

Other than Package and Package Data updates, no further updates are
planned for FDI before FreeDOS 1.2 Final.

Thanks, Jerome

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI - Wiki

[Jerome E. Shidel Jr.]

Hello all,

For those who are interested, I have been working on the FDI Wiki. It is not 
complete yet. However, It currently contains the everything you would need to 
know to build a FDI based FreeDOS release. Including, how to replicate the 
build environment, updating and adding packages and hanging release version 
numbers. All, of the basic stuff in the process is included. Advanced things, 
like customizing the theme and developing add-on user prompts and custom 
install processes, will come at later when I have the time. 

https://github.com/shidel/FDI/wiki

Some of the things, like setting up the Build Environment, are not nearly as 
bad as they look. I just tried to leave absolutely nothing out in the process. 

Thanks, Jerome
--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI Preview 15, Update 3

[Jerome E. Shidel Jr.]

Hello All,

Sorry that it took so long, but I have been swamped the last couple weeks. 

Anyhow, I updated vinfo in V8Power tools to detect QEMU. So, FDI should no 
longer get stuck by trying to create a RAMDRIVE or have issues under QEMU 
emulation.

Preview 15 Update 3 is now available at http://up.lod.bz/FDI

Thans for your patients, Jerome.

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI Preview 15, Update 2

[Jerome E. Shidel Jr.]

Hello All, 

I just pushed another minor update to Preview 15.

Changes:

- Typo correction on Partition Drive Screen.
- Automatic updating of installed FDNPKG.CFG drive letters to C:
(some were left pointing to D: after USB stick installation)

Thanks, Jerome

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Minor update to FDI Preview 15

[Jerome E. Shidel Jr.]

Oh, I also started including a VMDK file with the USB images to ease usage with 
virtual machines.
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Additional FDI translation text needed for included languages.

[Jerome E. Shidel Jr.]

Hello All,

There are a two of things that were recently added to the soon to 
be released and probably final preview of FDI #14 that could use 
translated into the included default languages (DE, EO, FR & NL).
Please remember, exact translation and wording is not important.
It is the concept the messages present that is relevant. The second
message is only shown when the user chose not to update the MBR
in advanced mode. Jim stated that he leans toward the installer 
always pushing new boot code into the MBR. So, starting in Preview 
14, this is how FDI will behave in normal mode. 

FreeDOS is a complete operating system. If you choose to install this on your 
computer, you may overwrite the operating system you have now (for example, 
Windows.) If this is not what you intend, please stop now.

Please note that you did not force an update of your MBR boot code. If you 
system fails to boot FreeDOS, please reboot using the install media and run 
‘MBRZAP.BAT’ to force new boot code to the MBR.

If you translate them and send them to me, I plug them into the 
appropriate FDI resource files. Please, remember to say what language 
is being translated. I probably could tell them apart. But…

Thanks again, Jerome
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI remaining issue

[Jerome E. Shidel Jr.]

> On Feb 23, 2016, at 2:34 PM, Maarten <netraa...@gmail.com> wrote:
> 
> I don’t have something to tell you about the problem, unfortunatly. But I 
> have something what might is an idea, but you all know that better then me.
>  
> Maybe we can provide an ‘upgrade’-installer and a System-installer. The 
> upgrade installer you just run from DOS os’s. If we can, we put both 
> installers in that setup image. But when the user chooses upgrade [1] you 
> copy the upgrade/update installer to the drive and you reboot the system, let 
> them run that installer. This solves the problem of drive letters, and is 
> simpler to run. You don’t need to run the setup installer, because this asks 
> you things you don’t need when upgrading your old FreeDOS and/or MS-DOS, 
> PC-DOS etc.
>  
> The system-installer would just be the FDI we all know. :)

I don’t think it would be needed. FDI detects wether or not a previous install 
is present. 
In normal mode. It will import language and the FreeDOS directory settings if 
present.
So, removes the Language screen automatically.

Says Welcome to installer, continue?
Asks if the user wants to back up old files?
Asks, base or full w/without sources?
Asks, if they are now ready to install just in case?
When done, asks if user wants to reboot?

I don’t see how a separate upgrade only version could reduce the number of 
questions or 
simplify the process for the user.

If the user is installing to a formatted but empty drive in normal mode:

Select language?
Welcome, continue?
Base or Full, w.without sources?
Do the install or quit?
Reboot or exit to DOS?

In advanced mode, the user gets to play “50 questions” because almost
nothing is assumed.


>  
>  
> [1] probably you need to prompt “This will upgrade you from any DOS OS. Setup 
> will copy the installer to your disk. To run type: ‘Upgrade’.”
>  
>  
> Maarten
>  
>  
>  
> Working on:
> Bird OS 2017 1.0.0a (Western Schreech-Owl)
>  
> Van: Jerome E. Shidel Jr. <mailto:jer...@shidel.net>
> Verzonden: dinsdag 23 februari 2016 19:19
> Aan: Technical discussion and questions for FreeDOS developers. 
> <mailto:freedos-devel@lists.sourceforge.net>
> Onderwerp: Re: [Freedos-devel] FDI remaining issue
>  
> I have a report of another issue regarding the USB stick installer.
>  
> Basically, the user has 2 drives. one MS-DOS and one Other DOS formatted.
>  
> The user boots the USB stick and all seems well through the install process. 
>  
> Reboots, and is faced with MS-DOS again. FreeDOS installed to D:.
>  
> After, a little back and forth, it turns out that when he boots the USB stick
> the USB stick is Drive C: and the other DOS drive is D:. The original 
> MS-DOS C: drive is nowhere to be found.
>  
> So, the installer behaves correctly. But, FreeDOS is not the boot drive. 
>  
> This appears to be completely BIOS related and I don’t think there is
> anything the installer can do about it. 
>  
> The solution was to to just boot MS-DOS and switch over to whatever
> drive letter the USB stick now has and run setup.bat. This method was 
> not optimal, but worked fine.
>  
> Like I said, I don’t think there is anything the installer can do about it. 
> But, it is something to be remembered.
>  
> Thanks, Jerome
>  
>  
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>  
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___
>  
> <http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___>
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net 
> <mailto:Freedos-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/freedos-devel 
> <https://lists.sourceforge.net/lists/listinfo/freedos-devel>

Re: [Freedos-devel] FDI remaining issue

[Jerome E. Shidel Jr.]

I have a report of another issue regarding the USB stick installer.

Basically, the user has 2 drives. one MS-DOS and one Other DOS formatted.

The user boots the USB stick and all seems well through the install process. 

Reboots, and is faced with MS-DOS again. FreeDOS installed to D:.

After, a little back and forth, it turns out that when he boots the USB stick
the USB stick is Drive C: and the other DOS drive is D:. The original 
MS-DOS C: drive is nowhere to be found.

So, the installer behaves correctly. But, FreeDOS is not the boot drive. 

This appears to be completely BIOS related and I don’t think there is
anything the installer can do about it. 

The solution was to to just boot MS-DOS and switch over to whatever
drive letter the USB stick now has and run setup.bat. This method was 
not optimal, but worked fine.

Like I said, I don’t think there is anything the installer can do about it. 
But, it is something to be remembered.

Thanks, Jerome


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI remaining issue

[Jerome E. Shidel Jr.]

Hello all, 

Preview 13 testing is still underway. So far, I have not received any reports of
major bugs or serious hiccups. However, there is one serious issue that is yet
to be resolved to my satisfaction. The MBR issue. When incompatible boot code 
already is present  or if the USB image is drive C: (targeting D:), post 
install 
fails to boot. Since it shouldn’t blast existing boot code, I guess the first 
situation 
is ok. However, the second is more tricky. Why is sys not updating the MBR?
If you force it with /BOOT or other option, you will run into the first problem.

As I see it, there are 4 solutions.

1) Don’t worry about it. Let the user fix it.
2) Write a program to figure out drive letter and test MBR, Blank force new, 
Exists leave it alone.
3) Like 2, except if it exists prompt user to blast it.
4) Don’t worry about it. But, always prompt user in advanced mode.


1 easiest solution

2 & 3 are a bit of a pain and require figuring out what drive and partition the 
kernel has assigned
to a specific drive letter. 

3 & 4 easy, but will require some more prompting and language translations.

Thanks in advance.

Jerome
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeCOM pipes

[Jerome E. Shidel Jr.]

> On Feb 16, 2016, at 12:23 PM, Matej Horvat <matej.hor...@guest.arnes.si> 
> wrote:
> 
> On 2016-02-16 3:06 PM, Jerome E. Shidel Jr. wrote:
>> When used at the tail of a pipe, if the set /p does not receive any
>> input, FreeCOM will basically crash. So, it would appear that
>> it receives the pipe and just fails to set the environment variable.
> 
> I can't reproduce this, at least not interactively. Does it only happen 
> in batch files?

I think it only happens in a batch file. 

It is very hard to reproduce. It only happens sometimes. Mostly, 
it seems to happen only after a write to the filesystem or a TEMP 
environment variable change or after lots of pipes + sets. It is very odd. 
Almost, like there is a buffer somewhere in the shell that takes a little 
while to update.  It will happen with or without a caching. (LBACACHE)

Mostly, it is just frustrating when doing lots of logic in a batch file. (like 
FDI)

> 
> You can also use:
> 
> SET /E PWD=CD
> 
> As described by "SET /?":
> "/E sets the given variable to the first line of output of the command 
> pointed to by [string].”

Never even though of /E. Maybe at some point, just to see if set /E has the 
same issue, I will swap out some of the /P stuff for /E and pull the 
“Workaround” 
failsafe checks out.

> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeCOM pipes

[Jerome E. Shidel Jr.]

While working on FDI, a while back I noticed something interesting.

Either FreeCOM pipes or it’s set /p command (or both) are flakey. I
think it is related to set /p.

I’ve worked around this issue in FDI. But, figured I would share what
I have discovered.

Take the following command:

cd | set /p PWD=

Sometimes it works, sometimes it doesn’t.

A workaround would be:

:TryAgain
cd | set /p PWD=
if “%PWD%” == “” goto TryAgain

Why do I think it is set /p?

When used at the tail of a pipe, if the set /p does not receive any
input, FreeCOM will basically crash. So, it would appear that
it receives the pipe and just fails to set the environment variable.

A work around becomes more tricky when the pipe could return
an empty string. 

But, like I have said. I have worked around this issue in FDI. 

Just thought I would share,

Jerome



--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2+ Preview 12 with Dimples

[Jerome E. Shidel Jr.]

Hello all,

Just released FDI Preview 12.

Some major non-UI underlying changes, for better performance and compatibility.
Too many improvements and far to many things to list. Hopefully, this will be 
the last 
preview before FreeDOS 1.2 beta. Next, I intend on looking through the package
lists and adding stuff to all and extras.

However, I mentioned dimples in the subject. I meant FDIMPLES. 
FreeDOS Installer - My Package List Editor Software. It is not 100% complete,
but it is fully integrated and works. Remember, you must be running the 
installer
in advanced mode for detailed package selections. You can enter advanced mode
by running “setup adv” or by pressing CTRL+C at any point the installer is 
waiting
on user input.

http://up.lod.bz/FDI 

Jerome--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK Update

[Jerome E. Shidel Jr.]

Hello Paul,

> On Feb 5, 2016, at 10:06 AM, Paul Dufresne  wrote:
> 
> I am a bit confused as to what is/should be the current version.
> 
> Antony Gordon said he made modifications to v. 1.2.1 and 1.3 but I
> don't know if the changes have been published and if so where.
> 
> Then there is (same code, two different categories):
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/disk/spfdisk
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/fdisk/spfdisk/
> Is that linked to 1.2.1 version that I have in 'fdi-setup' USB image preview?

I can’t speak to you other questions. But, regarding FDI-SETUP,
at present, all packages (except V8POWER and the WELCOME
message package) are pulled from Mateusz’ ALL_CD.ISO.
The Floppy image pulls them from that CD. The USB pulls
them from whichever version of that CD I am using. (Currently the
Jan 5, 2016 version)

I know this doesn’t really answer you question. But, I hope it helps.

Jerome

> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

> On Feb 2, 2016, at 7:28 PM, Rugxulo <rugx...@gmail.com> wrote:
> 
> Hi,
> 
> (I'll respond quickly here even though there's a billion follow-up
> responses already.)
> 
> 
> On Mon, Feb 1, 2016 at 6:10 PM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> wrote:
>> 
>>> On Feb 1, 2016, at 6:17 PM, Rugxulo <rugx...@gmail.com> wrote:
>>> 
>>> On Mon, Feb 1, 2016 at 9:25 AM, Jerome E. Shidel Jr. <jer...@shidel.net> 
>>> wrote:
>>>> 
>>>> I just the FreeDOS 1.2 Installer Preview 11.
>>>> 
>>>> Also, a more permanent USB stick image url location.
>>>> There is a link to it on the FDI download page.
>>> 
>>> I just downloaded the FDI-USB.ZIP file (now 178 MB .ZIP'd, unpacks to
>>> 256 MB .img).
>> 
>> Yeah, It’s a little big. But, on the other hand it is really hard to find
>> a USB stick under 512mb. So, other than download size, it isn’t to
>> important. However, that being said. It should be under 100mb
>> for individuals who have very limited or expensive bandwidth.
> 
> I just don't think most people downloading FreeDOS really need FPC or
> FBC or DJGPP (even if I do like them). I think they can just grab them
> separately. But OW and NASM are officially recommended and much
> smaller, so to those I have no complaints.
> 
>>>> Moved CD driver from Installed FDCONFIG.SYS to AUTOEXEC.BAT
>>> 
>>> But LBACACHE now loads before UDVD2 and FDAPM, so you still can't
>>> unload it.   :-(
>> 
>> But, it is the installers boot media. Not the installed system. Does it 
>> matter?
>> 
>> I will move it just for you. But, I’m curious why you really want to be able 
>> unload it.
>> 
>> So for the next release, I have set DOSLFN to load second to last.
>> Then finally, LBACACHE.
> 
> Sigh, no, I misunderstood that, sorry.
> 
> Of course you don't need to unload on the installer boot media. I just
> meant in general that it made no sense (to me) why you wouldn't at
> least give the user the option to unload later, if needed. It's easy
> to miss details like that, so I was just mentioning it for
> completeness.

No problem. I was a little perplexed as to why you were so insistent.
Now, it makes sense to why you kept bringing it up. Just as an 
fyi, I moved it on the boot media anyway. 

:-)

> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

> On Feb 2, 2016, at 7:39 PM, Eric Auer  wrote:
> 
> 
> Hi!
> 
>> I just don't think most people downloading FreeDOS really need FPC or
>> FBC or DJGPP (even if I do like them). I think they can just grab them
>> separately. But OW and NASM are officially recommended and much
>> smaller, so to those I have no complaints.
> 
> FreeBasic has a rather cool QB compatibility mode and some
> software in the FreeDOS distro is compiled with DJGPP, but
> of course without the tons of add-ons available for DJGPP.
> 
> Not sure which coolness factor FreePascal has, but Pascal
> certainly was a classic programming language of DOS users.

I agree with Pascal being a classic and very traditional language and
even if it is not installed I would like to see it ship on the install
media. 

But, if Jim wants the USB and ISO to be as slim as possible (no extras) and
it doesn’t become part of ALL, I will sadly pull it without complaint. :-(

> 
> Cheers, Eric
> 
> 
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Roll your own FreeDOS 1.2+

[Jerome E. Shidel Jr.]

Hello all, 

I have created a youtube video that demonstrates how to 
create your own custom FreeDOS 1.2+ installation Floppy and
USB stick images. 

It demonstrates the complete process from scratch, includes what you need to 
download, how to configure the build environment inside VirtualBOX, changing the
included extra packages, customizing the OS version and all the way to having 
the both the Floppy and USB stick images.

https://youtu.be/9daLiLdG6SM 

You could also modify the to be installed AUTOEXEC.BAT and FDCONFIG.SYS files
that are located under \FDSETUP\SETUP in the FDI source as *.DEF files.

The \FDSETUP\AUTOEXEC.BAT and \FDSETUP\FDCONFIG.SYS contain the boot
configuration files for the installer images themselves. 

Enjoy,

Jerome--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

> On Feb 1, 2016, at 12:13 PM, Paul Dufresne  > wrote:
> 
> I just wrote (DD in Linux) the FDI-USB .IMG file on an USB-KEY.
> Think this was my first try to boot FreeDOS on USB key.
> Boots fine (once adjusted in BIOS).
> 
> Suprise 1) Unable to select a language different than english.
> Others are shown, but key down does not move to others.
> Did not was able (or really try) to go around that.

Oops, sorry. I don’t know why I did it. Somehow, how I managed to remove a 
line from mkFDI.bat that dynamically generates that section of code for the
installer. Since, I only use English I don’t notice. Fixed it.

> 
> Surprise 2) FDISK was at first showing the C: as the USB-Key. (LABEL
> FDI-SETUP as I remember).
> But there is an option in FDISK to change drive. Worked well.
> I stopped there because I did not really want to install on that computer.

USB as drive C and install to D is fine. So far,
I’ve had two people tell me that booting on USB was C: and 
one that it was L:.  The new way FDI does the detection stuff 
should be fine. 

But, you are correct with the default for FDISK. So, added stuff
so FDISK would select D (drive 2) at start when USB is C:

I have made both changes and pushed the updates online for 
download at http://up.lod.bz/FDI 


> 
> Might try later for real on an other.
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140 
> 
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net 
> 
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

A side note to ALL, regarding what packages are included.

There is really no reason you cannot make your own personal customized FDI 
based release.

Two ways to do it.

The easy way:

For Floppy Image, just modify the package list files 
A:\FDSETUP\SETUP\*.LST. 
It will then include or exclude them. 

For USB image, same as above and also add and remove the packages.

The harder, but much better way, 

Create a Virtual Machine in VMware Fusion or other compatible Virtual 
Machine.

Create, two virtual flat hard disk images. First will be for the USB 
image. Second
 is a TEMP drive. Also, add a virtual CD and virtual floppy.

Boot the latest FDI floppy image. Exit the installer.

FDISK and Format both Hard Drives. (all re/boots should be done from 
FDI floppy)

Download FDI source from github and v8power tools from up.lod.bz.

Place FDI source files in D:\FDI

Place V8Power Binaries in D:\FDI\V8POWER

Create a TEMP directory on drive D: Set the Temp:

Edit the package list files in D:\FDI\SETTINGS

Change to D:\FDI

Insert repository CD image.

run mkfdi.bat

(This will turn the floppy in drive A: into the latest  version)

run mkfdi.bat usb

(this with turn drive C into the USB image)

Maybe, I will do a youtube video to demonstrate the second method. 

With the second version, you slim down or really beef up the install.
Make nearly any size USB stick. Etc.



--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

> On Feb 1, 2016, at 7:55 PM, Eric Auer  wrote:
> 
> 
> Hi :-)
> 
>>> I just downloaded the FDI-USB.ZIP file (now 178 MB .ZIP'd, unpacks
>>> to 256 MB .img).
> 
>> Yeah, It’s a little big. But, on the other hand it is really hard to find
>> a USB stick under 512mb. So, other than download size, it isn’t to
>> important. However, that being said. It should be under 100mb
>> for individuals who have very limited or expensive bandwidth.
> 
> The traditional answer would be to have a separate download which
> contains only the BASE packages and whatever is needed to install,
> such as UNZIP and the package manager :-) I would still like to
> hear what the largest packages in FDI-USB are and which packages
> of which size from Mateusz' 500 MB repository are still missing.

Many things are not included. 

Here are the current included Extra packages that are included. But,
not installed with either BASE or ALL. At present, they have not all
been verified as being able to ship with FreeDOS.

> 
> Having a separate download would make it easy for people to either
> enjoy ALL Mateusz' packages on a 500+ MB size stick without having
> to worry about DOS networking drivers (do you include ANY yet?) and
> at the same time make things quick and easy for others who simply
> want a basic install of DOS with a quick download :-)

I do get what you are saying here, 

I really don’t have the time to go through every package in his repository 
to verify they are appropriately licensed to be be included with the FreeDOS.

  1.0M Dec  4 09:36 ansimat.zip
   23K Dec  4 09:40 b64.zip
  477K Apr  5  2009 biew.zip
   89K Aug  7  2013 cpied.zip
  690K Apr  5  2009 curl.zip
  1.5M Dec  5 04:31 djgpp.zip
  5.0M Dec  4 10:11 djgpp_bn.zip
  414K Dec  5 04:33 djgpp_bs.zip
  4.7M Dec  5 04:33 djgpp_db.zip
  666K Dec  4 10:14 djgpp_fq.zip
  191K Dec  4 10:15 djgpp_fx.zip
   12M Dec  4 10:16 djgpp_gc.zip
  270K Dec  4 10:19 djgpp_mk.zip
   11M Dec  4 10:20 djgpp_ob.zip
  6.0M Dec  4 10:21 djgpp_rh.zip
  1.0M Dec  5 04:33 djgpp_tx.zip
  368K Dec  4 10:24 dos32a.zip
   29K Sep 22  2012 dosidle.zip
  376K Feb 17  2013 fasm.zip
   14M Dec  4 06:01 fbc.zip
  856K Dec  4 10:53 fbc_help.zip
   37M Dec  4 11:03 fpc.zip
  4.8K Dec 30  2008 gcdrom.zip
  231K Feb  1  2013 grep.zip
  1.4M Dec  4 11:15 jwasm.zip
  303K Feb  1  2013 less.zip
  139K Jun 17  2015 md5sum.zip
  1000 Jun 22  2015 mtcp.zip
  2.5M Jan  4 13:36 nasm.zip
  3.3M Dec  4 13:50 opengem.zip
   14M Jul 27  2014 ow.zip
  1.3M Dec  4 06:27 ozonegui.zip
  169K Apr  5  2009 part.zip
   26M Dec  4 13:57 perl.zip
  583K Dec 27 13:03 pgme.zip
  181K Nov 29 11:22 picosntp.zip
  597K Dec  4 13:35 picotcp.zip
  638K Jun 23  2013 ping.zip
  1.1M Dec  4 13:49 rsync.zip
   23K Feb 22  2009 search.zip
  3.8K Sep 22  2012 slowdos.zip
   28K Aug 16  2013 tinyaes.zip
  1.9M Dec  4 06:58 unrtf.zip
  1.9M Dec  4 12:24 upx.zip
   19K May 10  2015 utf8tocp.zip
  140K Jul 16  2013 vmsmount.zip
  551K Dec  5 04:36 vncview.zip
  2.3M Dec  4 07:05 wget.zip
   40K Apr  4  2009 xcdrom.zip
  180K Apr  5  2009 xfdisk.zip

> 
>>> 147 MB of "DEVEL"??? Uh ... maybe I could sympathize with OW.ZIP and
>>> NASM.ZIP (which total "only" 18 MB), but all of the rest is too
>>> obscure (relatively speaking) for most developers.
> 
> Hm? Are the "obscures" large? Are FPC, FreeBasic, DJGPP obscure?
> 
>>> But LBACACHE now loads before UDVD2 and FDAPM, so you still can't
>>> unload it.   :-(
>> 
>> But, it is the installers boot media. Not the installed system. Does it 
>> matter? 
> 
> Not really. Yet I agree that it is better to load FDAPM early ;-)
> 
>> The issue is not being able to check for available free space. I just don’t
>> see it as really being worth the overhead and additional complexity.
> 
>>  FDI starts, tests if there is enough freespace for minimum install.
>>  YES, continue, No, check if there would be enough if current version is 
>> removed.
>>  If not, stop telling user not enough space.
> 
> You could make it simpler: If there is enough space to install (make
> a base / all distinction) without deleting anything, be happy. If you
> have less space, warn the user: They MIGHT be able to install stuff,
> because the install will overwrite some old versions with newer ones,
> but they continue at own risk. Give the user a rough idea of free size.
> 
>>  If user wants to make a backup, make sure there will be enough room for 
>> that
>>  an the minimal install.
> 
> Can we assume that stuff is moved to backups, instead of adding backup
> size to the amount of already used disk space?
> 
>>  Based on package selection, make sure there will be enough room for that
>>  the backup.
> 
> I had the impression that you wanted to avoid individual package choices
> to keep the install simple? Of course the package manager can always be
> smart and ponder how much space is consumed by installing [list of some
> packages] but for the moment, I guess knowing how large 

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

> On Feb 1, 2016, at 6:17 PM, Rugxulo <rugx...@gmail.com> wrote:
> 
> Hi,
> 
> On Mon, Feb 1, 2016 at 9:25 AM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> wrote:
>> 
>> I just the FreeDOS 1.2 Installer Preview 11.
>> 
>> Also, a more permanent USB stick image url location.
>> There is a link to it on the FDI download page.
> 
> I just downloaded the FDI-USB.ZIP file (now 178 MB .ZIP'd, unpacks to
> 256 MB .img).

Yeah, It’s a little big. But, on the other hand it is really hard to find
a USB stick under 512mb. So, other than download size, it isn’t to
important. However, that being said. It should be under 100mb
for individuals who have very limited or expensive bandwidth.

> 
>> Extra (not BASE or ALL), uninstalled packages on USB image. (about 50 extra)
> 
> 147 MB of "DEVEL"??? Uh ... maybe I could sympathize with OW.ZIP and
> NASM.ZIP (which total "only" 18 MB), but all of the rest is too
> obscure (relatively speaking) for most developers. There aren't enough
> active projects using the others to justify forcing it on all FreeDOS
> downloaders. (I take it back, DJGPP *is* useful, but there are so many
> "competing" versions that it's hard to know what to use sometimes.)
> 
> Unfortunately, anything you give here is either too much or too
> minimal. Even limiting only to DJGPP mini-FAQ tools would be quite
> large (well, especially since later GCC versions are even bigger).
> What to do, stick to a classic like 3.46? Or my own home-rolled
> "EZ-GCC v2" (2.95.3)?
> 
> Ugh, no easy answer. Without any obvious goal, I would just omit
> everything except OW and NASM. Is anyone here (or elsewhere?) actively
> fighting to keep others included here?? If not, then why include them?
> Maybe I'm overthinking things (again).

I hear you there. If the EXTRA stuff was completely removed, their
would be complaints over not just putting them on the install media.
If I leave them in, complaints about total size of the image.

So, I’ll try to pick something in the middle to make everybody unhappy.

Just kidding :-)

> 
>> Moved CD driver from Installed FDCONFIG.SYS to AUTOEXEC.BAT
> 
> But LBACACHE now loads before UDVD2 and FDAPM, so you still can't
> unload it.   :-(

But, it is the installers boot media. Not the installed system. Does it matter? 

I will move it just for you. But, I’m curious why you really want to be able 
unload it.

So for the next release, I have set DOSLFN to load second to last. 
Then finally, LBACACHE.

> 
>> TODO: Sufficient free space is not verified prior to installation.
> 
> Would this help?

The issue is not being able to check for available free space. I just don’t
see it as really being worth the overhead and additional complexity.

example:

FDI starts, tests if there is enough freespace for minimum install.
YES, continue, No, check if there would be enough if current version is 
removed.
If not, stop telling user not enough space.

If user wants to make a backup, make sure there will be enough room for 
that
an the minimal install.

Based on package selection, make sure there will be enough room for that
the backup.

With all appropriate screens, message and such in multiple languages.

Or: 
Just test for Max install size + backup size.

Or: 
Just note at download time, full installation + backup will require NNN 
mb of free 
space. 

> 
> http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/free-disk-space-tester-freetest.zip
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 Preview 11

[Jerome E. Shidel Jr.]

I just the FreeDOS 1.2 Installer Preview 11. 

http://up.load.bz/FDI/latest 

Also, a more permanent USB stick image url location. 
There is a link to it on the FDI download page. Or,
just use the direct link  http://dnld.lod.bz/FDI-USB.zip 


What’s in Preview 11.

Improved BOOT from any USB stick at any drive letter (A, B, C, D, E….)

Improved Installation Target Detection. (C or D)

Extra (not BASE or ALL), uninstalled packages on USB image. (about 50 
extra)

Welcome to FreeDOS message, converted to a installed package with NLS.
(removed language specific messages from autoexec.bat)

V8Power Tools, converted to package like any other that gets installed 
with ALL.

Additional, BOOT menu item installed (DOS low - SAFE MODE)

Moved CD driver from Installed FDCONFIG.SYS to AUTOEXEC.BAT

Other minor improvements.

What is NOT in Preview 11. (Maybe 12, beta or not at all)

Boot sector is not overwritten with boot code if it happens to be 
missing.

Sufficient free space is not verified prior to installation.

Language specific COMMAND.COM is installed. But, it is not configured 
as default.

Language specific FDCONFIG.SYS menu items.


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 Packages

[Jerome E. Shidel Jr.]

Later today (EDT), I plan on have Preview 11 done. There may be
a Preview 12 before the FreeDOS 1.2 Beta. There may not.
So far, I’ve made several changes and improvements to
the soon to come Preview 11. They include:

Improved USB stick drive letter booting and general handling.

Removed special screens for installing V8Power Tools. It 
is now just another package in ALL.

Created another build related package list. SETTINGS\PKG_XTRA.LST.
It is not used by FDI. It is used by the mkFDI.bat build utility. It
contains a list of packages that will not be installed in either
BASE or ALL. However, they will be included in USB and ISO 
images. 

Some other mkFDI.bat improvements.

Anyhow, here is the current ALL and XTRA.LST packages. Let me know
if there are any more additions you wish to see. For reference, you can
see a list of available packages on Mateusz’ repository at:

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/listing.txt
 


Also, you may wish to examine the package list for the stuff that is used
by the FDI boot media.

FDI Boot Disk Image:
https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_FDI.LST 
 

BASE Install Packages:
https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_BASE.LST 


ALL Install Packages: (includes BASE)
https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_ALL.LST 


util\v8power
util\4dos
util\doslfn
util\fdnpkg
util\memtest
util\bootfix
util\shsufdrv
util\cwsdpmi
archiver\zip
archiver\unzip
util\grep
util\tee
util\touch
util\which
util\pg
archiver\tar
archiver\gzip
archiver\bz2

EXTRA included but not installed Packages:
https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_XTRA.LST 


net\mtcp
devel\nasm
devel\fpc
devel\ow
net\wget
net\rsync
net\curl


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI USB stick

[Jerome E. Shidel Jr.]

> On Jan 28, 2016, at 1:52 AM, Louis Santillan  wrote:
> 
> Well...so I finished my testing late last night with the MSI Wind Netbook.  I 
> ran into an issue the MBR was never updated by FDI 1.2. :/  Figured it out 
> eventually.  You can read more about it here [0].  There's pictures and video.
> 
> Now, I need to produce an ISO now for the eMachines M6805 I have (no support 
> for USB flash drive boot; tried several BIOSes).
> 
> [0] https://sites.google.com/site/lpsantil/fdi12-msi-wind

Just watched your video. The USB stick ran very nicely on your hardware. 
And you page was nicely detailed on the install process. Well done.

Just a couple notes, that don’t really matter.

That was pre10 not pre6. (Hopefully, I will have time to push pre11 tomorrow)

The forcing the stick to be treated as drive A: caused the boot errors when 
you were trying to fix the boot loop issue. (Hope to implement a cure for the 
boot errors in  pre11)

The MBR boot code issue. Yeah, I know. It just seems to be like others have 
mentioned.
If you replace it, you may be breaking stuff. If you don’t replace it, it may 
not boot.
Maybe, I will add an option to FDI in advanced mode to force a MBR boot code 
update
in some future pre or beta release of FDI. Or, if I have the time, I might add 
a check for
MBR boot code in V8Power Tools.

You didn’t try advanced mode? (either by manually launching as "setup.bat adv” 
or
pressing CTRL+C at any of the choice boxes)

> 
> On Tue, Jan 26, 2016 at 11:22 PM, Louis Santillan  wrote:
> Is there an ISO yet of FDI/FD 1.2preX?  Forgot that M6805 has a broken BIOS 
> wrt to USB boot.
> 
> On Tue, Jan 26, 2016 at 8:07 PM, Rugxulo  wrote:
> Hi,
> 
> On Tue, Jan 26, 2016 at 5:58 PM, Jerome Shidel  wrote:
> >  Hello Eric and all,
> >
> > A little more follow up on the USB stick test.
> >
> > The same user who was testing, per my suggestion ran it in advanced mode to 
> > override
> > the automatic D: drive as the install target. He said the install ran 
> > flawlessly when he
> > set it to C:\FDOS.
> >
> > He did say that he had an issue booting it. And basically, it seems to be 
> > issues with the
> > FDCONFIG paths. So, I will have to see if I can get FreeDOS to boot and 
> > load drivers from
> > an unknown drive letter. FDI doesn't care what drive it is running on. The 
> > wrong target
> > issue was an assumption I made and will fix.
> 
> Just remove all mentions of absolute drive letters (in FDCONFIG.SYS)
> entirely. It should still work. "DEVICE=\FDOS\HIMEMX.EXE" That's what
> I did with my MetaDOS floppy image, and it works (once extracted) atop
> (RUFUS-made) USB as "C:" or floppy as "A:".
> 
> > It appears that if I get the booting from G or L or X  to work, a USB 
> > stick installer may be viable.
> 
> Not all USB sticks are bootable, but most are. Plus, old machines
> (like my P4) need help (e.g. PLoP boot manager first, which makes it
> read-only, which isn't ideal but far better than nothing). We always
> have third-party things like RUFUS or UNetBootIn, too.
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI USB stick

[Jerome E. Shidel Jr.]

> On Jan 28, 2016, at 7:15 PM, Louis Santillan  wrote:
> 
> I used the default, minimal install.  No updates to autoexec.bat/config.sys.  
> That's a Jerome question.

Ok.

> 
> On Thu, Jan 28, 2016 at 4:03 PM, Rugxulo  wrote:
> Hi,
> 
> On Thu, Jan 28, 2016 at 12:52 AM, Louis Santillan  wrote:
> >
> > Well...so I finished my testing late last night with the MSI Wind Netbook.
> > I ran into an issue the MBR was never updated by FDI 1.2. :/  Figured it out
> > eventually.  You can read more about it here [0].  There's pictures and
> > video.
> 
> Very nicely documented, BTW.
> 
> N.B. "Destined for Chromixium 1.5.", see DistroWatch news ("Chromixium
> changes its name"; Cub Linux due in May 2016):
> 
> http://distrowatch.com/weekly.php?issue=20160125#news
> 
> > Now, I need to produce an ISO now for the eMachines M6805 I have (no support
> > for USB flash drive boot; tried several BIOSes).
> >
> > [0] https://sites.google.com/site/lpsantil/fdi12-msi-wind
> 
> I question the wisdom of putting LBACACHE in FDCONFIG.SYS at all. I
> see you're using INSTALLHIGH, which I guess? would save a bit of
> environment space. But that's outweighed by the 10 kb (or more!) that
> you can't "STOP" (unload) later (without rebooting).
> 
> Granted, you have 59 bytes free (577 kb), so maybe it's moot. Most
> people will never need more than that. At least you can unload DOSLFN
> to gain back 12 kb more, so maybe I'm overreacting here. Just normally
> I put as much unloadable stuff last, if possible.

I will probably move it to the AUTOEXEC. I may move the CD/DVD driver there
as well. Even though the USB image doesn’t need it, It may be useful to keep it
on the image for recovery or repair purposes.

> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI and FreeDOS 1.2

[Jerome E. Shidel Jr.]

Personally, I would like BASE to be more or less a minimum viable OS install 
and ALL to be a most likely 
wanted install. 

When I say minimum viable I mean: kernel, freecom, xcopy, deltree, move and a 
few other more or less
absolutes. 

However, by my understanding of what Jim wants. BASE is supposed to be 
equivalent to to what 
was provided with MS-DOS. 

For us dev types, it is very easy to make a custom package set for FDI or to 
just
roll your own installer. 

> On Jan 26, 2016, at 6:46 AM, Antony Gordon  wrote:
> 
> Hi,
> 
> Exactly. If you want networking, install it afterwards. The same for sound, 
> the myriad of development choices and memory managers. Despite wanting to 
> emulate DOS, it seems FreeDOS more closely emulates a Linux distribution from 
> the verbose initial boot to the "package" selection.
> 
> 
> On Tue, Jan 26, 2016, 6:33 AM Mateusz Viste  wrote:
> On 26/01/2016 12:10, Antony Gordon wrote:
> > Things would be so much simpler if FreeDOS emulated the Microsoft and
> > IBM (and Caldera, Digital Research) counterparts and installed the base
> > operating system.
> 
> I second that. But it would seem we are isolated in this opinion, since
> I see all the time people talking about multiple-choice packages,
> "advanced" modes, "FULL 400M+ install", etc...
> 
> What I'd love, as a user, is to be able to put the FreeDOS install CD
> (or floppy) into my computer, select a single choice "Yes, I want to
> install FreeDOS even though it means all existing data will be wiped
> out", and get a FreeDOS shell seconds later. A shell that mimicks what
> MS-DOS 6.x provided. And only THEN, if I wish/need, I'd install
> additional stuff using FDNPKG and/or FDINST.
> 
> Mateusz
> 
> 
> 
> 
> > On Sat, Jan 23, 2016, 7:31 PM Ralf Quint  > > wrote:
> >
> > On 1/23/2016 3:45 PM, Rugxulo wrote:
> >  > Hi again, quick reply,
> >  >
> >  > On Sat, Jan 23, 2016 at 5:43 PM, Rugxulo  > > wrote:
> >  >> On Sat, Jan 23, 2016 at 12:44 PM, Ralf Quint
> > > wrote:
> >  >>> On 1/22/2016 3:36 PM, Eric Auer wrote:
> >  >>> BWBasic is an interpreter, which runs very well on FreeDOS,
> > despite some
> >  >>> shortcomings, hence should be very well kept within ant FreeDOS
> > "distro"...
> >  >> IMO, it was too buggy to use for much.
> >  >
> > Well, fix it. It's Open Source
> >
> > Ralf
> >
> 
> 
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI and FreeDOS 1.2

[Jerome E. Shidel Jr.]

At present, BASE is fairly close to the 1.1 BASE. Of course, it no longer 
includes XMGR and UIDE.
this is the current ALL packages that are installed. Pull rdisk? Anything else?

https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_BASE.LST

Please note, that FDI’s floppy boot image needs a CD/DVD driver and it is 
currently using UDVD2.

These are the current additions that are installed when ALL is selected:

util\v8power

net\mtcp
util\4dos
util\doslfn
util\fdnpkg
util\memtest
util\bootfix
util\shsufdrv
util\cwsdpmi
archiver\zip
archiver\unzip

util\grep
util\tee
util\touch
util\which
util\pg

archiver\tar
archiver\gzip
archiver\bz2

devel\nasm
devel\fpc
devel\ow

net\wget
net\rsync
net\curl

Add or remove anything else?

Jerome





--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] V8Power Tools install?

[Jerome E. Shidel Jr.]

At present, V8Power tools (package) installs it’s executables to the 
%DOSDIR%\V8POWER directory.

Do you think that they would be better suited to be installed in the 
%DOSDIR%\BIN directory.

Remember, these are batch file enhancement utilities and must be able to be 
found by any batch file
that would wish to use them. So, either location is good. But, it needs to be 
finalized.

Thoughts?

Jerome
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Welcome to FreeDOS n.n

[Jerome E. Shidel Jr.]

Hello again,

I was thinking of pulling the “autoexec & config loaded", "Welcome to FreeDOS” 
and "type help” messages out of the AUTOEXEC.BAT file and placing them in a
%DOSDIR%\BIN\WELCOME.BAT file with the language translation files in 
%DOSDIR%\NLS\WELCOME.%LANG%. Also, installing them via a WELCOME.ZIP 
package. At present, FDI embeds the required stuff into a newly created 
AUTOEXEC.BAT.

1) This would make the AUTOEXEC.BAT file a little cleaner with just a:

if exist %DOSDIR%\BIN\WELCOME.BAT CALL %DOSDIR%\BIN\WELCOME.BAT

2) Easily remove the messages with a "fdinst remove welcome” command.

Thoughts?

Jerome
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI, updated

[Jerome E. Shidel Jr.]

I forgot something in the old (10 minute ago release).
So, i just put up another FDI update.

http://up.lod.bz/FDI/latest

Also, if someone wants to see if the USB stick image thingy works. 
(I have no way to boot it at present)

http://up.lod.bz/FDI-USB.zip





--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI and FreeDOS 1.2

[Jerome E. Shidel Jr.]

Hello Tom,

> On Jan 22, 2016, at 3:28 PM, Tom Ehlert <t...@drivesnapshot.de> wrote:
> 
> Hallo Herr Jerome E. Shidel Jr.,
> 
> am 22. Januar 2016 um 20:33 schrieben Sie:
> 
>> I emailed with Jim the other day. He is extremely busy at present.
>> However, he stated that he wished to get FreeDOS 1.2 out the 
>> door very soon. He did mention some reasons for getting it 
>> released. But, I’m not going to go into them. 
> 
>> I see no reason why a beta release is not ready in the next
>> few days-weeks. So, I highly recommend taking a look at the
>> package list files and making any requests you may have for 
>> additions or removals.
> 
>> https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_BASE.LST
>> https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_ALL.LST
> 
>> Also, Option 1 in the FDCONFIG.SYS file that FDI creates has issues 
>> with VirtualBOX. Someone who is more up to date on the memory 
>> managers should do an install and take a look at the config files. Then,
>> let me know what needs changed. Otherwise, It won’t get fixed.
> 
>> FDI status update:
> 
>> It is still finished. However, I just implemented a couple changes:
> 
>>Removed the XMGR
> if YOU feel like it; seems you are the new boss here
> 
> 
>>and UIDE packages.
> that sounds like a very bad idea

Well, I can be bossy, but usually I’m just really pushy. :-)

Jim said he wanted XMGR and UIDE pulled from the next release. 
I think it may be due to obscure legal reasons. But, you would have to
ask him. 

> 
> 
> regarding ALL:
> 
> ping, wget and possibly some more belong to the same package as mtcp,
> but only make sense if you also install some package drivers.
> same for rsync and curl

Ah, I didn’t realize ping was in mtcp. Pulled.
I don’t see wget in there, just htget.

what package for drivers?

> which is afaik included in command.com <http://command.com/>, at least the 
> one I have
> 
> I'd put doslfn in the base package

I thought base was supposed to be as close to MS-DOS as possible.
However, if Jim says OK, I will put it in there.

> 
> Tom
> 
> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140 
> <http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140>
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net 
> <mailto:Freedos-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/freedos-devel 
> <https://lists.sourceforge.net/lists/listinfo/freedos-devel>
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI and FreeDOS 1.2

[Jerome E. Shidel Jr.]

I emailed with Jim the other day. He is extremely busy at present.
However, he stated that he wished to get FreeDOS 1.2 out the 
door very soon. He did mention some reasons for getting it 
released. But, I’m not going to go into them. 

I see no reason why a beta release is not ready in the next
few days-weeks. So, I highly recommend taking a look at the
package list files and making any requests you may have for 
additions or removals.

https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_BASE.LST
https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_ALL.LST

Also, Option 1 in the FDCONFIG.SYS file that FDI creates has issues 
with VirtualBOX. Someone who is more up to date on the memory 
managers should do an install and take a look at the config files. Then,
let me know what needs changed. Otherwise, It won’t get fixed.

FDI status update:

It is still finished. However, I just implemented a couple changes:

Removed the XMGR and UIDE packages.

Added a few other packages to the ALL package list.

Slightly improved batch file start up DOSDIR and TEMP dir 
detection and configuration. (when present)

Modified a couple lines in the installer. So, that regardless of what 
drive FDI installs to, the boot files are configured to be booting from 
drive C:.

Modified mkFDI to create both Floppy Installer Image for CD Media
and Hard disk image for USB stick installer.

Modified mkFDI to adjust some configuration stuff for different
installer images.

Updated FDI, so when booting from USB/HD image it assumes
default target for install is drive D: (config files will be set for C: 
booting)

A couple other minor things.

I have tested the USB stick image as a hard drive and it works fine. However,
I have no way at present to boot from a DOS formatted USB stick. So, I have 
not uploaded the USB version.

Latest FDI image: http://up.lod.bz/FDI/latest

Jerome


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI and FreeDOS 1.2

[Jerome E. Shidel Jr.]

> On Jan 22, 2016, at 4:25 PM, Rugxulo <rugx...@gmail.com> wrote:
> 
> Hi,
> 
> On Fri, Jan 22, 2016 at 1:33 PM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> wrote:
>> 
>> I see no reason why a beta release is not ready in the next
>> few days-weeks. So, I highly recommend taking a look at the
>> package list files and making any requests you may have for
>> additions or removals.
>> 
>> https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_BASE.LST
> 
> "base/rdisk" and "util/udvd2”??

rdisk, because it was there before. (i think)
(but, the shsufdrv seems to work easier)

udvd2, for carom driver support. replacing uide.

> 
> (probably both belong in "util\", but why listed at all in PKG_BASE.LST ??)

(It’s where Mateusz has them on his repo)
(rdisk, ??, udvd2 for working cd/dvd drive, hopefully)

> 
>> https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_ALL.LST
> 
> "; The remaining packages are only installed when ALL is chosen."
> 
> util\cwsdpmi
> archiver\zip
> archiver\unzip
> 
> I can't speak for Jim. For a minor point release like 1.2, he doesn't
> want any major changes. But seriously, it's VERY hard to live without
> these.
> 

Agreed.



--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI and FreeDOS 1.2

[Jerome E. Shidel Jr.]

> On Jan 22, 2016, at 4:25 PM, Rugxulo <rugx...@gmail.com> wrote:
> 
> Hi,
> 
> On Fri, Jan 22, 2016 at 1:33 PM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> wrote:
>> 
>> I see no reason why a beta release is not ready in the next
>> few days-weeks. So, I highly recommend taking a look at the
>> package list files and making any requests you may have for
>> additions or removals.
>> 
>> https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_BASE.LST
> 
> "base/rdisk" and "util/udvd2"??
> 
> (probably both belong in "util\", but why listed at all in PKG_BASE.LST ??)
> 
>> https://github.com/shidel/FDI/blob/master/SETTINGS/PKG_ALL.LST
> 
> "; The remaining packages are only installed when ALL is chosen."
> 
> util\cwsdpmi
> archiver\zip
> archiver\unzip
> 
> I can't speak for Jim. For a minor point release like 1.2, he doesn't
> want any major changes. But seriously, it's VERY hard to live without
> these.
> 
> "; Some packages I would like to see in ALL."
> 
> (so you want more premade package .ZIPs from us?? or just
> reclassification of where to put them??)

That section is basically just the packages I felt should be also installed 
when 
“ALL” is chosen. 

> 
> "util\grep" and "util\xgrep" (what's the difference?? 32-bit DJGPP version??)

Someone mentions, why not xgrep too. Pulled.

> 
> util\less (386+ DJGPP unless you want ancient 16-bit GNUish version)
> 
> I assume it is practically recommend to use "util\pg" instead of "util\less".
> 
> util\tee
> util\touch
> util\which
> 
> Not sure how majorly useful these are for most people (e.g. I hardly
> ever use them), but they wouldn't be hard to package up. Besides,
> FreeCOM has a (limited, not as good) built-in "WHICH".
> 
> archiver\tar
> archiver\gzip
> archiver\bz2
> 
> I'm not understanding your ideas here. Are you not using Mateusz's
> packages from "1.1/repos"? He already has these packaged.

The installer uses packages from Mateusz’s repo. At present, I intend 
the installer to keep the same packages in the same places as his
all_cd.iso. However, the FreeDOS 1.2 release won’t contain all
of the packages that he provides. This would provide compatibility
between the two sources for packages. Mateusz’s disc image is 
currently about 500mb. I think the Official FreeDOS release should
be under 100mb.

> 
> Of course, tar and gzip must be ancient 16-bit versions, if you want
> to be ultra compatible. bzip2 never had 16-bit builds, AFAIK. Anyways,
> p7zip already supports all of those archive/compresion formats, and he
> has a package for that as well.
> 
> devel\bwbasic
> devel\bcc
> 
> These aren't extremely useful (plus fairly buggy) to most people.

Someone requested basic and c, I will remove them.

> 
>> Also, Option 1 in the FDCONFIG.SYS file that FDI creates has issues
>> with VirtualBOX. Someone who is more up to date on the memory
>> managers should do an install and take a look at the config files. Then,
>> let me know what needs changed. Otherwise, It won’t get fixed.
> 
> You mean JEMMEX? Just don't make it default at all, make "XMS only"
> (HIMEMX) the default.
> 
>>A couple other minor things.
>> 
>> I have tested the USB stick image as a hard drive and it works fine. However,
>> I have no way at present to boot from a DOS formatted USB stick. So, I have
>> not uploaded the USB version.
> 
> PLoP Boot Manager (via floppy [or other methods]) lets me boot a USB
> on my "old" P4. You could try that:
> 
> https://www.plop.at/en/bootmanagers.html 
> <https://www.plop.at/en/bootmanagers.html>

I’m traveling again and won’t be home for a week or so. Currently, I only
have my Mac and It won’t boot a drive partition for Dos. VMware fusion and
Virtual Box won’t simulate boot from USB. When I get home, if I have the time,
I will test it on the a couple machines.

> 
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI

[Jerome E. Shidel Jr.]

I did a little tweaking and stuff to FDI. So, I just released latest image. 

Mostly, this was adding the ability to remove the install media before 
doing the reboot. Also, if FDINST is installed, an appropriate config file for 
it
is also now included. (Same as the OS install: Binaries only or with Sources)

http://up.lod.bz/FDI/latest 

Remember FDI is done. So, think of it like a good Pie. Once it is cooked, 
don’t leave it in the oven to long or it well be over done. ;-)

Oh, still would like the NL, ES, EO and FR translations for the reboot message.
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FPC 3.0.0

[Jerome E. Shidel Jr.]

> On Jan 14, 2016, at 11:54 AM, Jerome E. Shidel Jr. <jer...@shidel.net> wrote:
> 
> Well, I was messing around a little with the new FreePascal Compiler for DOS.
> 
> Basically, what ships requires DOS LFN support. Many units, libraries and 
> executables
> are longer than the 8.3 standard file names. 
> 
> It would be a lot of tedious work to migrate it to completely support 8.3 
> names. 
> 
> I don’t know if the effort is worth it or not. I know I don’t have the time 
> to do it.
> 
> So basically, unless someone else ports it’s file names that leaves three 
> options.
> 
> 1) stick with the current version.
> 2) leave it alone and require DOSLFN.
> 3) Strip it way way way down.
> 
> I will let some else decide how they would like to handle this. :-)

(Although, I may look into porting it.)

> 
> Jerome
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FPC 3.0.0

[Jerome E. Shidel Jr.]

Well, I was messing around a little with the new FreePascal Compiler for DOS.

Basically, what ships requires DOS LFN support. Many units, libraries and 
executables
are longer than the 8.3 standard file names. 

It would be a lot of tedious work to migrate it to completely support 8.3 
names. 

I don’t know if the effort is worth it or not. I know I don’t have the time to 
do it.

So basically, unless someone else ports it’s file names that leaves three 
options.

1) stick with the current version.
2) leave it alone and require DOSLFN.
3) Strip it way way way down.

I will let some else decide how they would like to handle this. :-)

Jerome
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI Translations

[Jerome E. Shidel Jr.]

Hello again,

I just made some changes to V8Power Tools so the user can remove the install 
media before FDI does a system reboot.

So, I would like to get the following translated into all the appropriate 
languages. (ES, EO, FR, NL & DE)
Once again, rewording is fine.

Remove the installation media and press a key to restart the system or press 
CTRL+C to exit.

Thanks in advance,

Jerome
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Silly me

[Jerome E. Shidel Jr.]

Hello again all you FDEV’s,

I was feeling a little bored, so by adding 6 lines to FDI, I enabled “install 
from directory” support. Kinda, sorta.

Basically, you do an xcopy /e a:\*.* . into a subdirectory for both the FDI 
boot image and Mateusz’s ALL_CD.iso.

And it works… Mostly, that is.

Well, it works all the way up to  the system transfer. Since, you can’t 
transfer the system files from and to C: it
catches the error and drops out. (I could work around the problem, but I don’t 
really see the point)

So, It could not be used to download everything to a directory on C: and run 
the install. But, I guess it could 
be useful to install from a flash drive or some other disk. 

http://up.lod.bz/FDI/latest

How are the BASE & ALL package lists and package updates going?

I would like to change the FreeDOS 1.2-pre9 label to FreeDOS 1.2-alpha. (Hint, 
Hint.)
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

[Jerome E. Shidel Jr.]

> On Jan 4, 2016, at 4:09 PM, Antony Gordon <cuzint...@gmail.com> wrote:
> 
> Hi,
> 
> I’m using NASM. It seems to work well with all the other labels. 
> 
> In my digging, I have found that default may be a keyword. I’ll try that too 
> just to be sure.

I think you are correct that it is a keyword. (I’ve never used it)

So, just do a search, replace and pray with something like defopt

But labels really do need that : 

Nash always complains that “a label alone on a line without a colon may be in 
error”

It is really useful when you type something like “jump OverInfiniteLoop"

:-)

> 
> -T
>> On Jan 4, 2016, at 4:07 PM, Jerome E. Shidel Jr. <jer...@shidel.net> wrote:
>> 
>> 
>>> On Jan 4, 2016, at 10:54 AM, Antony Gordon <cuzint...@gmail.com> wrote:
>>> 
>>> Hi,
>>> 
>>> I’m attempting to recompile FDISK and apparently you need to assemble 
>>> bootnorm.asm and booteasy.asm and I’m getting this error when assembling 
>>> booteasy.asm
>>> 
>>> booteasy.asm:260: error: invalid parameter to [default] directive
>>> This is line 260 below.
>>> 
>>> default db  '?',' '+80h
>>> 
>>> Any thoughts?
>> 
>> Yep. What assembler are you using?
>> 
>> default looks like it should be a label.
>> 
>> in nasm you would require a colon to inform the compiler it is label. like 
>> this
>> 
>> default: db …….
>> 
>>> 
>>> -T
>>> --
>>> ___
>>> Freedos-devel mailing list
>>> Freedos-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>> 
>> 
>> --
>> ___
>> Freedos-devel mailing list
>> Freedos-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 beta

[Jerome E. Shidel Jr.]

The new FreeDOS batch file based installer (FDI) has been done for a while now 
and
I have used it to install FreeDOS multiple times. Since, it just uses Mateusz’s 
repo disc
image for packages and is not FreeDOS 1.1, I consider it a FreeDOS 1.2 
preview/alpha
version.

It would be nice to have a FreeDOS 1.2 Beta Release sometime soon. Then a RC and
Final version sometime thereafter.

So, to the best of my knowledge this is what needs to be completed. 
(Not by me!)

1) Universally compatible simple fdconfig.sys an autoexec.bat file that is 
installed by FDI.

The present one that is created is has limited compatibility. For 
example, boot option 1
is not compatible with VirtualBox. Someone needs to take a look at them 
and provide the
needed changes. One additional consideration is regarding language and 
codepage 
support. FDI can automatically include custom settings for these when 
creating a new 
autoexec.bat based on the user’s selected language. If these settings 
are to be included, 
they need to be provided and placed in a custom SETLANG.BAT file for 
the specific 
language. FDI will embed them into the new autoexec file during the 
installation. 

2) List of packages for BASE and ALL. 

I have tried to make BASE as close to the what was in FreeDOS 1.1.
I have no clue what to put into ALL for 1.2.

3) Assist Mateusz in bringing all of his packages up to there latest versions.

4) Assemble a Boot CD that contains the installer and the FreeDOS packages.


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] A little message

[Jerome E. Shidel Jr.]

> On Dec 31, 2015, at 6:13 PM, JAYDEN CHARBONNEAU  
> wrote:
> 
> See you guys next year! (Hah...hah..hah?)
> 
So your the one hacking into my webcam. :-)

Happy New Year to Everyone. (5.37 hours to go here)

> On Dec 31, 2015 10:29 AM, "Mercury Thirteen"  > wrote:
> Then a happy New Year to all those of us who are still stuck in last
> year! :P :)
> 
> On 12/31/2015 9:39 AM, Mateusz Viste wrote:
> > I fear you are slightly too late - there are many places in the world
> > where it's 2016 already - Most of Australia, some parts of Russia, New
> > Zealand, and a few more. :)
> >
> > Mateusz
> >
> >
> >
> > On 31/12/2015 15:09, JAYDEN CHARBONNEAU wrote:
> >> Yes,tonight is New Years Eve!Stay up late!Party!Watch the balldrop!I you
> >> all have a wonderful (and crazy) evening!
> >>
> >> -Jayden
> >>
> >> *Crazy meaning have a fun party
> >>
> >> On Thu, Dec 31, 2015 at 2:52 AM, Maarten Vermeulen  >> 
> >> >> wrote:
> >>
> >>  And a happy new year! :)
> >>
> >>
> >>  
> >> 
> >>  Van: JAYDEN CHARBONNEAU  >> >
> >>  Verzonden: ‎26-‎12-‎2015 16:07
> >>
> >>  Aan: Technical discussion and questions for FreeDOS developers.
> >>   >> >
> >>  Onderwerp: Re: [Freedos-devel] A little message
> >>
> >>  I recently got my band director to let us play Sleigh Ride.The
> >>  trumpets enjoyed making the horse noises.
> >>  On Dec 26, 2015 3:19 AM, "Maarten Vermeulen"  >> 
> >>  >> wrote:
> >>   >
> >>   > For those who like it, a Dutch christmas song.
> >>   > 'midden in de winternacht' it's name. This is one of the first
> >>  christmas songs you learn in dutch, because this one is always used
> >>  on school.
> >>   >
> >>   > So here is it, 'midden in de winternacht'.
> >>   >
> >>   > https://m.youtube.com/watch?v=lOyEmKJozc0 
> >> 
> >>   >
> >>   > Of course you are allowed to use google translate :)
> >>   > 
> >>   > Van: Rugxulo
> >>   > Verzonden: ‎26-‎12-‎2015 06:09
> >>   > Aan: Technical discussion and questions for FreeDOS developers.
> >>   > Onderwerp: Re: [Freedos-devel] A little message
> >>   >
> >>   > Hi,
> >>   >
> >>   > On Fri, Dec 25, 2015 at 12:37 PM, Maarten Vermeulen
> >>   
> >> >> wrote:
> >>   > >
> >>   > > Yes thanks! Everyone have a merry christmas!
> >>   > > Good luck with your familly! :P
> >>   >
> >>   > What, no Dutch translation?  :-O
> >>   >
> >>   > "Gelukkig Kerstfeest!" (according to https://translate.google.com 
> >> )
> >>   >
> >>   > (And the German ...)
> >>   >
> >>   > "Fröhliche Weihnachten" (also according to Google)
> >>   >
> >>   > (Kaj la esperantan tradukon ...)
> >>   >
> >>   > "Feliĉan Kristnaskon!"
> >>   >
> >>   >
> >
> > --
> > ___
> > Freedos-devel mailing list
> > Freedos-devel@lists.sourceforge.net 
> > 
> > https://lists.sourceforge.net/lists/listinfo/freedos-devel 
> > 
> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net 
> 
> https://lists.sourceforge.net/lists/listinfo/freedos-devel 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel

--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI updated.

[Jerome E. Shidel Jr.]

Thanks to Maarten, I found out that there was a compatibility issue in 
VirtualBox 
with the 186+ High Precision Interrupt Timer used by the V8Power Tool vdelay 
utility.

The delay is used to prevent messages from flicker on/off the screen and having 
a user go “what did that say?” 

Basically, using the timer would just cause the Installer to freeze.

Anyhow, the compatibility issue in vdelay has been resolved.

So even no no changes were made to FDI, there is a new FDI Preview 9 release 
to resolve the VirtualBox compatibility issue available at 
http://up.lod.bz/FDI/latest



--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI Preview 9

[Jerome E. Shidel Jr.]

FreeDOS Installer Preview 9, now ready.

http://up.lod.bz/FDI/latest

I updated the language translations, Thanks again.

Increased performance and reduced code for the Language Options Screen. By,
spending some time working on the install media build utility mkFDI. This 
reduced
the need for multiple calls to vecho for displaying each language on the screen.
That was getting a little slow to cycle through them. 

A little bit of other language handling and fine tuning. 

A couple other things to reduce some env usage and complexity without 
sacrificing 
any flexibility.
--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI Language Translations

[Jerome E. Shidel Jr.]

> On Dec 23, 2015, at 7:58 AM, Mateusz Viste <mate...@viste.fr> wrote:
> 
> On 23/12/2015 13:38, Jerome E. Shidel Jr. wrote:
>>> Japanese - Nobody.
>>> Russian - Nobody.
>>> Chinese - Nobody.
>> 
>> I thought there was a standard and completely acceptable practice
>> for representing these languages using the standard Western DOS
>> Latin based font that was put into place at the dawn of the PC age.
> 
> I don't know about asian languages, but for russian it would be a heresy 
> to do so. Yes, there exists an informal "latin" equivalent way to write 
> russian, but it was never intended to be used by Russian users, it's 
> rather for western people to be able to vocalize (*very* approximately) 
> russian words and phrases.

You are probably correct with regards to Russian translation.

As for the Asian languages, I don’t know either. I thought that the latin
based representation of their written languages came about do due
the two main issues. The limited character set capabilities of the Operating
Systems and writing directions of the written languages. So, more or less,
I came down to: Ok, you want to use computers too. Make your language 
work with the hardware. 

Assuming, that my poor knowledge of computer history is even remotely
accurate, I don’t know if is still acceptable to represent the Asian languages
using the DOS Latin font. Or, if it is considered offensive to translate their
languages that way in modern times.

> 
> As for actual russian users, there is CP866, and that's what shall be 
> used for DOS text interfaces.

So, Russian is probably out. Assuming that it is possible to do some code
page swapping on a running system, I don’t think Jim would want the additional
complexity added to FDI. 

Using the font tools I built for PGME and it’s Font Designer., it wouldn’t be 
very difficult to change the current DOS font. The tools already exist. This 
also assumes that the language could be represented accurately in a 8x?? 
size font and someone would create the font and translations. But again, I 
don’t think Jim would want the extra complexity.

> 
> Mateusz
> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI Language Translations

[Jerome E. Shidel Jr.]

Just a minor note to those working on FDI Translations.

I just updated the LangTest.bat utility for testing translation 
resource files. I had forgot to include a couple message and
I also made a couple minor improvements.

So, if you are using that utility, you should retrieve the 
latest sources from http://github.com/shidel/FDI  

Other that adding Rugxulo’s Esperanto translation to the 
language selection screen in FDI, no significant changes 
were made to the installer.--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI Language Translations

[Jerome E. Shidel Jr.]

Hello Christian,

Looks really good.

You did miss something though.

“What FreeDOS packages do you want to install?” in the FDINS.DEF file.

PACS?=What /f %1 %2 /f %3 packages do you want to install?

Thanks again
Jerome.


> On Dec 23, 2015, at 5:35 PM, Christian Imhorst <christian.imho...@gmail.com> 
> wrote:
> 
> Hi Jerome,
> 
> the German translation is done. You can find the files at 
> https://github.com/christianimhorst/FDI
> 
> Hope I could help.
> 
> Best regards,
> Christian
> 
> 
> 
> Am Wed, 23 Dec 2015 07:38:47 -0500
> schrieb "Jerome E. Shidel Jr." <jer...@shidel.net>:
> 
>> 
>>> On Dec 21, 2015, at 9:06 AM, Jerome E. Shidel Jr.
>>> <jer...@shidel.net> wrote:
>>> 
>>> At present, based on a user Facebook poll. This is the state of 
>>> current Language Translations for FDI. I don’t know if all of these
>>> are possible using the Standard DOS Latin Codepage. 
>>> 
>>> I don’t know if it is would be possible to have FDI keep changing
>>> the Codepage and Character set. But, I don’t think Jim would want
>>> the added complexity. So, I will not be adding it even if it is
>>> possible.
>>> 
>>> English - Me, Done.
>>> Spanish - Me and Google, Done.
>>> French - Paul Dufresne, Mostly Done.
>> 
>> Done. (I had google help me finish the strings that I forgot to
>> include).
>> 
>>> Dutch - Marteen, Unknown/Pending.
>> 
>> Dutch - Maarten Vermeulen, Pending (Sorry for misspelling your name).
>> 
>> Esperanto - Rugxulo, Done. 
>> 
>>> German - Nobody.
>> 
>> I really think it needs German. Need a Volunteer still. :-)
>> 
>>> Japanese - Nobody.
>>> Russian - Nobody.
>>> Chinese - Nobody.
>> 
>> I thought there was a standard and completely acceptable practice 
>> for representing these languages using the standard Western DOS
>> Latin based font that was put into place at the dawn of the PC age.
>> 
>> Basically stuff like this: (per Google Translate: "Welcome to
>> FreeDOS”)
>> 
>> Japanese - FreeDOS no e yōkoso.
>> Russian -  Dobro pozhalovat' na FreeDOS.
>> Chinese - Huānyíng FreeDOS de.
>> 
>>> Welsh - Nobody.
>>> Patagonian - Nobody.
>> 
>> Patagonian - No Such Language. Patagonia speaks Spanish and Welsh.
>> 
>>> Basque - Nobody.
>>> Navajo - Nobody.
>>> Sanskrit - Nobody.
>>> Swahili - Nobody.
>>> 
>>> Any volunteers?
>> 
>> 
>> --
>> ___
>> Freedos-devel mailing list
>> Freedos-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI updated

[Jerome E. Shidel Jr.]

Just released new FDI boot image.

http://up.lod.bz/FDI/latest 

Reduced some complexity and slight performance improvement.
(add option to V8Power Tools vprogres program to calculate percentage internally
the latest version is included in the FDI image and is also available at
http://up.lod.bz/V8Power/Latest  )

Reduced required free environment space a little. FreeCOM was having an
issue providing enough free env space when installer was launched manually.

Added Dutch and German translations to there mostly completed current state. 
(Dutch not yet added to Language Prompting Screen)

Made new autoexec creation a little more dynamic to support automatic insertion
of language codepage settings and inclusion of language specific welcome 
messages.

FDI, now sets Installation target drive to root directory before exit. 
Preventing need
to do CD \ when exiting installer after installation and examining target drive.

Maybe tomorrow:

Probably, I will update the mkFDI.bat utility (The thing that builds the boot 
image
from scratch) to include the different language welcome messages at startup.

Maybe, add automatic codepage switching if appropriate %LANG%\SETLANG.BAT file
is available for the Language.

Add Dutch to Language Selection screen.

Push new FDI boot image to server.

Enjoy Christmas Eve dinner at my relatives.

Get a good night sleep waiting for Santa Claus. 
Hope he brings me that Ferrari or even a Tesla. I’m not picky.

:-)

--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI Language Translations

[Jerome E. Shidel Jr.]

> On Dec 21, 2015, at 9:06 AM, Jerome E. Shidel Jr. <jer...@shidel.net> wrote:
> 
> At present, based on a user Facebook poll. This is the state of 
> current Language Translations for FDI. I don’t know if all of these
> are possible using the Standard DOS Latin Codepage. 
> 
> I don’t know if it is would be possible to have FDI keep changing the 
> Codepage and Character set. But, I don’t think Jim would want the 
> added complexity. So, I will not be adding it even if it is possible.
> 
> English - Me, Done.
> Spanish - Me and Google, Done.
> French - Paul Dufresne, Mostly Done.

Done. (I had google help me finish the strings that I forgot to include).

> Dutch - Marteen, Unknown/Pending.

Dutch - Maarten Vermeulen, Pending (Sorry for misspelling your name).

Esperanto - Rugxulo, Done. 

> German - Nobody.

I really think it needs German. Need a Volunteer still. :-)

> Japanese - Nobody.
> Russian - Nobody.
> Chinese - Nobody.

I thought there was a standard and completely acceptable practice 
for representing these languages using the standard Western DOS
Latin based font that was put into place at the dawn of the PC age.

Basically stuff like this: (per Google Translate: "Welcome to FreeDOS”)

Japanese - FreeDOS no e yōkoso.
Russian -  Dobro pozhalovat' na FreeDOS.
Chinese - Huānyíng FreeDOS de.

> Welsh - Nobody.
> Patagonian - Nobody.

Patagonian - No Such Language. Patagonia speaks Spanish and Welsh.

> Basque - Nobody.
> Navajo - Nobody.
> Sanskrit - Nobody.
> Swahili - Nobody.
> 
> Any volunteers?


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDos languages

[Jerome E. Shidel Jr.]

> On Dec 22, 2015, at 10:01 PM, Jose Antonio Senna 
>  wrote:
> 
> How did "patagonian" appear in the list of 
> requested FreeDos languages ?
> AFAIK
> 1) There is no patagonian language.
> 2) PT stands for "portuguese" in the ISO
>  page codes.
> Regards
> JAS

Someone entered it in the Facebook language poll for the new installer.

Doing a little quick looking online, it does not show up in the 

https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes

list of codes. Looking a little further, it appears their are
two languages used in Patagonia, Spanish and Welsh.


> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] fdisk translation

[Jerome E. Shidel Jr.]

> On Dec 22, 2015, at 11:51 AM, Paul Dufresne  wrote:
> 
> When testing the installer, it was not feeling right to go from the
> french installer to the english fdisk... how could fdisk be
> translated?

Just a note, when FDI launches, if the LANG variable is set it uses that
setting. If it is not (you booted from the FDI install media), it will attempt 
to
auto-detect the proper language and set the LANG variable. If neither was
possible, it prompt the user and then sets the LANG variable.

It also uses this setting for the new AUTOEXEC.BAT config file. (assuming 
the user is in either BASIC mode or elects to install new config files).

> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.2 ALL packages

[Jerome E. Shidel Jr.]

> On Dec 20, 2015, at 5:45 PM, Antony Gordon <cuzint...@gmail.com> wrote:
> 
> Hi,
> 
> An assembler and a Pascal compiler. Missing BASIC and C/C++.
> 
> 

I don’t use Basic or C(s). :-)

> That would make the programming languages complete. You should probably 
> mention sources for all packages in the "everything" install.
> 
There are 4 types of package install that FDI performs.

Basic.
Basic w/Sources.

All.
All w/Sources.

All does not mean everything plus sources. Since most users won’t care about 
having the sources, they are not automatically
installed unless the user wants them.
> Base should just reference that the sources are on the install media. IIRC, 
> most Linux distributions don't specifically install the source code unless 
> requested by the end user.
> 
> -T
> 
> 
> On Sun, Dec 20, 2015, 4:55 PM Jerome E. Shidel Jr. <jer...@shidel.net> wrote:
> This is the list of the ALL package list for the FDI installer.
> 
> Please let me know if I should anything else or remove something.
> 
> Also, V8Power Tools is also installed when ALL is selected.
> 
> This list includes all packages in the BASE. I just did not include them here 
> to
> shorten the list.
> 
> ; The remaining packages are only installed when ALL is chosen.
> net\mtcp
> util\4dos
> util\doslfn
> util\fdnpkg
> util\memtest
> util\bootfix
> util\shsufdrv
> util\cwsdpmi
> archiver\zip
> archiver\unzip
> 
> ; Some packages I would like to see in ALL.
> util\grep
> archiver\tar
> archiver\gzip
> archiver\bz2
> devel\nasm
> devel\fpc
> net\wget
> net\rsync
> 
> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.2 ALL packages

[Jerome E. Shidel Jr.]

> On Dec 21, 2015, at 12:52 AM, Mateusz Viste  wrote:
> 
> On 21/12/2015 00:02, Rugxulo wrote:
>>> util\fdnpkg
>> 
>> Presumably latest here? (0.99.4 "<8 hours ago", according to SF.net page)
> 
> Good catch! I did release (silently) FDNPKG to v0.99.4 yesterday. Since 
> it contains nothing big from the user's point of view, I didn't feel 
> that it justify announcing it anywhere. But yes, here it is :)

Yeah, I saw you pushed it out about 2 hours before I did another Preview 
release of FDI. So, I pulled it down. Made sure it was working. Then
used it on the Preview Release. :-)

> 
>>> devel\fpc
>> 
>> 3.0.0 was released recently, but there is no "package" for it yet.
> 
> Same goes for DJGPP. And FreeBASIC. And surely many more packages. This 
> is one of the issues that I pointed to in my latest "call for 
> volunteers" on the user list. But since call remained completely 
> unanswered, I assume nobody cares. So why bother?

I hear you there. I get almost no feedback on what packages need to be
in BASE. Or even, what would like to be seen in ALL. Very disappointing.

I hope that most of them are at least the latest “Stable” release.

> 
> Mateusz
> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS 1.2 ALL packages

[Jerome E. Shidel Jr.]

> On Dec 20, 2015, at 6:02 PM, Rugxulo <rugx...@gmail.com> wrote:
> 
> Hi,
> 
> On Sun, Dec 20, 2015 at 3:55 PM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> wrote:
>> 
>> This is the list of the ALL package list for the FDI installer.
>> 
>> Please let me know if I should anything else or remove something.
>> 
>> Also, V8Power Tools is also installed when ALL is selected.
>> 
>> This list includes all packages in the BASE. I just did not include them 
>> here to
>> shorten the list.
>> 
>> ; The remaining packages are only installed when ALL is chosen.
>> net\mtcp
> 
>> util\4dos
> 
> (I know some people can't live without this. I just hate the idea that
> it somehow taints the whole bunch due to ambiguous license.)
> 
>> util\doslfn
> 
> Which version? 0.41c?

The packages and versions assume just using the ones available on
 Mateusz’s FreeDOS Package Repository. 
(repeat for all version questions).

The new batch file based FreeDOS Installer (FDI) is finished. It is only waiting
on the package lists to be completed. Once that is done, the install media 
can be assembled and it can go into beta testing. While it is waiting on those
lists, I will be adding submitted language translations for the installer.

> 
>> util\fdnpkg
> 
> Presumably latest here? (0.99.4 "<8 hours ago", according to SF.net page)
> 
>> util\memtest
> 
> Uh, you mean Eric's old patched version? Version??
> 
>> util\bootfix
>> util\shsufdrv
> 
> BTW, the licensing is slightly ambiguous here (IMO), but Jason Hood
> told me that it's "zlib".
> 
>> util\cwsdpmi
> 
> Please make sure r7 only (although including both r5 2008 and r7
> wouldn't be the worst idea, but I seriously don't know of any obvious
> reason to do that).
> 
>> archiver\zip
> 
> 2.32? (I still don't know why we never "officially" had 3.00, not that
> it majorly matters.)
> 
>> archiver\unzip
> 
> 6.00?
> 
>> ; Some packages I would like to see in ALL.
>> util\grep
> 
> Xgrep? (No LFNs, no *nix globbing, but it's very small!)
> 
> http://freedos.sourceforge.net/software/?prog=xgrep
> 
>> archiver\tar
> 
> Which? ("UTIL" does include an ancient 16-bit one.)
> 
> http://freedos.sourceforge.net/software/?prog=tar
> 
>> archiver\gzip
> 
> Which? (I'm assuming only the old 16-bit one and not the 386+ DJGPP build.)
> 
> http://freedos.sourceforge.net/software/?prog=gzip
> 
>> archiver\bz2
> 
> (386+ DJGPP only)
> 
> http://freedos.sourceforge.net/software/?prog=bzip2
> 
>> devel\nasm
> 
> Which? Latest is 2.11.08.
> 
> http://freedos.sourceforge.net/software/?prog=nasm
> http://www.nasm.us/
> 
>> devel\fpc
> 
> 3.0.0 was released recently, but there is no "package" for it yet. It
> would be quite large (which is annoying), but perhaps LZMA (which
> Mateusz dislikes) would mitigate that.
> 
>> net\wget
> 
> Michael Kostylev made a (slightly) newer version semi-recently, but I
> have no idea if he included all patches or not (as things like that
> are a pain to rebuild). So I'm not honestly sure if 1.11 is that much
> worse than 1.12 (and certainly the latter is much larger). (He also
> rebuilt Curl, but I have the same worries. I may just mirror them to
> iBiblio anyways, lacking any direct proof of error.)
> 
> http://www.bttr-software.de/forum/board_entry.php?id=14569
> 
>> net\rsync
> 
> Dunno if that's even available, can't remember, never tried it. EDIT:
> Here's what we seem to have (but it's not officially listed under
> "NET", apparently):
> 
> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/rsync/
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI Language Translations

[Jerome E. Shidel Jr.]

At present, based on a user Facebook poll. This is the state of 
current Language Translations for FDI. I don’t know if all of these
are possible using the Standard DOS Latin Codepage. 

I don’t know if it is would be possible to have FDI keep changing the 
Codepage and Character set. But, I don’t think Jim would want the 
added complexity. So, I will not be adding it even if it is possible.

English - Me, Done.
Spanish - Me and Google, Done.
French - Paul Dufresne, Mostly Done.
Dutch - Marteen, Unknown/Pending.

German - Nobody.
Japanese - Nobody.
Russian - Nobody.
Chinese - Nobody.
Welsh - Nobody.
Patagonian - Nobody.
Basque - Nobody.
Navajo - Nobody.
Sanskrit - Nobody.
Swahili - Nobody.

Any volunteers?


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 BASE packages

[Jerome E. Shidel Jr.]

This is the list of the BASE Packages for the FDI installer.

Please note that I switched out UIDE for UDVD2. UIDE was causing strange
disk errors with FDINST and with FreeCOM.

Remember this is the Minimalist, MS-DOS functionality only BASE for FreeDOS 1.2.

Please let me know if I left anything out or should remove something.

Also, V8Power Tools is not installed when only BASE is selected.

; Package list for BASE only installation.

base\append
base\assign
base\attrib
base\chkdsk
base\choice
base\command
base\comp
base\cpidos
base\ctmouse
base\debug
base\defrag
base\deltree
base\devload
base\diskcomp
base\diskcopy
base\display
base\dosfsck
base\edit
base\edlin
base\exe2bin
base\fc
base\fdapm
base\fdisk
base\find
base\format
base\fdxms
base\fdxms286
base\help
base\jemm
base\himemx
base\kernel
base\keyb
base\keyb_lay
base\label
base\lbacache
base\mem
base\mirror
base\mkeyb
base\mode
base\more
base\move
base\nansi
base\nlsfunc
base\print
base\rdisk
base\recover
base\replace
base\share
base\shsucdx
base\sort
base\swsubst
base\tree
base\undelete
base\unformat
base\xcopy
base\xmgr
util\udvd2


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FreeDOS 1.2 ALL packages

[Jerome E. Shidel Jr.]

This is the list of the ALL package list for the FDI installer.

Please let me know if I should anything else or remove something.

Also, V8Power Tools is also installed when ALL is selected.

This list includes all packages in the BASE. I just did not include them here 
to 
shorten the list.

; The remaining packages are only installed when ALL is chosen.
net\mtcp
util\4dos
util\doslfn
util\fdnpkg
util\memtest
util\bootfix
util\shsufdrv
util\cwsdpmi
archiver\zip
archiver\unzip

; Some packages I would like to see in ALL.
util\grep
archiver\tar
archiver\gzip
archiver\bz2
devel\nasm
devel\fpc
net\wget
net\rsync



--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI Additional Languages

[Jerome E. Shidel Jr.]

> On Dec 18, 2015, at 2:39 PM, Maarten  wrote:
> 
> Just a few things:
>  
> I added this to the author section:
>  
>  
> ***
> FreeDOS 1.2 Installer (language) Translation.
> Provided by: Maarten Vermeulen
> Contact Email: netraa...@gmail.com
> Created/Modified: created at 18 dec 2015 (19:40 UTC +1.00) Finished at -
> Released Under GPL v2.0 License.
> ***
>  
> ; LANG_AUTHOR is unused at present, but you should set it to your name.
> LANG_AUTHOR=Maarten Vermeulen
> LANG_NAME=Dutch
>  
> Is that acceptable?

I have no problem with that and neither will v8power tools or the installer. :-)

>  
> I have now this on the format section:
>  
> NOFORMAT=/s-  "Schijf " /f %1 %2 /f %3 " lijkt niet geformatteerd te zijn."
> FORMAT?="Weet u zeker dat u de schijf wilt formatteren?"
> FORMAT_YES="  Ja - Verwijder en formatteer schijf %1."
> FORMATADV_QUICK="  Ja - verwijder en formatteer snel schijf %1."
> FORMATADV_SLOW="  Ja - Verwijder en formatteer schijf %1" " volledig."
>  
> In the sentence of FORMATADV_SLOW I added something behind it, in dutch this 
> is the only solution for these sort of senteces. But as I did it, is this 
> allowed?

That is fine and it will work fine. The order of text and parameters is 
not important and will be parsed correctly.

Only a minor displayed output issue. You would have 2 spaces between %1 and 
volledig. 

You have three options:
1) Make it all inside the same quote.
2) Remove the leading space before volledig.
3) stick a /s- in there, causing no spaces between strings.

here is an example of that kind of stuff using vecho:

vecho Hellotheremy/s- friend how “are you” /s+ today? “I   SAID   
FINE” !

would output:

Hello there myfriendhoware you today? I   SAID   FINE !

Hope that makes sense.

One more note, to use quotes like the ‘ character you must quote it.

Examples:

vecho ‘Say “Hello” Bob’
Say “Hello” Bob

vecho “Bob’s House”
Bob’s House.

The first quote sets the terminating quote.

>  
> Also what is meant with this, I don’t really get where you reffering to….
>  
> “Do not span lines in option choices. A new line will become an additional
> choice and will throw off the return value for the following selections(…)”

Basically, lets say you have two choices. 

Format and erase drive. Totally nuking my hard drive.
Quit to Dos.

If for some reason, the text exceeds one line and is spanned across multiple 
lines
the it will become it’s own choice. So, if the choice are is two narrow or you 
insert
a line break switch (/p) in a choice string, it will cause a new and choice to 
be created.

So, if the above options output like this:

Format and erase drive. Totally nuking
my hard drive.
Quit to DOS.

You now have 3 choices (one per line) and quit to dos is no longer result 2.

Anyhow, for now, you really don’t need to worry about it. Once, I have the time 
to
finish the LangTest.bat utility. I will go through and adjust the frame sizes 
to accommodate
text width and other such things.


>  
> Thanks,
> Maarten
>  
> 
> Van: Maarten
> Verzonden: vrijdag 18 december 2015 19:25
> Aan: Eric Auer
> Onderwerp: RE: [Freedos-devel] FDI Additional Languages
>  
> I am going to work at the Dutch language. but now I have questions! :)
>  
> 1.   Do i need to translate everything (except the real code)?
> 2.   Where do I put the finished files?
> 3.   And I fill in my name email etc. ?
>  
> Maarten
>  
> 
> Van: Eric Auer
> Verzonden: vrijdag 18 december 2015 17:36
> Aan: freedos-devel@lists.sourceforge.net
> Onderwerp: Re: [Freedos-devel] FDI Additional Languages
>  
>  
> Hi Paul,
>  
> > mmm is code page (437 is default, 850 is updated form, 1252 for Windows)
>  
> In general, you can assume that 437 is what comes with your BIOS
> and graphics card BIOS while 850 is popular in DOS. Codepages of
> Windows are not popular in DOS :-) Maybe Mateusz or Aitor can say
> what the most popular codepages are: A default install comes with
> EGA.CPX and EGAn.CPX where n = 2 ... 10 and CPX = compressed CPI.
>  
> Each CPX can contain several fonts. For example EGA.CPX would be
> 58880 bytes instead of 6322 bytes without (UPX) compression ;-)
>  
> See also:
> http://help.fdos.org/en/hhstndrd/base/display.htm
> http://help.fdos.org/en/hhstndrd/base/mode.htm
>  
> After some searching, I found this page:
> http://help.fdos.org/en/hhstndrd/base/cpidos.htm
>  
> It gives a list of codepages in each font file, which summarizes as:
>  
> (there are several variants of several codepages, e.g. with / without
> Euro currency sign, or different regional variants of codepages...)
>  
> EGA: 437 US, 850/858 Latin-1 852 Eastern 853 Southern 857 Turkish
> EGA2: 859 French/Estonian 775 Baltic 1116-1119 Latvian/Lithuanian
> EGA3: 771/772 Lithuanian/Russian 855/872 Cyrillic 866/808 

Re: [Freedos-devel] FDI Additional Languages

[Jerome E. Shidel Jr.]

> On Dec 18, 2015, at 2:39 PM, Maarten  wrote:
> 
> Just a few things:

Also, thanks for working on a Dutch translation.

>  

Just some FYI,

Also, you can delete any of the comment text of you want. Add lines, etc.

The text resource file has a very strict look-up policy and everything that 
does not
match the Key it is looking for at that moment is ignored. Just don’t change 
anything before the = symbol.

These would all be different ID keys:

McDonalds=Not Burger King.
MCDONALDS=Not Taco Bell.
mcdonalds=Not Hardees.

And these ID keys would never be found: (because they contain spaces)

Mc Donalds=Not Subway.
McDonalds =Not Wendys.
McDonalds=Not White Castle.

Spaces are fine after the equal symbol, like:

McDonads=  Not KFC.

(I’m about to eat dinner, So, food was on my mind. :-) 

And any character other than Space and Equals can be used in a Key like:

**MCDONALDS**=Burgers
MC=Fries
#MC_DONALDS:9.4?=Apple Pie

Actually, the look-up process even supports DOS and Unix line endings.
It could even work with a binary blob or executable.  (provided the text was 
wrapped in a CR)

Technically, The value of a key is treated like an addition to the command-line 
parameters. So,
any switch or option that is supported by the related V8Power Tool can be used. 
At present, 
vecho, vframe and vask support the resource lookup. Most of the resource data 
for text in FDI is
used by vecho. 

These switches for vecho may also be of use when translating to Dutch.

/P  Perform a CRLF now.
/S +Insert a space character between parameters. (DEFAULT)
/S -Do not add space character between multiple parameters.
/C code Write an ASCII character code. (like /c32, or /c0x20)
/R timesRepeat the next write times number of times. (1-65535) 
(Like /r5/c32 to do 5 spaces)


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI Additional Languages

[Jerome E. Shidel Jr.]

It has been several days. Are there no volunteers to do Language translations?

If not, it will only support English and “Broken” Spanish.

https://github.com/shidel/FDI/tree/master/LANGUAGE/TEMPLATE

> On Dec 13, 2015, at 5:07 PM, Jerome E. Shidel Jr. <jer...@shidel.net> wrote:
> 
> Just an additional note on the languages.
> 
> I ran a poll on Facebook. And the requests were in order:
> 
> English (EN) +6
> Spanish (ES) +5
> German (DE) +4
> Japanese +3
> Russian +3
> Chinese (ZH_TW) +3
> Patagonian (PT) +1
> Klingon
> Swahili 
> 
> Also, my “Broken” Spanish translation should really be redone by 
> someone who speaks more than my very poor Spanish. All, I did
> was run text through google translate and try to fix it up a little. 
> Sometimes, I’d read what it gave me and would think “I know that 
> can’t be correct.”
> 
> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI

[Jerome E. Shidel Jr.]

Hello Jim,

Mostly, I don’t think it is too complex.

It really only has one mode of operation. Fresh install.

However, it will make a backup and preserve package data when a user 
happens to be upgrading.

If no language setting was found, the first screen prompts for the language.

Next is the Welcome to the Installer screen.

(Clean system, Asks to partition and to format)

(Pre-existing OS askes to make a backup)

Install Base/All w/without sources.

The the install now prompt.

(installs OS)

Asks to reboot or exit.

All of the other prompting and questions are only shown in advanced mode.
They just provide an opportunity for the user to override default actions and
assumptions that the installer 

Is there anything in particular that has you concerned?

Just an FYI, I am really leaning towards not providing detailed package 
selection
in advanced mode. I have though of several ways to implement it. But, 
I don’t really like any of the ones I have come up with that don’t require
a separate utility that does it. I am not going to create a tool just for that.
So, DPS probably won’t be included in the standard installer.

Other than DPS, determining what packages are in BASE and ALL, and adding
languages, the installer is done.


> On Dec 17, 2015, at 11:32 AM, Jim Hall <jh...@freedos.org> wrote:
> 
> I worry that the new FreeDOS installer is becoming too complex, trying to do 
> all things for every use case and every user. 
> 
> 
> On Sat, Dec 12, 2015 at 11:49 AM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> wrote:
> Tying to decide what to do about a specific upgrade situation regarding 
> package files.
> 
> At present:
> 
> DOSDIR is backed up.
> 
>  All packages that are going to be installed are removed before 
> installation.
> 
> Package data files are backed up.
> 
> The the DOSDIR is purged.
> 
> Package data files are restored.
> 
> New packages are installed.
> 
> Issue:
> 
> Packages that have files in the DOSDIR, will lose those files.
> 
> Solution 1: (Present behavior)
> 
> Let the user worry about it, and let them do a remove/install of 
> those packages later.
> 
> Solution 2:
> 
> Also, uninstall any packages that have any files that reside in the 
> DOSDIR.
> 
> Solution 3:
> 
> Restore the missing files from the backup.
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI Additional Languages

[Jerome E. Shidel Jr.]

I have no problem including any submitted language translation for FDI.
By it’s inclusion, it would be supported by FDI either through auto-detection or
setting the LANG environment variable.

I just make no promises that it will be on the Select Language screen.

> On Dec 17, 2015, at 10:48 AM, Maarten Vermeulen  wrote:
> 
> Well, google translte is not needed, I am dutch.
> So I would like to do that, but if dutch isn't used it doesn't make any sense 
> to translate it.
> 
> Maarten


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI

[Jerome E. Shidel Jr.]

> On Dec 17, 2015, at 12:38 PM, JAYDEN CHARBONNEAU <jcharbonnea...@cpsge.org> 
> wrote:
> 
> Perhaps implementing some of the code from the older installer (FD1.1)?That 
> allowed you to select your packages on install.We could take some of the code 
> from that and use it for our modern ADVANCED mode.

Detailed package selection would not be difficult to create from scratch. I 
just don’t know if I want to spend any time on a separate 
utility that 99.9% of the people who install FreeDOS would never use or see. On 
top of that, I know from what Jim has said, he
has no desire for that feature.

> 
> On Thu, Dec 17, 2015 at 12:21 PM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> wrote:
> Hello Jim,
> 
> Mostly, I don’t think it is too complex.
> 
> It really only has one mode of operation. Fresh install.
> 
> However, it will make a backup and preserve package data when a user
> happens to be upgrading.
> 
> If no language setting was found, the first screen prompts for the language.
> 
> Next is the Welcome to the Installer screen.
> 
> (Clean system, Asks to partition and to format)
> 
> (Pre-existing OS askes to make a backup)
> 
> Install Base/All w/without sources.
> 
> The the install now prompt.
> 
> (installs OS)
> 
> Asks to reboot or exit.
> 
> All of the other prompting and questions are only shown in advanced mode.
> They just provide an opportunity for the user to override default actions and
> assumptions that the installer
> 
> Is there anything in particular that has you concerned?
> 
> Just an FYI, I am really leaning towards not providing detailed package 
> selection
> in advanced mode. I have though of several ways to implement it. But,
> I don’t really like any of the ones I have come up with that don’t require
> a separate utility that does it. I am not going to create a tool just for 
> that.
> So, DPS probably won’t be included in the standard installer.
> 
> Other than DPS, determining what packages are in BASE and ALL, and adding
> languages, the installer is done.
> 
> 
> > On Dec 17, 2015, at 11:32 AM, Jim Hall <jh...@freedos.org> wrote:
> >
> > I worry that the new FreeDOS installer is becoming too complex, trying to 
> > do all things for every use case and every user.
> >
> >
> > On Sat, Dec 12, 2015 at 11:49 AM, Jerome E. Shidel Jr. <jer...@shidel.net> 
> > wrote:
> > Tying to decide what to do about a specific upgrade situation regarding 
> > package files.
> >
> > At present:
> >
> > DOSDIR is backed up.
> >
> >  All packages that are going to be installed are removed before 
> > installation.
> >
> > Package data files are backed up.
> >
> > The the DOSDIR is purged.
> >
> > Package data files are restored.
> >
> > New packages are installed.
> >
> > Issue:
> >
> > Packages that have files in the DOSDIR, will lose those files.
> >
> > Solution 1: (Present behavior)
> >
> > Let the user worry about it, and let them do a remove/install of 
> > those packages later.
> >
> > Solution 2:
> >
> > Also, uninstall any packages that have any files that reside in the 
> > DOSDIR.
> >
> > Solution 3:
> >
> > Restore the missing files from the backup.
> > --
> > ___
> > Freedos-devel mailing list
> > Freedos-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI Additional Languages

[Jerome E. Shidel Jr.]

> On Dec 17, 2015, at 3:26 PM, Maarten Vermeulen <netraa...@gmail.com> wrote:
> 
> I am going to translate the 3 files as well, if I get back a mail from Jim...
> Is there a dead line? When should it be finsihed?
> It is 80% sure that i help the other 20% (the mail) is not sure.

No “deadline.” I’m just don’t have any patience. :-) 

The installer is done. Except, maybe Detailed Package Selection. But, I’m 
really starting
to think that won’t be included in the installer. It might make better sense 
for a visual
front end to a package manager be installed when the “All Packages” option is 
selected.
That way, it would keep some complexity out of the installer and the user could 
easily
add and remove packages at will at any time.

We still need to decide exactly what packages are in the BASE and ALL sets.
I made my best guess at what goes into BASE, but that may need tweaked.
As for ALL, I have no idea what Jim wants in the ALL packages. 
Things like FPC, NASM, games or other utilities?

Once that is settled upon, we can do a package snapshot and it can go to Beta 
Testing.

(I’ve been running the FreeDOS 1.2-pre system for a while)

Since, the language stuff is not part of the functionality of the Installer it 
can be added 
at anytime up to actual release. So, there is no hurry. But, sooner is usually 
better. :-)

> 
> I hope I can help!
> 
> Maarten
> Van: Paul Dufresne
> Verzonden: ‎17-‎12-‎2015 19:23
> Aan: Technical discussion and questions for FreeDOS developers.
> Onderwerp: Re: [Freedos-devel] FDI Additional Languages
> 
> Yeah, I am thinking about translating the 3 files to french... just
> have a little problem making it a priority.
> Guess you should not postpone release if you don't get results soon enough.
> 
> 2015-12-17 12:27 GMT-05:00 Jerome E. Shidel Jr. <jer...@shidel.net>:
> > I have no problem including any submitted language translation for FDI.
> > By it’s inclusion, it would be supported by FDI either through 
> > auto-detection or
> > setting the LANG environment variable.
> >
> > I just make no promises that it will be on the Select Language screen.
> >
> >> On Dec 17, 2015, at 10:48 AM, Maarten Vermeulen <netraa...@gmail.com> 
> >> wrote:
> >>
> >> Well, google translte is not needed, I am dutch.
> >> So I would like to do that, but if dutch isn't used it doesn't make any 
> >> sense to translate it.
> >>
> >> Maarten
> >
> >
> > --
> > ___
> > Freedos-devel mailing list
> > Freedos-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDINST

[Jerome E. Shidel Jr.]

Mateusz a reminder, 

You need to update your online repo and all_cd.iso to contain the fixed version 
of FDINST.

:-)
--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI

[Jerome E. Shidel Jr.]

> On Dec 13, 2015, at 12:45 PM, Tom Ehlert  wrote:
> 
> 
>> Tying to decide what to do about a specific upgrade situation regarding 
>> package files.
> 
>> At present:
> 
>>DOSDIR is backed up.
> 
>> All packages that are going to be installed are removed before 
>> installation.
> 
>>Package data files are backed up.
> 
>>The the DOSDIR is purged.
> 
> seriously?

Yes. Purging the DOSDIR is performed in basic mode to provide a “Clean" OS 
directory.
This is what my interpretation of what Jim said he wants the installer to do. 

Step 1 is backup DOSDIR. So, anything that was in there is backed up before it 
is
purged.

Advanced mode, lets the user decide if the installer is to nuke the old DOSDIR.

> 
> destroying programs that were created by more conventional means
> without this (stupid) package manager?
> 
> deleting config files?

Absolutely. And it enjoys doing it. In basic mode it makes many, many, many 
assumptions
and performs multiple automatic adjustments. In advanced mode, nearly all 
decisions 
are left up to the user.

> 
> Tom
> 



--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDI Additional Languages

[Jerome E. Shidel Jr.]

Just an additional note on the languages.

I ran a poll on Facebook. And the requests were in order:

English (EN) +6
Spanish (ES) +5
German (DE) +4
Japanese +3
Russian +3
Chinese (ZH_TW) +3
Patagonian (PT) +1
Klingon
Swahili 

Also, my “Broken” Spanish translation should really be redone by 
someone who speaks more than my very poor Spanish. All, I did
was run text through google translate and try to fix it up a little. 
Sometimes, I’d read what it gave me and would think “I know that 
can’t be correct.”



--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI Additional Languages

[Jerome E. Shidel Jr.]

Well, except for adding package selection in FDI, all user facing text 
is ready for translation into any additional languages that the installer
should support. 

All translation text for FDI is contained in 3 text files per language and 
will be located under the installers directory in a subdirectory named
by language ID. 

For example, on the install boot media:

English:
A:\FDSETUP\SETUP\EN\FDSETUP.DEF
A:\FDSETUP\SETUP\EN\FDASK.DEF
A:\FDSETUP\SETUP\EN\FDINS.DEF

Spanish:
A:\FDSETUP\SETUP\ES\FDSETUP.DEF
A:\FDSETUP\SETUP\ES\FDASK.DEF
A:\FDSETUP\SETUP\ES\FDINS.DEF

So, if you wish to create custom language translations for FDI, this
is what you need:

Download the language template files from github at:
https://github.com/shidel/FDI/tree/master/LANGUAGE/TEMPLATE

These lines are included in the boot image and also are installed on 
the new system config files and translated by them. They also need 
more language translations.

( 

Notes on below:
/s- means no spaces between text strings. (/s+ is default)
/f? is foreground color change. (can use number instead of name)
/a? sets text attribute, foreground and background to value.
/b? set background (not used below)
/p is perform a carriage return linefeed now. (not used below)

There is no limit on the length of a translation string. However, it 
will stop translating when it reaches 255 characters and ignore 
the rest of the string. This limit includes all switches and variables
that are expanded into the string. But, does not include options that
were set prior to the activation of the string. (i.e., the command line)

DONE %1 is FDCONFIG.SYS, %2 is AUTOEXEC.BAT
“Done processing startup files C:\FDCONFIG.SYS and C:\AUTOEXEC.BAT”

HELP %1 is the command HELP
"Type HELP to get support on commands and navigation.”

WELCOME %1 is FreeDOS, %2 is Version, “%3" is URL. 
(%3 must be quoted contains / char)
“Welcome to the FreeDOS 1.2 operating system (http://www.freedos.org)”
)

English (EN)
DONE.EN=Done processing startup files /fCyan %1 /a7 and /fCyan %2 /a7
HELP.EN=Type /fWhite %1 /fGray to get support on commands and navigation.
WELCOME.EN=Welcome to the /fGreen %1 /fCyan %2 /fGray operating system ( /s- 
/fYellow “%3" /fGray )

Spanish (ES)
DONE.ES=Inicio transformación efectuada archivos /fCyan %1 /a7 y /fCyan %2 /a7
HELP.ES=Escriba /fWhite %1 /fGray para conseguir el apoyo de los comandos y de 
navegación.
WELCOME.ES=Bienvenido al sistema operativo /fGreen %1 /fCyan %2 /fGray ( /s- 
/fYellow "%3" /fGray )

For best results, you probably should adjust some of the dialog 
boxes sizes and such things inside the translation files. To test the 
translation files.

Download the prototype FDI boot image at:
http://up.lod.bz/FDI/latest

Download Mateusz’s all_cd.iso at:
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/

Place the translations in the appropriate subdirectory on the floppy image.

Create a new virtual machine that has a CD, Floppy drive and uninitialized 
hard drive for DOS.

Boot the floppy image.

Exit the installer.

Set the LANG variable to your language. 

Make sure the CD is mounted.

Run setup. (or setup adv)

Also, you can use CTRL+C when FDI is waiting for user input to switch in/out of 
Advanced 
mode or to exit the installer.

Send me your translations.





--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI

[Jerome E. Shidel Jr.]

Tying to decide what to do about a specific upgrade situation regarding package 
files.

At present:

DOSDIR is backed up.

 All packages that are going to be installed are removed before 
installation.

Package data files are backed up.

The the DOSDIR is purged.

Package data files are restored.

New packages are installed.

Issue:

Packages that have files in the DOSDIR, will lose those files.

Solution 1: (Present behavior)

Let the user worry about it, and let them do a remove/install of those 
packages later.

Solution 2:

Also, uninstall any packages that have any files that reside in the 
DOSDIR.

Solution 3:

Restore the missing files from the backup.
--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] FDI Advanced Mode

[Jerome E. Shidel Jr.]

Added Installation Target Drive and Directory changing in FDI advanced mode.

Now, I just need to find the time to write vchkbox to allow package selection 
in advanced mode. Maybe.
--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDINST

[Jerome E. Shidel Jr.]

> On Dec 10, 2015, at 1:51 AM, Mateusz Viste <mate...@viste.fr> wrote:
> 
> Okay, I fixed your floppy, by adding the missing stuff, changing a few 
> config.sys lines etc, and the final result is that it works. which 
> is sad, because yet again, I am unable to reproduce the problems you 
> report, and I'd really like to.

I don’t know why the A:\FDOS shows no files on your vm.  They are there. I even 
redownloaded the version I posted to double check. 

> 
> Here is "my" version of your floppy pkg tester:
> gopher://gopher.viste.fr/1/temp/
> 
> I tested it on Oracle VirtualBox 5.0.10, and all 262 packages pass fine 
> ("IRIR OK"). I was using the all_cd.iso from last saturday, and an empty 
> virtual disk of 4 GB with a single partition formatted FAT32.
> 
> So either there is something very wrong with the VMWare thing you are 
> using, OR by manipulating your floppy I fixed something in it... Would 
> you mind testing "my" version, so we are clear on that? I probably did 
> some things differently than you: no LFN, no cache, added FILES=40, used 
> UDVD2 instead of UIDE, and a few other details.

I ran your modified driver and config version. All tested good.
So, either the remaining issues are not in FDINST or only occur in combination
with one of the drivers you swapped out. 

Basically, the config it was using was pulled straight out of FreeDOS 1.1 and 
heavily stripped down.

The DOSDIR and TEMP dir are changed dynamically by the PKGTEST.BAT and 
don’t need set at boot time.

I might do some further testing to see where the conflict arrises. But, I don’t
really have the time for that lately. Besides, everything is testing GOOD now
with FDINST.

> 
> BTW, there was a "._PKGTEST.img" file in your zip archive. I completely 
> ignored it, because I didn't know what to do with it - I guess it's 
> useless, and you only included it to show off having a mac, right? ;-)

It just sneaked in there. :)

> 
> cheers,
> Mateusz
> 

BTW, did you enjoy the V8Power Tools Demonstrantion?

> 
> 
> On 09/12/2015 23:17, Jerome E. Shidel Jr. wrote:
>> 
>>> On Dec 7, 2015, at 12:47 AM, Mateusz Viste <mate...@viste.fr> wrote:
>>> 
>>> Could you confirm please that these tests were performed using the
>>> latest version of both the all_cd.iso and fdinst?
>> 
>> Still having issues with the latest versions.
>> -3, -9 a couple invalid opcode errors and such.
>> 
>> About 12 packages, 317 errors.
>> 
>>> 
>>> The 'out of memory' error you report on fbc.zip makes me think you used
>>> an old all_cd.iso file. This was an error I spotted, too, and it was due
>>> to the fact that the sole file list requires more memory than what
>>> FDINST is able to allocate. The "good" iso is dated "2015-Dec-05
>>> 06:33:10" on ibiblio - I repackaged fbc by zipping all sources all together.
>>> 
>>> I am running a very similar test than you, that is: install the entire
>>> content of all_cd, look for errors, remove all packages, look for
>>> errors, install all packages again, look for errors. I don't run into
>>> any troubles any more, though. The difference is that I run my test
>>> suite under DOSemu, while you run it under VirtualBox. Dunno if
>>> virtualbox is stable enough for that... (on my PC, vbox is quite
>>> unstable when running FreeDOS - for example trying to execute djgpp
>>> immediately kills the VM).
>>> 
>>> Mateusz
>>> 
>> 
>> I created a standalone tester.
>> 
>> Download compressed image from http://up.lod.bz/PKGTEST/latest
>> 
>> Setup a virtual machine machine with a DOS CD-ROM and formatted Drive C:
>> 
>> Mount the ALL_CD.ISO and boot the Floppy image the test will autorun.
>> 
>> Since the tester sets up it’s own DOS target directory and stuff, It would 
>> probably
>> be ok to just boot the image using an existing DOS vm. But, I recommend a
>> fresh vm just in case something runs amuck.
>> 
>> Notes:
>>  I = fdinst install
>>  R = fdinst remove
>>  P = Manually purge of DOSDIR
>> 
>> Stuff in red is bad.
>> 
>>> 
>>> 
>>> 
>>> On 06/12/2015 23:02, Jerome E. Shidel Jr. wrote:
>>>> 
>>>>> On Dec 5, 2015, at 6:36 AM, Mateusz Viste <mate...@viste.fr> wrote:
>>>>> 
>>>>> On 04/12/2015 18:58, Mateusz Viste wrote:
>>>>>> I am in the process of fixing all the ibiblio packages that contain LFN.
>>>>> 
>>>>> Done. I spent the day on repackaging t

Re: [Freedos-devel] FDINST

[Jerome E. Shidel Jr.]

> On Dec 10, 2015, at 6:38 AM, Mateusz Viste <mate...@viste.fr> wrote:
> 
> On 10/12/2015 10:46, Jerome E. Shidel Jr. wrote:
>> I don’t know why the A:\FDOS shows no files on your vm.  They are there. I 
>> even
>> redownloaded the version I posted to double check.
> 
> I re-downloaded your zip again, and yes, the files are in FDOS now. No 
> idea what kind of magic happened - I might have corrupted the image 
> somehow when I downloaded it the first time. But with the "correct" 
> image the CDROM is not detected (no D: drive). Well, not important any 
> more, since the problem appears to be caused not by FDINST, but rather 
> the floppy environment.

Well, I messed around a little bit with the config. 
It appears, all "current issues” are caused by the UIDE.SYS driver.
If UDVD2.SYS is used, the problems go away. 

So, my best guess is that there is a bug in that driver, resulting in
CD-ROM read errors. It might be worth while to verify that CD read
errors are handled by the unzip code. But, I think the issue is strictly in
the driver. After all, virtual CD drives don’t have read errors.

So, it looks like you have squashed all the FDINST bugs. :-)

> 
>> I ran your modified driver and config version. All tested good.
> 
> Perfect.
> 
>> BTW, did you enjoy the V8Power Tools Demonstrantion?
> 
> Yes, I noticed it, and it looks very cool! The CTRL+C detection is a 
> really nice touch.

:-)

> 
> Mateusz
> 
> 
> 
>>> On 09/12/2015 23:17, Jerome E. Shidel Jr. wrote:
>>>> 
>>>>> On Dec 7, 2015, at 12:47 AM, Mateusz Viste <mate...@viste.fr> wrote:
>>>>> 
>>>>> Could you confirm please that these tests were performed using the
>>>>> latest version of both the all_cd.iso and fdinst?
>>>> 
>>>> Still having issues with the latest versions.
>>>> -3, -9 a couple invalid opcode errors and such.
>>>> 
>>>> About 12 packages, 317 errors.
>>>> 
>>>>> 
>>>>> The 'out of memory' error you report on fbc.zip makes me think you used
>>>>> an old all_cd.iso file. This was an error I spotted, too, and it was due
>>>>> to the fact that the sole file list requires more memory than what
>>>>> FDINST is able to allocate. The "good" iso is dated "2015-Dec-05
>>>>> 06:33:10" on ibiblio - I repackaged fbc by zipping all sources all 
>>>>> together.
>>>>> 
>>>>> I am running a very similar test than you, that is: install the entire
>>>>> content of all_cd, look for errors, remove all packages, look for
>>>>> errors, install all packages again, look for errors. I don't run into
>>>>> any troubles any more, though. The difference is that I run my test
>>>>> suite under DOSemu, while you run it under VirtualBox. Dunno if
>>>>> virtualbox is stable enough for that... (on my PC, vbox is quite
>>>>> unstable when running FreeDOS - for example trying to execute djgpp
>>>>> immediately kills the VM).
>>>>> 
>>>>> Mateusz
>>>>> 
>>>> 
>>>> I created a standalone tester.
>>>> 
>>>> Download compressed image from http://up.lod.bz/PKGTEST/latest
>>>> 
>>>> Setup a virtual machine machine with a DOS CD-ROM and formatted Drive C:
>>>> 
>>>> Mount the ALL_CD.ISO and boot the Floppy image the test will autorun.
>>>> 
>>>> Since the tester sets up it’s own DOS target directory and stuff, It would 
>>>> probably
>>>> be ok to just boot the image using an existing DOS vm. But, I recommend a
>>>> fresh vm just in case something runs amuck.
>>>> 
>>>> Notes:
>>>>I = fdinst install
>>>>R = fdinst remove
>>>>P = Manually purge of DOSDIR
>>>> 
>>>> Stuff in red is bad.
>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On 06/12/2015 23:02, Jerome E. Shidel Jr. wrote:
>>>>>> 
>>>>>>> On Dec 5, 2015, at 6:36 AM, Mateusz Viste <mate...@viste.fr> wrote:
>>>>>>> 
>>>>>>> On 04/12/2015 18:58, Mateusz Viste wrote:
>>>>>>>> I am in the process of fixing all the ibiblio packages that contain 
>>>>>>>> LFN.
>>>>>>> 
>>>>>>> Done. I spent the day on repackaging the whole base of ibiblio packages
>>>>>&

Re: [Freedos-devel] FDINST

[Jerome E. Shidel Jr.]

> On Dec 7, 2015, at 12:47 AM, Mateusz Viste <mate...@viste.fr> wrote:
> 
> Could you confirm please that these tests were performed using the 
> latest version of both the all_cd.iso and fdinst?

Still having issues with the latest versions.
-3, -9 a couple invalid opcode errors and such.

About 12 packages, 317 errors.

> 
> The 'out of memory' error you report on fbc.zip makes me think you used 
> an old all_cd.iso file. This was an error I spotted, too, and it was due 
> to the fact that the sole file list requires more memory than what 
> FDINST is able to allocate. The "good" iso is dated "2015-Dec-05 
> 06:33:10" on ibiblio - I repackaged fbc by zipping all sources all together.
> 
> I am running a very similar test than you, that is: install the entire 
> content of all_cd, look for errors, remove all packages, look for 
> errors, install all packages again, look for errors. I don't run into 
> any troubles any more, though. The difference is that I run my test 
> suite under DOSemu, while you run it under VirtualBox. Dunno if 
> virtualbox is stable enough for that... (on my PC, vbox is quite 
> unstable when running FreeDOS - for example trying to execute djgpp 
> immediately kills the VM).
> 
> Mateusz
> 

I created a standalone tester. 

Download compressed image from http://up.lod.bz/PKGTEST/latest

Setup a virtual machine machine with a DOS CD-ROM and formatted Drive C:

Mount the ALL_CD.ISO and boot the Floppy image the test will autorun.

Since the tester sets up it’s own DOS target directory and stuff, It would 
probably
be ok to just boot the image using an existing DOS vm. But, I recommend a 
fresh vm just in case something runs amuck.

Notes: 
I = fdinst install
R = fdinst remove
    P = Manually purge of DOSDIR

Stuff in red is bad.

> 
> 
> 
> On 06/12/2015 23:02, Jerome E. Shidel Jr. wrote:
>> 
>>> On Dec 5, 2015, at 6:36 AM, Mateusz Viste <mate...@viste.fr> wrote:
>>> 
>>> On 04/12/2015 18:58, Mateusz Viste wrote:
>>>> I am in the process of fixing all the ibiblio packages that contain LFN.
>>> 
>>> Done. I spent the day on repackaging the whole base of ibiblio packages
>>> so every single one is compliant to the 8+3 scheme.
>>> 
>>> I also rebuilt a new all_cd.iso with all the updated packages. Now, I am
>>> able to install/remove/install all of them without experiencing any error.
>>> 
>>> Latest version of all_cd.iso:
>>> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/
>>> 
>>> Latest FDNPKG/FDINST devel version:
>>> gopher://gopher.viste.fr/1/temp
>>> 
>>> Mateusz
>> 
>> This is a similar pass with the same configuration. Mostly it looks the 
>> same, but
>> a couple packages through different errors. Look at the OW.zip for example.
>> 
>> D:\ARCHIVER\ARJ.ZIP reinstall error.
>> 1 Errors with D:\ARCHIVER\ARJ.ZIP
>> E:\FDSETUP\bin\arjdisp.exe [-9]
>> -
>> 0 Errors with D:\ARCHIVER\BZ2.ZIP
>> -
>> 0 Errors with D:\ARCHIVER\CABEXT.ZIP
>> -
>> 0 Errors with D:\ARCHIVER\LZIP.ZIP
>> -
>> 0 Errors with D:\ARCHIVER\P7ZIP.ZIP
>> -
>> 0 Errors with D:\ARCHIVER\UPX.ZIP
>> -
>> 0 Errors with D:\BASE\COMMAND.ZIP
>> -
>> D:\BASE\CPIDOS.ZIP reinstall error.
>> 2 Errors with D:\BASE\CPIDOS.ZIP
>> E:\FDSETUP\cpi\ega17.cpx [-9]
>> E:\FDSETUP\cpi\ega14.cpx [-9]
>> -
>> D:\BASE\CTMOUSE.ZIP reinstall error.
>> 1 Errors with D:\BASE\CTMOUSE.ZIP
>> E:\FDSETUP\bin\ctmouse\ctm-pl.exe [-9]
>> -
>> 0 Errors with D:\BASE\EDLIN.ZIP
>> -
>> D:\BASE\HELP.ZIP reinstall error.
>>  Errors with D:\BASE\HELP.ZIP
>> E:\FDSETUP\help\en\hhstndrd\hhstndrd.zip [-9]
>> -
>> 0 Errors with D:\DEVEL\BCC.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_BN.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_BS.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_DB.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_FQ.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_FX.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_GC.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_GP.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_MK.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_OB.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_RH.ZIP
>> -
>> 0 Errors with D:\DEVEL\DJGPP_TX.ZIP
>> -
>> 0 Errors with D:\DEVEL\EUPHORIA.ZIP
>> -
>> 0 Errors with D:\DEVEL\FBC.ZIP
>&g

Re: [Freedos-devel] FDINST

[Jerome E. Shidel Jr.]

> On Dec 5, 2015, at 6:36 AM, Mateusz Viste  wrote:
> 
> On 04/12/2015 18:58, Mateusz Viste wrote:
>> I am in the process of fixing all the ibiblio packages that contain LFN.
> 
> Done. I spent the day on repackaging the whole base of ibiblio packages 
> so every single one is compliant to the 8+3 scheme.
> 
> I also rebuilt a new all_cd.iso with all the updated packages. Now, I am 
> able to install/remove/install all of them without experiencing any error.
> 
> Latest version of all_cd.iso:
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/
> 
> Latest FDNPKG/FDINST devel version:
> gopher://gopher.viste.fr/1/temp
> 
> Mateusz
> 

This is the latest results if the tester for the latest version of FDINST.
Please note, this is using the previous version of your ALL_CD.iso image.
Not the latest one. (I only have so much bandwidth to use on my cellphone)

Packages with no errors are not listed. 
Packages listed with "0 errors” are ones that reported an error. Those are 
mostly
the ones that contained non-compliant file names.

Files that show “Reinstall Error” were installed ok, removed ok, failed 
reinstall.
Files that don’t have that label failed on the first attempt and no further 
attempt was made.

(FBC.ZIP, generated an Out of memory error)

These results were with caching. However, I have started it again without 
caching and
so far the results appear to be the same.

--

0 Errors with D:\ARCHIVER\BZ2.ZIP 
-
0 Errors with D:\ARCHIVER\CABEXT.ZIP 
-
0 Errors with D:\ARCHIVER\LZIP.ZIP 
-
0 Errors with D:\ARCHIVER\P7ZIP.ZIP 
-
0 Errors with D:\ARCHIVER\UPX.ZIP 
-
0 Errors with D:\BASE\COMMAND.ZIP 
-
D:\BASE\CPIDOS.ZIP reinstall error. 
2 Errors with D:\BASE\CPIDOS.ZIP 
C:\TESTB\FDSETUP\cpi\ega17.cpx [-9]
C:\TESTB\FDSETUP\cpi\ega14.cpx [-9]
-
D:\BASE\CTMOUSE.ZIP reinstall error. 
1 Errors with D:\BASE\CTMOUSE.ZIP 
C:\TESTB\FDSETUP\bin\ctmouse\ctm-pl.exe [-9]
-
0 Errors with D:\BASE\EDLIN.ZIP 
-
D:\BASE\HELP.ZIP reinstall error. 
1 Errors with D:\BASE\HELP.ZIP 
C:\TESTB\FDSETUP\bin\help.exe [-9]
-
0 Errors with D:\DEVEL\BCC.ZIP 
-
0 Errors with D:\DEVEL\DJGPP.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_BN.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_BS.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_DB.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_FQ.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_FX.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_GC.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_GP.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_MK.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_OB.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_RH.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_TX.ZIP 
-
0 Errors with D:\DEVEL\EUPHORIA.ZIP 
-
0 Errors with D:\DEVEL\FBC.ZIP 
-
0 Errors with D:\DEVEL\FPC.ZIP 
-
0 Errors with D:\DEVEL\JWASM.ZIP 
-
0 Errors with D:\DEVEL\LUA.ZIP 
-
0 Errors with D:\DEVEL\NASM.ZIP 
-
1 Errors with D:\DEVEL\OW.ZIP 
C:\TESTB\FDSETUP\devel\ow\src\memos.c [-3]
-
0 Errors with D:\DEVEL\PERL.ZIP 
-
0 Errors with D:\DEVEL\REGINA.ZIP 
-
0 Errors with D:\DEVEL\UPX.ZIP 
-
2 Errors with D:\EMULATOR\CHIP8.ZIP 
C:\TESTB\FDSETUP\chip8\sgames\sources\uboat.src [-3]
C:\TESTB\FDSETUP\chip8\games\sources\syzygy.src [-3]
-
1 Errors with D:\EMULATOR\GLAUNCH.ZIP 
C:\TESTB\FDSETUP\glaunch\readme.htm [-3]
-
0 Errors with D:\EMULATOR\SIMCOUPE.ZIP 
-
0 Errors with D:\EMULATOR\TEO.ZIP 
-
0 Errors with D:\EMULATOR\VICE.ZIP 
-
0 Errors with D:\EMULATOR\ZSNES.ZIP 
-
0 Errors with D:\GAMES\BOLITARE.ZIP 
-
0 Errors with D:\GAMES\FREEDOOM.ZIP 
-
0 Errors with D:\GAMES\IVAN.ZIP 
-
D:\GAMES\KILOBLAS.ZIP reinstall error. 
1 Errors with D:\GAMES\KILOBLAS.ZIP 
C:\TESTB\FDSETUP\games\kiloblas\shapes.kb2 [-3]
-
0 Errors with D:\GAMES\LIQUIWAR.ZIP 
-
D:\GAMES\MIRMAGIC.ZIP reinstall error. 
4 Errors with D:\GAMES\MIRMAGIC.ZIP 
C:\TESTB\FDSETUP\games\mirmagic\graphics\df.pcx [-9]
C:\TESTB\FDSETUP\games\mirmagic\graphics\toons.pcx [-3]
C:\TESTB\FDSETUP\games\mirmagic\graphics\screen.pcx [-3]
C:\TESTB\FDSETUP\games\mirmagic\sounds\kabumm.wav [-9]
-
D:\GAMES\NETHACK.ZIP reinstall error. 
3 Errors with D:\GAMES\NETHACK.ZIP 
C:\TESTB\FDSETUP\games\nethack\nhdat [-3]
C:\TESTB\FDSETUP\games\nethack\nethacko.tib [-3]
C:\TESTB\FDSETUP\games\nethack\nethack.exe [-3]
-
1 Errors with D:\GAMES\VERTIGO.ZIP 
C:\TESTB\FDSETUP\games\vertigo\sound\talk\lit_righ.wav [-9]
-
1 Errors with D:\GAMES\VITETRIS.ZIP 
C:\TESTB\FDSETUP\games\vitetris\tetris.exe [-3]
-
0 Errors with D:\GAMES\WING.ZIP 
-
D:\GAMES\XARGON.ZIP reinstall error. 
4 Errors with D:\GAMES\XARGON.ZIP 
C:\TESTB\FDSETUP\games\xargon\audio.xr1 [-9]
C:\TESTB\FDSETUP\games\xargon\xrfile02.exe [-9]
C:\TESTB\FDSETUP\games\xargon\audio.xr3 [-9]
C:\TESTB\FDSETUP\games\xargon\audio.xr2 [-9]
-
2 Errors with D:\NET\CRYNWR.ZIP 
C:\TESTB\FDSETUP\drivers\crynwr\ctrondni.com [-9]
C:\TESTB\FDSETUP\doc\crynwr\changes.doc 

Re: [Freedos-devel] FDINST

[Jerome E. Shidel Jr.]

> On Dec 5, 2015, at 6:36 AM, Mateusz Viste  wrote:
> 
> On 04/12/2015 18:58, Mateusz Viste wrote:
>> I am in the process of fixing all the ibiblio packages that contain LFN.
> 
> Done. I spent the day on repackaging the whole base of ibiblio packages 
> so every single one is compliant to the 8+3 scheme.
> 
> I also rebuilt a new all_cd.iso with all the updated packages. Now, I am 
> able to install/remove/install all of them without experiencing any error.
> 
> Latest version of all_cd.iso:
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/
> 
> Latest FDNPKG/FDINST devel version:
> gopher://gopher.viste.fr/1/temp
> 
> Mateusz

This is a similar pass with the same configuration. Mostly it looks the same, 
but
a couple packages through different errors. Look at the OW.zip for example.

D:\ARCHIVER\ARJ.ZIP reinstall error. 
1 Errors with D:\ARCHIVER\ARJ.ZIP 
E:\FDSETUP\bin\arjdisp.exe [-9]
-
0 Errors with D:\ARCHIVER\BZ2.ZIP 
-
0 Errors with D:\ARCHIVER\CABEXT.ZIP 
-
0 Errors with D:\ARCHIVER\LZIP.ZIP 
-
0 Errors with D:\ARCHIVER\P7ZIP.ZIP 
-
0 Errors with D:\ARCHIVER\UPX.ZIP 
-
0 Errors with D:\BASE\COMMAND.ZIP 
-
D:\BASE\CPIDOS.ZIP reinstall error. 
2 Errors with D:\BASE\CPIDOS.ZIP 
E:\FDSETUP\cpi\ega17.cpx [-9]
E:\FDSETUP\cpi\ega14.cpx [-9]
-
D:\BASE\CTMOUSE.ZIP reinstall error. 
1 Errors with D:\BASE\CTMOUSE.ZIP 
E:\FDSETUP\bin\ctmouse\ctm-pl.exe [-9]
-
0 Errors with D:\BASE\EDLIN.ZIP 
-
D:\BASE\HELP.ZIP reinstall error. 
 Errors with D:\BASE\HELP.ZIP 
E:\FDSETUP\help\en\hhstndrd\hhstndrd.zip [-9]
-
0 Errors with D:\DEVEL\BCC.ZIP 
-
0 Errors with D:\DEVEL\DJGPP.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_BN.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_BS.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_DB.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_FQ.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_FX.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_GC.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_GP.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_MK.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_OB.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_RH.ZIP 
-
0 Errors with D:\DEVEL\DJGPP_TX.ZIP 
-
0 Errors with D:\DEVEL\EUPHORIA.ZIP 
-
0 Errors with D:\DEVEL\FBC.ZIP 
-
0 Errors with D:\DEVEL\FPC.ZIP 
-
0 Errors with D:\DEVEL\JWASM.ZIP 
-
0 Errors with D:\DEVEL\LUA.ZIP 
-
0 Errors with D:\DEVEL\NASM.ZIP 
-
23 Errors with D:\DEVEL\OW.ZIP 
E:\FDSETUP\devel\ow\src\memos.c [-3]
E:\FDSETUP\devel\ow\samples\win\alarm\alarm.c [-1]
E:\FDSETUP\devel\ow\samples\win\alarm\alarm.h [-1]
E:\FDSETUP\devel\ow\samples\win\alarm\win32\alarm.tgt [-2]
E:\FDSETUP\devel\ow\samples\win\alarm\win32\alarm.wpj [-2]
E:\FDSETUP\devel\ow\samples\win\alarm\win32\makefile [-2]
E:\FDSETUP\devel\ow\samples\win\generic\win16\generic.tgt [-2]
E:\FDSETUP\devel\ow\samples\win\generic\win16\generic.wpj [-2]
E:\FDSETUP\devel\ow\samples\win\generic\win16\makefile [-2]
E:\FDSETUP\devel\ow\samples\win\generic\generic.c [-2]
E:\FDSETUP\devel\ow\samples\win\generic\generic.h [-2]
E:\FDSETUP\devel\ow\samples\win\generic\generic.ico [-2]
E:\FDSETUP\devel\ow\samples\win\generic\generic.mif [-2]
E:\FDSETUP\devel\ow\samples\win\generic\manifest.xml [-2]
E:\FDSETUP\devel\ow\samples\win\generic\win386\generic.tgt [-2]
E:\FDSETUP\devel\ow\samples\win\generic\win386\generic.wpj [-2]
E:\FDSETUP\devel\ow\samples\win\generic\win386\makefile [-2]
E:\FDSETUP\devel\ow\samples\win\generic\generic.rc [-2]
E:\FDSETUP\devel\ow\samples\win\generic\win32\generic.tgt [-2]
E:\FDSETUP\devel\ow\samples\win\generic\win32\generic.wpj [-2]
E:\FDSETUP\devel\ow\samples\win\generic\win32\makefile [-2]
E:\FDSETUP\devel\ow\samples\win\helpex\mouse.bmp [-2]
-
0 Errors with D:\DEVEL\PERL.ZIP 
-
0 Errors with D:\DEVEL\REGINA.ZIP 
-
0 Errors with D:\DEVEL\UPX.ZIP 
-
2 Errors with D:\EMULATOR\CHIP8.ZIP 
E:\FDSETUP\chip8\sgames\sources\uboat.src [-3]
E:\FDSETUP\chip8\games\sources\syzygy.src [-3]
-
1 Errors with D:\EMULATOR\GLAUNCH.ZIP 
E:\FDSETUP\glaunch\readme.htm [-3]
-
0 Errors with D:\EMULATOR\SIMCOUPE.ZIP 
-
0 Errors with D:\EMULATOR\TEO.ZIP 
-
0 Errors with D:\EMULATOR\VICE.ZIP 
-
0 Errors with D:\EMULATOR\ZSNES.ZIP 
-
0 Errors with D:\GAMES\BOLITARE.ZIP 
-
D:\GAMES\FMINES.ZIP reinstall error. 
9 Errors with D:\GAMES\FMINES.ZIP 
E:\FDSETUP\games\fmines\animals\mine204.dat [-3]
E:\FDSETUP\games\fmines\animals\mine305.dat [-3]
E:\FDSETUP\games\fmines\animals\mine303.dat [-3]
E:\FDSETUP\games\fmines\animals\mine304.dat [-3]
E:\FDSETUP\games\fmines\animals\mine102.dat [-9]
E:\FDSETUP\games\fmines\animals\mine301.dat [-9]
E:\FDSETUP\games\fmines\animals\mine302.dat [-3]
E:\FDSETUP\games\fmines\insects\image.dat [-3]
E:\FDSETUP\games\fmines\insects\mine201.dat [-9]
-
0 Errors with D:\GAMES\FREEDOOM.ZIP 
-
0 Errors with D:\GAMES\IVAN.ZIP 
-
D:\GAMES\KRAPTOR.ZIP reinstall error. 
1 Errors with D:\GAMES\KRAPTOR.ZIP 
E:\FDSETUP\games\kraptor\level3.dat [-9]
-
0 Errors 

Re: [Freedos-devel] FDINST

[Jerome E. Shidel Jr.]

> On Dec 2, 2015, at 3:28 AM, Mateusz Viste  wrote:
> 
> I uploaded a new devel version right now:
> 
> gopher://gopher.viste.fr/1/temp
> 
> Joe Forster kindly hinted off-list that open watcom comes with a 
> 'doslfnX.lib' library that can be used to transparently enable LFN 
> support within the compiled application. Since the required effort is 
> more than reasonable, I linked FDINST to it, so hopefully (?) FDINST 
> should now support LFN files, and therefore it might solve all the -2 
> errors that were popping up when trying to unpack LFN files from packages.
> 
> Mateusz

I will run the complete test on it later today and let you know the results.

But, so far, a quick test is looking good. A couple of packages that caused 
system lockup or crash during the install, remove and reinstall process, 
no longer freeze up the system.  :-) :-) :-)

Some, are still throwing errors in a extremely stripped down configuration.
However, that configuration does not have any LFN support. So, it may
just be [-2] errors.

Later, I will check the log and also run it under DOSLFN. I will let you know
 the results.

> 
> 
> 
> On 01/12/2015 19:04, Mateusz Viste wrote:
>> Hi,
>> 
>> Here is a new devel version of the FDNPKG package (including FDINST, as
>> usual). The big change is that I use zlib now, instead of tinfl.
>> 
>> gopher://gopher.viste.fr/1/temp
>> 
>> My limited tests show that it doesn't fail any more on neither the
>> 'lzma' nor 'help' packages, which the previous deflate library was
>> failing on when compiled to a 16bit target.
>> 
>> This should solve all the -15 and -9 errors you had (these errors being
>> "DEFLATE failure" and "CRC mismatch", respectively).
>> 
>> The -2 errors you reported will NOT be solved ("cannot create file"),
>> since these are related to LFN handling, and as far as I know, Open
>> Watcom doesn't support LFN natively (and I don't plan to write my own
>> INT-based LFN client implementation, nor using a specialized library for
>> that). Ideally, a FreeDOS package shouldn't contain LFN files, but
>> unfortunately some software uses non-8+3 filenames in their sources...
>> No idea how this could be solved 'cleanly' at the package level.
>> 
>> I do not know whether this devel version will solve troubles related to
>> freezing and/or inability to reinstall packages. It might solve them, if
>> TINFL was trashing memory for whatever reason. But it also might be some
>> FDNPKG bug just as well, or not related to FDNPKG/TINFL at all. I will
>> have to do more tests, so far I wasn't able to reproduce the behavior
>> you described.
>> 
>> Mateusz
>> 
> 
> 
> --
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 


--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] vask

[Jerome E. Shidel Jr.]

Well, just completed vask for V8Power Tools.

http://up.lod.bz/V8Power/latest

Single line text input utility.

Features:

Preset edit text.
Time-out support. (/d)
Control-C (on/off) (/c)
Left/Right edit text panning.
Global/Local input (V8 Framing Stuff)
Width overriding. (5 - Screen Columns, very small max can reduce width 
to < 5) (/w)
Max character count limiting. (1-127, adjust width if max < width) (/m)

Esc to reset to preset.
Left, Right, Home and End keys.
PgUp, PgDn, Up and Down keys. (Special Movement).

Basic usage example w/timeout : 

@echo off
vecho /n /fYellow “Your Name? “
vask /c /d10 /fWhite /bBlue Jerome Shidel | set /p NAME=
if errorlevel 200 goto CTRLC
if errorlevel 1 goto TIMEOUT
vecho /a0x07 /p Hello there /s- ‘ “‘ /fWhite “%NAME%” /fGray ‘.”'
goto DONE
:CTRLC
:TIMEOUT
vecho /a7 /p Default user name %NAME% selected.
:DONE
set NAME=



--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911=/4140
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] V8Power Tools - vecho

[Jerome E. Shidel Jr.]

Added some stuff to vecho to increase usage compatibility with echo command. 

Mostly, that is the /s+ and /s- switch. It used to only do /s-. Now, it 
defaults to /s+ for
added compatibility.

example:

vecho /bGray /fBlack Hello /fRed there /fGreen my /fBlue friend /fBlack .

Previously: Hellotheremyfriend.
Now: Hello there my friend .

The /s- and /s+ will switch into and out of the previous way of handling 
multiple parameters.

So, What is wanted would be this command.

vecho /bGray /fBlack Hello /fRed there /fGreen my /fBlue friend /s- /fBlack .

Previously: Hello there my friend.

Multiple spaces between strings (like unix and linux) are ignored unless quoted.

example: vecho Hellothere, Bob.
produces: Hello there, Bob.

example: vecho /s- Hellothere, Bob.
produces: Hellothere,Bob.

example: vecho "Hellothere,” “Bob."
produces: Hello there, Bob.

example: vecho /s- "Hellothere,” “Bob."
produces: Hello there,Bob.

There really is a whole lot of stuff packed into vecho’s 2.5kb executable.

[none]  Preforms a Carriage Return and Line Feed to the display.
textWrites text to the display.
/A nSet text attribute to n.
/B colorSet the background text attribute to color (or a value).
/F colorSet the forground text attribute to color (or a value).
/N  Do not write a CRLF when done.
/P  Perform a CRLF now.
/S +Insert a space character between parameters. (default)
/S -Do not add space character between multiple parameters.
/C code Write an ASCII character code.
/R timesRepeat the next write a number of times. (1-65535)
/I  Write text that may waiting from the STDIN device.
/G  Write text globally and ignore all framing.
/L  Write text locally with regards to framing. (DEFAULT)
/X code Erase rest of line using ascii code, but don't move the cursor.
/E  Same as using "/X 0x20” or “/X32".
/T file ID  Look up ID in file and process it like command line options.
Any additional options that follow this switch are used to
populate %1-%9 variables in the text string.


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDINST

[Jerome E. Shidel Jr.]

Eric, 

Also, I should say that someone who is more up to date on all of the drivers 
and all of their different configuration options should 
design the config for the FDI boot disk and the configuration that will be 
installed by FDI.

I do not have the time to devote to doing that task. If no one else provides 
them, I will just use what gets installed by FreeDOS 1.1 and
a stripped down version for the FDI boot image.

:-)
--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDINST

[Jerome E. Shidel Jr.]

> On Nov 28, 2015, at 7:48 AM, Tom Ehlert  wrote:
> 
> 
>>Virtual machine with 64MB ram. 
>>Boots FreeDOS 1.2-pre, (Using latest packages from your repo)
>>Sets up a clean 32mb ram drive and some floppy caching.
>>Configures FDNPKG.CFG to install to the ramdrive. (Sources excluded)
> 
>>Installs, removes and installs each package on the  ALL_CD.iso.  If 
>> it fails any part of
>>the IRI process fails or it detects unreported issues, it purges the 
>> DOSDIR on the
>>ram drive and retries up to 2 more times.
> 
> I just happen to notice 'ramdrive' and 'some floppy caching'.
> 
> together with a 32 bit FDINST these might (or might not) make
> problems. I'd check this first and install to a real drive, without
> floppy caching
> 
> Tom

FDINST is 16-bit, FDNPKG is 32-bit.

I had the same though about caching, memory managers etc.

So, even with the following configuration and installing to a physical (inside 
a vm) drive
it has the same or similar issues.

Also, please note if all goes well, the tester installs, removes then 
reinstalls the packages.
If the tester catches an error, it completely purges the target tree and 
retries the install,
remove and install process. Repeating it up to 3 times. 

FDINST occasionally throws more or fewer errors on subsequent install attempts 
or on
occasion, further installs of the same package, result in a system freeze. 

FDCONFIG.SYS:

SET DOSDIR=C:\FDOS
COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS
LASTDRIVE=Z
BUFFERS=20
FILES=40
DOS=HIGH
DOS=UMB
DOSDATA=UMB
DEVICE=C:\FDOS\BIN\HIMEMX.EXE
SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT

AUTOEXEC.BAT
@ECHO OFF
SET LANG=EN
SET PATH=%dosdir%\BIN
SET PATH=%path%;C:\TOOLS
SET TEMP=%dosdir%\TEMP
SET TMP=%TEMP%
SHSUCDX /QQ /D3
DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5
SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D /D:?FDCD0002,D 
/D:?FDCD0003,D
SHSUCDX /D
SET AUTOFILE=%0
SET CFGFILE=C:\FDCONFIG.SYS

Excerpt from "mkfdi.bat testb” log: (note doing it manually by hand generates 
similar results)
2 Errors with D:\ARCHIVER\BZ2.ZIP 
C:\TESTB\FDSETUP\doc\bz2\readme.xml.stuff [-2]
C:\TESTB\FDSETUP\doc\bz2\readme.compilation.problems [-2]
-
2 Errors with D:\ARCHIVER\BZ2.ZIP 
C:\TESTB\FDSETUP\doc\bz2\readme.xml.stuff [-2]
C:\TESTB\FDSETUP\doc\bz2\readme.compilation.problems [-2]
-
2 Errors with D:\ARCHIVER\BZ2.ZIP 
C:\TESTB\FDSETUP\doc\bz2\readme.xml.stuff [-2]
C:\TESTB\FDSETUP\doc\bz2\readme.compilation.problems [-2]
-
2 Errors with D:\ARCHIVER\LZIP.ZIP 
C:\TESTB\FDSETUP\bin\lziprecover.exe [-15]
C:\TESTB\FDSETUP\bin\lzip.exe [-15]
-
2 Errors with D:\ARCHIVER\LZIP.ZIP 
C:\TESTB\FDSETUP\bin\lziprecover.exe [-15]
C:\TESTB\FDSETUP\bin\lzip.exe [-15]
-
2 Errors with D:\ARCHIVER\LZIP.ZIP 
C:\TESTB\FDSETUP\bin\lziprecover.exe [-15]
C:\TESTB\FDSETUP\bin\lzip.exe [-15]
-
1 Errors with D:\ARCHIVER\LZMA.ZIP 
C:\TESTB\FDSETUP\bin\lzma.exe [-15]
-
1 Errors with D:\ARCHIVER\LZMA.ZIP 
C:\TESTB\FDSETUP\bin\lzma.exe [-15]
-
1 Errors with D:\ARCHIVER\LZMA.ZIP 
C:\TESTB\FDSETUP\bin\lzma.exe [-15]
-
3 Errors with D:\ARCHIVER\P7ZIP.ZIP 
C:\TESTB\FDSETUP\bin\p7zip.exe [-15]
C:\TESTB\FDSETUP\bin\p7zipr.exe [-15]
C:\TESTB\FDSETUP\bin\7zcon.sfx [-15]
-
3 Errors with D:\ARCHIVER\P7ZIP.ZIP 
C:\TESTB\FDSETUP\bin\p7zip.exe [-15]
C:\TESTB\FDSETUP\bin\p7zipr.exe [-15]
C:\TESTB\FDSETUP\bin\7zcon.sfx [-15]
-
3 Errors with D:\ARCHIVER\P7ZIP.ZIP 
C:\TESTB\FDSETUP\bin\p7zip.exe [-15]
C:\TESTB\FDSETUP\bin\p7zipr.exe [-15]
C:\TESTB\FDSETUP\bin\7zcon.sfx [-15]
-
1 Errors with D:\ARCHIVER\UNRAR.ZIP 
C:\TESTB\FDSETUP\bin\unrar.exe [-15]
-
1 Errors with D:\ARCHIVER\UNRAR.ZIP 
C:\TESTB\FDSETUP\bin\unrar.exe [-15]
-
1 Errors with D:\ARCHIVER\UNRAR.ZIP 
C:\TESTB\FDSETUP\bin\unrar.exe [-15]
-
1 Errors with D:\ARCHIVER\UPX.ZIP 
C:\TESTB\FDSETUP\bin\upx.exe [-15]
-
1 Errors with D:\ARCHIVER\UPX.ZIP 
C:\TESTB\FDSETUP\bin\upx.exe [-15]
-
1 Errors with D:\ARCHIVER\UPX.ZIP 
C:\TESTB\FDSETUP\bin\upx.exe [-15]




--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel