OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: mauro on January 13, 2024, 12:22:25 pm
-
Hi all, I'm finding this issue: my previous DFSee installation was the evaluation one, now asking for a valid key to run. I've found on the eCSoft/2 pages this version defined free-open source and installed it replacing the expired one, providing its uninstallation before.
In the new situation, running the object DFSOS2 returns an error window in the middle of a command-prompt window (see image). Also trying to start the RUN DFSee object returns same error alert, not specifying anything else than "IBMS506$ device does not recognize the command", which I cannot translate in something useful.
Is anyone aware of what can be done to run this DFSee ?
Thank you much
-
What happens if you ignore the error and continue?
-
no way to get out from there until I select End program/commad/operation
-
Did you totally remove the old version before you installed v17? What you are describing sounds as if there are parts of the old version still around especially if you installed it in the previous dir.
Delete the DFSee directory, run clean ini and or xfix, then install the new version. That is what I do when installing newer versions of existing programs it prevents old information being carried over.
-
Add "AUTOFAIL=YES" to your 'config.sys'. It prevents this sort of popup and always returns an error to the app.
-
Did you totally remove the old version before you installed v17? What you are describing sounds as if there are parts of the old version still around especially if you installed it in the previous dir.
I've uninstalled the old version through Warpin, which was the installation app used, believing it was safe enuogh
Delete the DFSee directory, run clean ini and or xfix, then install the new version. That is what I do when installing newer versions of existing programs it prevents old information being carried over.
run clean ini and xfix are 3rd party utilities or available in the system?
-
Hi mauro
Might be worth simply deleting the contents of the dfsee directory and then unzipping(?) the latest version into that directory.
What the error seems to be saying is that the loaded disk driver IBM1S506.ADD does not understand whatever command from dfsee. When starting dfsee it seems that disk(s) get read for partition info so that is probably the failing bit. Strange...
What version (how old) is the IBM1S506.ADD in use? - might be worth trying danis506 as I recall that overcame some of the early IBM1S506 deficiencies.
Regards
Pete
-
Hi mauro
Might be worth simply deleting the contents of the dfsee directory and then unzipping(?) the latest version into that directory.
Thank you Pete , it hasn't worked
Regards
Pete
-
Hi mauro,
One other thing you might try is to delete the DFSee partition then run xfix and or checkini with the parameters /C /H /T Doing that will remove a lot of useless info from the ini files.
-
Hi all, I'm finding this issue: my previous DFSee installation was the evaluation one, now asking for a valid key to run. I've found on the eCSoft/2 pages this version defined free-open source and installed it replacing the expired one, providing its uninstallation before.
In the new situation, running the object DFSOS2 returns an error window in the middle of a command-prompt window (see image). Also trying to start the RUN DFSee object returns same error alert, not specifying anything else than "IBMS506$ device does not recognize the command", which I cannot translate in something useful.
Is anyone aware of what can be done to run this DFSee ?
Thank you much
I downloaded my copy from the ARCA NOAE. It was listed as sponser and support software. I made a donation, downloaded and installed. Everything works great. I noticed it since has been removed.
-
It is still available from the DFSee site.
-
Hi mauro
Might be worth simply deleting the contents of the dfsee directory and then unzipping(?) the latest version into that directory.
What the error seems to be saying is that the loaded disk driver IBM1S506.ADD does not understand whatever command from dfsee. When starting dfsee it seems that disk(s) get read for partition info so that is probably the failing bit. Strange...
What version (how old) is the IBM1S506.ADD in use? - might be worth trying danis506 as I recall that overcame some of the early IBM1S506 deficiencies.
Regards
Pete
ok Pete, I've downloaded the zip file who generate -as usual- a folder, but no explainations (no specific readme) on how proceed to replace the old IBM1S506.ADD
-
It's a drop in replacement. Find your BASEDEV=IBM1S506.ADD, rem it and add a line right after BASEDEV=DANIS506.add along with any parameters that IBM1S506.ADD had.
I notice my config.sys has BASEDEV=DANIS506.ADD /!BIOS
-
Hi mauro,
One other thing you might try is to delete the DFSee partition then run xfix and or checkini with the parameters /C /H /T Doing that will remove a lot of useless info from the ini files.
Hi Ivan, did everyting you wrote in this order:
-uninstalled previous DFsee by Warpin deinstaller
-deleted its previous working directory (C:/TOOLS)
-rebooted
-applied XFIX, removed all invalid entries and saved action on OS2.INI
-rebooted
-applied CHECKINI, went all at the end of items scanning and then confirmed end of session (is that what the way to apply the cleaning? No confirmation read about result)
-rebooted
-installed DFSee 17 free downloaded from ecsoft/2
-run DFSee 17
-SAME ERROR MESSAGE
-uninstalled DFSee 17 by Warpin deinstaller
-deleted its previous working directory (C:/TOOLS)
-rebooted
-downloaded DFSee 17 beta from https://www.dfsee.com/download/
-installed it
-run DFSee 17 beta
-SAME ERROR MESSAGE
I think have followed slavishly all necessary steps to accomplish this attempts.
Thank you
-
It's a drop in replacement. Find your BASEDEV=IBM1S506.ADD, rem it and add a line right after BASEDEV=DANIS506.add along with any parameters that IBM1S506.ADD had.
I notice my config.sys has BASEDEV=DANIS506.ADD /!BIOS
ok, then it's only DANIS.506.ADD file to be placed in same directory where IBM1S506.ADD is ?
Do I ignore the other files in the decompressed directory?
Tks
-
Hi mauro
Copy danis506.add and daniatap.flt to [BootDrive]:\os2\boot
Open [BootDrive]:\config.sys and add the following 2 lines
BASEDEV=DANIS506.ADD /!BIOS
BASEDEV=DANIATAP.FLT
then REM the start of these lines if they exist
BASEDEV=IBM1S506.ADD
BASEDEV=IBMATAPI.FLT
BASEDEV=IBMIDECD.FLT
Save config.sys
Reboot
Test DFSee
Regards
Pete
-
I also have BASEDEV=DANIATAP.FLT right after the DANIS506.ADD line. Right now I can't remember what it replaces or if it replaces something, check the documentation. The DANIS506.ADD should be OK on its own.
-
Hi Dave
Memory nudge: daniatapi.flt replaces the 2 files IBMATAPI.FLT and IBMIDECD.FLT
Regards
Pete
-
Hi mauro
Copy danis506.add and daniatap.flt to [BootDrive]:\os2\boot
Open [BootDrive]:\config.sys and add the following 2 lines
BASEDEV=DANIS506.ADD /!BIOS
BASEDEV=DANIATAP.FLT
then REM the start of these lines if they exist
BASEDEV=IBM1S506.ADD
BASEDEV=IBMATAPI.FLT
BASEDEV=IBMIDECD.FLT
Save config.sys
Reboot
Test DFSee
Regards
Pete
Ok Pete, it has worked! Now we know that DFSee 17 (guess other software as well) needs DANIS506.ADD and DANIATAP.FLT to replace IBM1S506.ADD and IBMATAPI.FLT .
Thank you much
-
Hi All
I seem to have found a problem with DFSee 17 and creating Desktop objects.
In the dfsee bin directory is the file dfswpobj.cmd which is meant to create all DFSee Desktop objects.
When I run that file it reports lots of objects created successfully - and nothing appears on the Desktop.
Anyone else seeing this? - you will need to delete existing DFSee Desktop objects to test this so I suggest Desktop backup *before* testing.
Regards
Pete
-
not my case, desktop objects in DFSee 17 installation were correctly created on the desktop.
All I can say about is that I first provided the uninstallation of the previous version both by WarpIn and then deleting the DFSee directory in HOME:\TOOLS
-
Most probable reason for your issue is using an old BASEDEV=IBM1S506.ADD which had a small partition size limit. Later versions corrected this and Dani's driver always had no small drive limit
-
Most probable reason for your issue is using an old BASEDEV=IBM1S506.ADD which had a small partition size limit. Later versions corrected this and Dani's driver always had no small drive limit
confirm this has fixed the issue in my case