[Freedos-user] Desqview

[Jerome Ibanes]

I'm having an issue running Deskview 2.8 on FreeDos, which I would
describe as such:

- Desqview 2.8 can be freely downloaded at http://www.chsoft.com/dv.html
- I am not running QEMM (not required with Desqview).
- I do want to run Desqview, "accept no substitute".
- I am not running Dosbox.

The installation process runs fine, but upon starting Desqview, I run
across this error: "Missing (or bad) DESQview file: DESQVIEW.DVO".
Subsequently, the application is then unable to run dos applications.

Would anyone know how to address this issue? The file "DESQVIEW.DVO"
is indeed present in C:\DV (where I installed Desqview).

Thank you,
J.

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Desqview

[mcelhanon]

I have a retail box copy of DESQview version 2.42 with all the
accompanying manuals.  In the error messages appendix says the
following about this error:

"The DESQview command you performed tried to read the indicated
DESQview file, but couldn't."

"If you decide the indicated file is bad, delete it and then reinstall
DESQview.  There is no harm in reinstalling DESQview over the same
version of an existing system."

In addition, it says:

"Sometimes, loading memory-resident programs prior to starting up
DESQview, or allocating too few DOS file handles (by the FILES command
in your CONFIG.SYS file), can cause this error.  Also, if DESQview
cannot find the .DVO (Open Window Menu) file this message will appear
as a Startup Message."

On an installation of this program that I have on an old computer, the
DESQVIEW.DVO file is 249 bytes.  You are correct that QEMM is not
required (at least for the version I have) because I am running
DESQview 386 using MS HIMEM.SYS and EMM386.EXE without problems.  This
is because some IBM drivers I have for this old computer would not
work with QEMM.

I don't know if this is of any help, but it's all I know about the
problem.  Good luck.



On 7/12/13, Jerome Ibanes  wrote:
> I'm having an issue running Deskview 2.8 on FreeDos, which I would
> describe as such:
>
> - Desqview 2.8 can be freely downloaded at http://www.chsoft.com/dv.html
> - I am not running QEMM (not required with Desqview).
> - I do want to run Desqview, "accept no substitute".
> - I am not running Dosbox.
>
> The installation process runs fine, but upon starting Desqview, I run
> across this error: "Missing (or bad) DESQview file: DESQVIEW.DVO".
> Subsequently, the application is then unable to run dos applications.
>
> Would anyone know how to address this issue? The file "DESQVIEW.DVO"
> is indeed present in C:\DV (where I installed Desqview).
>
> Thank you,
> J.
>
> --
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Desqview

[john s wolter]

I have a license and have used this.  I see it as a wonder you've gotten
this far.

Cheers,
John S Wolter

LinkedIn: johnswolter 
johnswol...@wolterworks.com
USA, Eastern Standard Time, -5 GMT, -4 GMT DST



On Mon, Jul 15, 2013 at 10:55 AM,  wrote:

> I have a retail box copy of DESQview version 2.42 with all the
> accompanying manuals.  In the error messages appendix says the
> following about this error:
>
> "The DESQview command you performed tried to read the indicated
> DESQview file, but couldn't."
>
> "If you decide the indicated file is bad, delete it and then reinstall
> DESQview.  There is no harm in reinstalling DESQview over the same
> version of an existing system."
>
> In addition, it says:
>
> "Sometimes, loading memory-resident programs prior to starting up
> DESQview, or allocating too few DOS file handles (by the FILES command
> in your CONFIG.SYS file), can cause this error.  Also, if DESQview
> cannot find the .DVO (Open Window Menu) file this message will appear
> as a Startup Message."
>
> On an installation of this program that I have on an old computer, the
> DESQVIEW.DVO file is 249 bytes.  You are correct that QEMM is not
> required (at least for the version I have) because I am running
> DESQview 386 using MS HIMEM.SYS and EMM386.EXE without problems.  This
> is because some IBM drivers I have for this old computer would not
> work with QEMM.
>
> I don't know if this is of any help, but it's all I know about the
> problem.  Good luck.
>
>
--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Desqview

[Felix Miata]

On 2013-07-12 06:38 (GMT-0700) Jerome Ibanes composed:

> I'm having an issue running Deskview 2.8 on FreeDos, which I would
> describe as such:

> - Desqview 2.8 can be freely downloaded at http://www.chsoft.com/dv.html
> - I am not running QEMM (not required with Desqview).
> - I do want to run Desqview, "accept no substitute".
> - I am not running Dosbox.
>
> The installation process runs fine, but upon starting Desqview, I run
> across this error: "Missing (or bad) DESQview file: DESQVIEW.DVO".
> Subsequently, the application is then unable to run dos applications.
>
> Would anyone know how to address this issue? The file "DESQVIEW.DVO"
> is indeed present in C:\DV (where I installed Desqview).

The following is from CONFIG.SYS used on my last PC that would run QEMM and DV:

[MAX]
SWITCHES  =/F/W
DEVICE=C:\Q\QEMM386.SYS RAM ROM BE:N XSTI=1A X=F000-F8FF X=FE00-FEFF
SHELL=C:\Q\LOADHI.COM C:\DOS\COMMAND.COM C:\DOS\ /p /f /k C:\AE.BAT
set AUTOBAT=AE.BAT
set CONFIG=MAX
DOS =   HIGH
BUFFERS =   8
FILES   =   60
FCBS=   1,0
LASTDRIVE   =   Z
DEVICE=C:\Q\LOADHI.SYS C:\DOS\RAMDRIVE.SYS 6144 128 512 /E
set BUFFERS=SMALL
set RAMDISK=6144
set DOSHIGH=YES
BREAK=ON
STACKS=0,0

Maybe it holds a clue to a solution? I haven't used DV since 1997 when I 
found I needed full GUI internet access and made OS/2, the better DOS than 
DOS of that age and still, my primary OS.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Desqview

[mcelhanon]

The copy I have was being thrown away at the place I worked almost 2
decades ago.  I fooled around with it back then, experimenting with
the various configurations that are possible with DESQview, but never
found any real use for it that couldn't be done more flexibly with
other choices.  This current installation was just done by starting
with basic config.sys and autoexec.bat files (like what you get with
the default DOS installation) and then running the QEMM and DESQview
installation program, which creates new config.sys and autoexec.bat
files.  This setup the DESQview 386 configuration which uses Expanded
Memory to page the multiple DOS programs back and forth from the
program memory area (first 640KB).  It initially worked with QEMM just
fine, but when I started trying to load the IBM hardware drivers the
computer wouldn't boot.  So, I used the MS DOS memory management
(which is the same as IBM's PC DOS) and didn't have any problems.

It really didn't take any "guru-type" savvy to get it working, but it
can make it more tedious to make farther changes to the start-up
configuration files.  Providing you have enough memory, the program
doesn't seem to have any trouble juggling up to 4 DOS real-mode
programs (programs that will run in ~512KB ram).  It's sort of like
running command-line Linux with 4 virtual terminals open.


On 7/15/13, john s wolter  wrote:
> I have a license and have used this.  I see it as a wonder you've gotten
> this far.
>
> Cheers,
> John S Wolter
> 
> LinkedIn: johnswolter 
> johnswol...@wolterworks.com
> USA, Eastern Standard Time, -5 GMT, -4 GMT DST
>
>
>
> On Mon, Jul 15, 2013 at 10:55 AM,  wrote:
>
>> I have a retail box copy of DESQview version 2.42 with all the
>> accompanying manuals.  In the error messages appendix says the
>> following about this error:
>>
>> "The DESQview command you performed tried to read the indicated
>> DESQview file, but couldn't."
>>
>> "If you decide the indicated file is bad, delete it and then reinstall
>> DESQview.  There is no harm in reinstalling DESQview over the same
>> version of an existing system."
>>
>> In addition, it says:
>>
>> "Sometimes, loading memory-resident programs prior to starting up
>> DESQview, or allocating too few DOS file handles (by the FILES command
>> in your CONFIG.SYS file), can cause this error.  Also, if DESQview
>> cannot find the .DVO (Open Window Menu) file this message will appear
>> as a Startup Message."
>>
>> On an installation of this program that I have on an old computer, the
>> DESQVIEW.DVO file is 249 bytes.  You are correct that QEMM is not
>> required (at least for the version I have) because I am running
>> DESQview 386 using MS HIMEM.SYS and EMM386.EXE without problems.  This
>> is because some IBM drivers I have for this old computer would not
>> work with QEMM.
>>
>> I don't know if this is of any help, but it's all I know about the
>> problem.  Good luck.
>>
>>
>

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Desqview

[dmccunney]

On Tue, Jul 16, 2013 at 11:07 AM,   wrote:
> It really didn't take any "guru-type" savvy to get it working, but it
> can make it more tedious to make farther changes to the start-up
> configuration files.  Providing you have enough memory, the program
> doesn't seem to have any trouble juggling up to 4 DOS real-mode
> programs (programs that will run in ~512KB ram).  It's sort of like
> running command-line Linux with 4 virtual terminals open.

I used DV back in the day.  I knew a BBS sysop who ran successfully
four instances of Wildcat BBS software on a single 286 machine under
DV.  It allowed him to support multiple nodes without resorting to a
local network.  (He did need four modems and incoming phone lines.)
The trick was getting the time slicing right.

I still know someone who uses DV/X for most things, and boots into
Windows when he's doing something that can only be done under Windows.
 When he does boot into Windows, it's Win98SE, with an open source
package that adds enough of the Win32 extensions that he can run some
programs built for NT/2K/XP.

I ran the old MKS Toolkit under DOS, which provided DOS versions of
all the Unix commands that made sense in the single-user, single
tasking environment.  I got it because it had a nearly complete
version of the Unix Korn shell, with everything save asynchronous
background processes.  When installed in highest compatibility mode,
the Toolkit replaced COMMAND.COM with INIT.EXE as your boot shell.
Boot the system, and INIT ran, and printed Login: on your screen.
Enter a userid and optional password, and INIT called LOGIN.EXE  LOGIN
looked at a *nix compatible /etc/passwd file, and it it found a match
for the ID, changed to whatever was listed as that IDs directory and
ran what was specified as that ID's shell.

I loaded things common to all in CONFIG.SYS, like my RAMdisk, cache,
and mouse driver.  I had user IDs that ran vanilla COMMAND.COM, 4DOS,
the MKS Korn Shell, and DV.

Switching environment was a matter of exiting the shell I was in, and
putting in another ID at the Login: prompt.  I could do it without
rebooting.
__
Dennis
https://plus.google.com/u/0/105128793974319004519

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user