On 13/12/2015 16:21, Jerome E. Shidel Jr. wrote:
> You need to update your online repo and all_cd.iso to contain the fixed
> version of FDINST.
Absolutely. But I need to publish a new formal release with latest
FDNPKG/FDINST version first. Then I will update the all_cd with the new
package, and
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
[email protected]
On my side I found why your floppy image didn't bring me CDROM support
at all: UIDE was failing to load with an "XMS init error". Apparently it
requires more than 4M of RAM (I have allocated 4M of RAM to my VM),
which is probably expected, since it's supposed to perform caching.
Anyway, UDVD2 w
> On Dec 10, 2015, at 6:38 AM, Mateusz Viste 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
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 mi
> On Dec 10, 2015, at 1:51 AM, Mateusz Viste 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 real
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.
Here is "my" version of your floppy pkg tester:
goph
Nice image, thanks! I cannot use it though, I will have to fix it first.
A few observations:
You don't seem to declare a DOSDIR variable.
In FDCONFIG, I see this:
DOS=HIGH
DOS=UMB
Not sure if this is supposed to work. I have always only seen this instead:
DOS=HIGH,UMB
For tests, it might be be
> On Dec 7, 2015, at 12:47 AM, Mateusz Viste 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 e
Hi,
On Dec 6, 2015 11:48 PM, "Mateusz Viste" wrote:
> 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 i
> On Dec 7, 2015, at 12:47 AM, Mateusz Viste wrote:
>
> Could you confirm please that these tests were performed using the
> latest version of both the all_cd.iso and fdinst?
This was running against previous version of all_cd.iso. Not, latest. As I
said, I have limited bandwidth to download
Could you confirm please that these tests were performed using the
latest version of both the all_cd.iso and fdinst?
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 li
> 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
> 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
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 pa
I uploaded the devel version from today: gopher://gopher.viste.fr/1/temp
In this one I slightly optimized the memory usage, removed LFN support
(too dangerous!) and added explicit checks of filenames sanity, before
installing any package.
Now, any package that contains non-8+3 filenames will be
On 02/12/2015 23:40, Jerome Shidel wrote:
> It did not freeze or lockup.
That's some success already :) This would confirm that the lockups and
crashes were due to tinfl behaving badly on 16bit. That's good.
> There were multiple issues and about 2500 errors (total). Containing -2,-3,-4
> and -
On 02/12/2015 23:57, Rugxulo wrote:
> Honestly, there's not much to do about it. If you see that a file uses
> invalid chars or is longer than 8.3, just either ignore it or rename
> it.
I think that's what I will end up doing indeed. LFN in DOS always has
been a hack anyway. Also, it's the second
Hi,
On Wed, Dec 2, 2015 at 2:28 AM, Mateusz Viste wrote:
>
> 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 link
> On Dec 2, 2015, at 11:14 AM, "Jerome E. Shidel Jr." wrote:
>
>
>> 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'
> 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
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 reasonab
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
On 30/11/2015 20:48, Louis Santillan wrote:
> I would post an issue to Richard Geldreich's miniz project site [0].
I did write to him yesterday already.
> Rich also intended for tinfl to be
> RFC compliant, so if there is an issue, he may want to address it.
The problem has nothing to do with RF
I would post an issue to Richard Geldreich's miniz project site [0].
Though he's focused on lzham these days, he's usually pretty good
about responding to bug reports. Rich also intended for tinfl to be
RFC compliant, so if there is an issue, he may want to address it.
[0] https://github.com/ric
Hello,
Quick mail to say that although I had no time to work on the issue, I
did a quick investigation and confirmed that the problem comes from the
DEFLATE library I use (TINFL, from the Miniz suite). This library
behaves differently when compiled under DJGPP (FDNPKG) and Watcom
(FDINST). In
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 on
Hello Eric,
> On Nov 28, 2015, at 5:26 PM, Eric Auer wrote:
>
>
> Hi Jerome,
>
>> COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS
>
>> 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
>
> I recommend to
Hi Jerome,
> COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS
> 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
I recommend to NOT use shellhigh with the XMS swap command.com:
It already has a small RESIDENT me
> 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. (S
> COMMAND, DJGPP_RH, NASM. Install ok, remove ok, reinstall system
> freeze/lockup.
> HELP. Install ok, remove ok, reinstall system memory corrupt crash.
> ...
re-install should be exactly the same as install.
if it behaves differently, this is a HUGE hint that in the meantime
s
> 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 instal
> On Nov 27, 2015, at 2:32 PM, Mateusz Viste wrote:
>
> Wow, that's a huge QA automation you developed there, it looks
> impressive! Thanks for sharing your results, I will get into this in
> upcoming days.
Thanks, it is built out of Batch + V8Power Tools + Grep.
:)
>
> BTW, what kind of v
Wow, that's a huge QA automation you developed there, it looks
impressive! Thanks for sharing your results, I will get into this in
upcoming days.
BTW, what kind of virtual machine do you use? VirtualBox? Qemu? Bochs?
Something else? It's just in case I can't reproduce the problems easily,
so
> On Nov 27, 2015, at 3:58 AM, Mateusz Viste wrote:
>
> On 27/11/2015 05:55, Jerome E. Shidel Jr. wrote:
>> Unfortunately, I don’t have access to any functional gopher clients.
>
> You can use a gopher proxy :) Here is a link:
>
> http://gopherproxy.meulie.net/gopher.viste.fr/1/temp
>
> Mateu
On 27/11/2015 05:55, Jerome E. Shidel Jr. wrote:
> Unfortunately, I don’t have access to any functional gopher clients.
You can use a gopher proxy :) Here is a link:
http://gopherproxy.meulie.net/gopher.viste.fr/1/temp
Mateusz
--
Unfortunately, I don’t have access to any functional gopher clients.
I ended up putting a package tester in the install media boot disc creator.
If you want to just email me the latest version of FDINST, that would be fine.
---
> On Nov 24, 2015, at 1:35 PM, Mateusz Viste wrote:
>
> On 24/11/2015 18:38, Jerome E. Shidel Jr. wrote:
>> That fixed the problem with the attrib package.
>> But, now there is a new problem. :(
>> FDINST locks-up while extracting the help package.
>
> That's a bug specific to FDINST. FDNPKG wo
> On Nov 24, 2015, at 1:35 PM, Mateusz Viste wrote:
>
>> On 24/11/2015 18:38, Jerome E. Shidel Jr. wrote:
>> That fixed the problem with the attrib package.
>> But, now there is a new problem. :(
>> FDINST locks-up while extracting the help package.
>
> That's a bug specific to FDINST. FDNPKG
On 24/11/2015 18:38, Jerome E. Shidel Jr. wrote:
> That fixed the problem with the attrib package.
> But, now there is a new problem. :(
> FDINST locks-up while extracting the help package.
That's a bug specific to FDINST. FDNPKG works fine. In fact, the bug is
present in the source code of both
Is it a VOLUME conflict?I honestly don't really mess with FDNPKG too
much,so I wouldn't really know how the source code was compiled and how it
works.
On Tue, Nov 24, 2015 at 12:38 PM, Jerome E. Shidel Jr.
wrote:
>
> > On Nov 24, 2015, at 12:31 AM, Mateusz Viste wrote:
> >
> > On 23/11/2015 20:
> On Nov 24, 2015, at 12:31 AM, Mateusz Viste wrote:
>
> On 23/11/2015 20:53, Jerome E. Shidel Jr. wrote:
>>> FDNPKG v0.99.3 fixes this issue.
>>
>> So, is it going to be fixed in FDINST?
>
> It is fixed, FDINST uses FDNPKG. Any fix inside FDNPKG's core applies
> also to FDINST, too. Sorry if
On 23/11/2015 20:53, Jerome E. Shidel Jr. wrote:
>> FDNPKG v0.99.3 fixes this issue.
>
> So, is it going to be fixed in FDINST?
It is fixed, FDINST uses FDNPKG. Any fix inside FDNPKG's core applies
also to FDINST, too. Sorry if that was unclear.
> End result, any attempt to use attrib will cause
I could work around this issue or possible revert back to just using unzip.
But, I don’t think it should have to do that. And I would rather use a package
manager.
> On Nov 23, 2015, at 12:44 PM, Mateusz Viste wrote:
>
> On 22/11/2015 20:39, Jerome E. Shidel Jr. wrote:
>> I’ve tried recompressin
On 22/11/2015 20:39, Jerome E. Shidel Jr. wrote:
> I’ve tried recompressing them multiple ways, but that either
> causes FDINST to choke on all of the files. Or, just fail at the
> same point.
In fact, the problem is not about compression, but the lack of it.
I introduced a 1-byte bug in v0.99.2
Having a problem two problems using FDINST in FDI.
1) There are several packages it fails to extract.
They extract fine using unzip, but have problems in FDINST.
I’ve tried recompressing them multiple ways, but that either
causes FDINST to choke on all of the files. Or, just fail at the
s
46 matches
Mail list logo
