In Vax/VMS world we used a technique called "spawning" another process.
Seems there should be SOMETHING similar in Windows. In fact it should be
even easier since DQSD has no need to stay "attached" to the spawned process
and check its exit status.
Anyway I did most of my work in FORTRAN, COBOL and Assembler on minis and
mainframes. Don't know much about Windows development environment. Which
source code file actually does the call to run the browser?
I am still looking for a way to "trick" DQSD into staring IE 32 bit but no
joy so far.
Well Adobe has 64 bit Flash Player Beta add-ons for *nix. What/why they are
delaying on a Windows 64 bit is weird. I suspect that will change, but
when?
I don't believe Adobe has a 64 bit Shockwave version yet either.
-Original Message-
From: Charlie Russel [mailto:char...@scribes.com]
Sent: Thursday, May 14, 2009 2:35 PM
To: DQSD users mailing list
Subject: Re: [DQSD-Users] Windows 7 RC 64 Bit Install Help needed
The problem is, in a way, hard coded by the methods used. DQSD runs as a DLL
in Windows Explorer. As such, it makes "inproc" or in-process calls to other
executables. 64-bit processes can't make 32-bit calls, (and 32-bit processes
can't make 64-bit calls). I am NOT a developer, far from it, but it should
be technically possible to fork off the call in a way that would allow it to
call the 32-bit IE. But doing so is both non-trivial in Windows (which
doesn't really _do_ forks), and a significant shift from how the existing
32-bit code works. The intent was to not have two different code bases,
which would be required if we changed the way the browser gets called.
Charlie.
> -Original Message-
> From: James Nix [mailto:ni...@charter.net]
> Sent: May-14-09 8:25 AM
> To: 'DQSD users mailing list'
> Subject: Re: [DQSD-Users] Windows 7 RC 64 Bit Install Help needed
>
> All,
>
> Perhaps this has been mentioned before, perhaps not.
>
> Problem: DQSDx64 by default runs the 64 Bit IEXPLORE.EXE.
>
> This is a problem because many add-ons do not (yet) support the 64 bit
> IEXPLORE.
>
> Of particular note is Adobe Flash Player v10.
>
> DQSDx64 will, by default run C:\Program Files\Internet
> Explorer\iexplore.exe
>
> In Windows 7 64 Bit that is the 64 bit version of IE.
>
> The 32 bit version of IE is located, by default, in C:\Program Files
> (x86)\Internet Explorer\iexplore.exe
>
> I would think that most people (including me!) would want to use the 32
> bit
> IE for compatibility purposes.
>
> I did a quick check for an easy way to change the DQSDx64 target IE exe
> file
> but did not see one. Is it hard coded?
>
>
> Thanks!
>
>
>
> -Original Message-
> From: Kim Gräsman [mailto:kim.gras...@gmail.com]
> Sent: Wednesday, May 13, 2009 8:38 AM
> To: DQSD users mailing list
> Subject: Re: [DQSD-Users] Windows 7 RC 64 Bit Install Help needed
>
> James,
>
> Nice, thanks!
>
> One thing that stands out to me is the need to Unblock the entire
> archive, which presumably goes through the contents of the .zip and
> unblocks every single file.
>
> If only we could package this as an installer instead, that problem
> would go away. Problem is, we don't have any experience with free
> installer packages that support 64-bit Windows.
>
> - Kim
>
> On Mon, May 11, 2009 at 23:42, James Nix wrote:
> > Well, good news and bad news.
> >
> > The good news is I have it working.
> >
> > The bad news is it can be difficult to remove if the installation
> screws
> up
> > in a certain way. See notes below!!!
> >
> > The steps I came up with avoid some Windows 7 security checks without
> > disabling them altogether. I will list the general steps, not every
> Windows
> > UAC "Confirm this step" message. Note that I use TweakUAC to suppress
> most
> > of them anyway.
> >
> > 1) Download the dqsdx64-4100-beta.zip package to a location you will
> > remember. :-)
> >
> > 2) Right click the dqsdx64-4100-beta.zip package and select
> Properties.
> At
> > the bottom of the dialog there may be a message
> >
> > "Security: This file came from another computer and might be blocked
> to
> help
> > protect this computer"
> >
> > Click the "Unblock" button. Click "Apply" then close the Properties
> dialog.
> >
> > 3) Repeat Step 2 above and VERIFY THAT THERE IS NO SECURITY
> MESSAGE
> >
> > 4) Create a temporary folder for easy Command Window access - I used
> > C:\Temp. Unzip the dqsdx64-4100-beta.zip file (keeping folder names)
> into
> > C:\Temp.
> >
> > 5) Navigate to C:\Temp\DQSDx64. Check a couple of .JS files and
> verify
> > that the files do not have the "Security" message in their Properties
> (see
> > step 2).
> >
> > 6) Create a new desktop shortcut - Target: CMD.EXE ; Name "Command
> Window"
> >
> > 7) CREATE A SYSTEM RESTORE POINT. IF THE INSTALLATION SCREWS UP THE
> DQSD
> > CLOCK SCRIPT ERROR WILL MAKE IT DIFFICULT TO REMOVE DQSD. THE EASIEST
> "FIX"
> > IT IS TO DO A SYSTEM RESTORE.
> >
> > 8) Right click the Comm
