Re: [Freedos-devel] FDINST

[Tom Ehlert]

> 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


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

Re: [Freedos-devel] FDINST

[Tom Ehlert]

> 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
someone (the remove ?) trashed system memory.

this could be a bad behaved cache, memory manager or bad 'remove'

as the  rest has been around for a while, my first guess would be that
'remove' is the bad guy.

I'd try to

  install
  remove manually
  install

instead and see if that changes anything.

Anyway it's unlikely that FDNPKG is the bad behaving guy as it has
been around for a while.

just an educated guess, and good luck

Tom


--
___
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

Re: [Freedos-devel] FDINST

[Eric Auer]

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 memory footprint, but needs a
large INITIAL amount of memory which is often not free in UMB.

Instead, I recommend to use UMB more for CD and cache drivers.

> SHSUCDX /QQ /D3
> DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5

How are your experiences with UIDE / SHSUCDX cooperation? It
would be easier to load UIDE in config.sys otherwise...

> SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D /D:?FDCD0002,D 
> /D:?FDCD0003,D

If you ask me: Suspiciously complex SHSUCDX options. Also, the
/QQ probably means something like "no messages", which is bad
if you want to give the user a chance to report potential bugs!

> SHSUCDX /D

See above.

> SET AUTOFILE=%0
> SET CFGFILE=C:\FDCONFIG.SYS

Do you actually know if it is C: here? If you boot from CD, it
will most likely be A: instead of C:

Cheers, Eric



--
___
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.]

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 NOT use shellhigh with the XMS swap command.com:
> 
> It already has a small RESIDENT memory footprint, but needs a
> large INITIAL amount of memory which is often not free in UMB.
> 
> Instead, I recommend to use UMB more for CD and cache drivers.
> 
>> SHSUCDX /QQ /D3
>> DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5
> 
> How are your experiences with UIDE / SHSUCDX cooperation? It
> would be easier to load UIDE in config.sys otherwise...
> 
>> SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D /D:?FDCD0002,D 
>> /D:?FDCD0003,D
> 
> If you ask me: Suspiciously complex SHSUCDX options. Also, the
> /QQ probably means something like "no messages", which is bad
> if you want to give the user a chance to report potential bugs!
> 
>> SHSUCDX /D
> 
> See above.
> 
>> SET AUTOFILE=%0
>> SET CFGFILE=C:\FDCONFIG.SYS
> 
> Do you actually know if it is C: here? If you boot from CD, it
> will most likely be A: instead of C:
> 

The above config files are just super stripped down "default FreeDOS 1.1” 
configuration
files on an installed system. Being used to do bug and crash detection of 
FDINST.

At preset, FDI (FreeDOS 1.2+ Installer) uses an even more stripped down 
configuration.
Mostly it just loads everything to lower memory, loads the cd-driver and disk & 
floppy caching.
 
FDI more or less just installs the same configuration that FreeDOS 1.1 creates. 
It customizes
it dynamically to use the settings and choices that are made when running the 
installer.

> Cheers, Eric
> 
> 
> 
> --
> ___
> 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