PDA

View Full Version : Windows 95 error



NewsArchive
09-12-1997, 12:00 AM
When I tried to install a my delphi app using MS ACCESS 95 on a Windows NT
PC it hung up after the reboot option. The same install has been working
fine on Windows 95 PC's. Is there anything different that needs to be set
for windows NT PC's? After trying to reboot it says Error during startup
process run recovery and locks out the keyboard. Have not been able to get
the PC working. I guess I will have to load Windows NT for the user again.
Any Ideas?

NewsArchive
06-10-1998, 12:00 AM
Hi,
InstallShield support has created an InstallScript-based extension function
for this purpose. See knowledge base article Q101296 "HOWTO: Determining
Target Operating System by Calling the Function _GetOS" on
http://support.installshield.com

Stefan Krueger
Software Engineer
skrueger@usa.net

*** InstallSite - Free resources for setup developers
*** http://www.ibv-tools.de

Ken McKinney schrieb in Nachricht <357DB835.C7F98B3C@adaptivemedia.com>...
>I've got an additional question (sorry, no answer to yours:)
>
>Will the InstallShield GetSystemInfo( OS, nvResult, svResult ) API call
>return whether the user is on Windows98? At the very least, if Windows98
>is not supported, we should have a means to detect its presence and abort
the
>install.
>
>Ken McKinney
>
>Stan Loll wrote:
>
>> I am a registered user of InstallShield 5.1(build 147). Is Windows 98
>> supported? Will I need to download a new version? Will installations
made
>> now work on Windows 98? When I asked tech support, I was told my 30 day
>> support had expired. Go figure.
>>
>> Stan Loll, sloll@lolltech.com
>
>
>

NewsArchive
08-08-2000, 12:00 AM
490?!? But Version9X = 500 for Windows 98. It has to at least be higher
than that.

"Andreas Magnusson" <andreas_ch_m@hotmail.com> wrote in message
news:398ef68d.0@208.30.171.38...
> From the latest documentation:
> Windows ME: Version9X=490, WindowsBuild (if you need)= 2494 or greater.
> /Andreas
> "Raymond Saxe" <rsaxe@knosysinc.com> wrote in message
> news:398ed914.0@208.30.171.38...
> > To detect Windows ME, would it show up as Version9X = 600?
> >
> >
>
>

NewsArchive
08-08-2000, 12:00 AM
Well, OK. I just made a test install for a Windows ME image, and sure
enough, Version9X = 490. Does anybody have any conceivable idea why this
should be the version number??? I don't have access to the Windows ME
documentation. What does it say???

"Raymond Saxe" <rsaxe@knosysinc.com> wrote in message
news:39902223.0@208.30.171.38...
> 490?!? But Version9X = 500 for Windows 98. It has to at least be higher
> than that.
>
> "Andreas Magnusson" <andreas_ch_m@hotmail.com> wrote in message
> news:398ef68d.0@208.30.171.38...
> > From the latest documentation:
> > Windows ME: Version9X=490, WindowsBuild (if you need)= 2494 or greater.
> > /Andreas
> > "Raymond Saxe" <rsaxe@knosysinc.com> wrote in message
> > news:398ed914.0@208.30.171.38...
> > > To detect Windows ME, would it show up as Version9X = 600?
> > >
> > >
> >
> >
>
>

NewsArchive
08-08-2000, 12:00 AM
My fault. I could've sword that the version number of Win98 was 5.00, but
it's 4.10. Must've gotten some bad information in the past, or maybe there
was something funny in that salmon I had for dinner last night. ;-)

"Raymond Saxe" <rsaxe@knosysinc.com> wrote in message
news:399037d1.0@208.30.171.38...
> Well, OK. I just made a test install for a Windows ME image, and sure
> enough, Version9X = 490. Does anybody have any conceivable idea why this
> should be the version number??? I don't have access to the Windows ME
> documentation. What does it say???
>
> "Raymond Saxe" <rsaxe@knosysinc.com> wrote in message
> news:39902223.0@208.30.171.38...
> > 490?!? But Version9X = 500 for Windows 98. It has to at least be
higher
> > than that.
> >
> > "Andreas Magnusson" <andreas_ch_m@hotmail.com> wrote in message
> > news:398ef68d.0@208.30.171.38...
> > > From the latest documentation:
> > > Windows ME: Version9X=490, WindowsBuild (if you need)= 2494 or
greater.
> > > /Andreas
> > > "Raymond Saxe" <rsaxe@knosysinc.com> wrote in message
> > > news:398ed914.0@208.30.171.38...
> > > > To detect Windows ME, would it show up as Version9X = 600?
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
08-08-2000, 12:00 AM
Documented in the latest msi.chm:
Windows ME: Version9X=490

> But Version9X = 500 for Windows 98.

No. Version9X = 410 for Windows 98

Maybe you confused with:

VersionNT = 500 for Windows 2000.

--
Stefan Krueger - Independent Setup Consultant
<<reply-to address is invalid to avoid spam>>

Visit InstallSite at http://www.installsite.org to download
free code samples, tips, tools and more...
For information about individual support and consulting services
please send a blank mail to the autoresponder at info@installsite.org

Stefan Krueger and the InstallSite.org web site are not affiliated
with InstallShield Software Corporation.

NewsArchive
09-15-2000, 12:00 AM
Uhoh! Well, this new system that I will be authoring and designer on has ME
loaded, so I guess we'll see what happens!! :)

Since ME is not a supported platform, will any problems or support questions
I have for this platform, be curbed?

Aaron Rayner


"Chandy Navaratan" <supportnews@installshield.com> wrote in message
news:39c1dcdd$1@12.41.20.38...
> Hi Aaron,
>
> We are not aware of any issues specific to Windows Me although I must say
> that Windows Me is not one of the supported platforms as of 6.5x. Hope
this
> helps.
>
> --
> Chandy Navaratan
> DemoShield Development
> http://www.demoshield.com
>
>
> "ERIN D RAYNER" <erinrayner@PRODIGY.NET> wrote in message
> news:39c194ca$1@12.41.20.38...
> > What are the issues with Windows ME and DS 6.51? Anyone?
> >
> > Aaron Rayner
> >
> >
> >
> >
>
>

NewsArchive
10-10-2000, 12:00 AM

NewsArchive
10-12-2000, 12:00 AM
You can install on Windows Me now by using "Any OS" in the Requirements
view. My previous post was too brief - what is not supported is the ability
to install a different version of a specific file to the Me version (using
the Advanced tab of the Properties dialog in Files view).

Dominique Busso <dbusso@francenet.fr> wrote in message
news:39E36B3E.72F26BD2@francenet.fr...
> Madhavi Gullapalli wrote:
> >
> > In the next release.
> >
> > Peter Upfold <peter@statmon.com> wrote in message
> > news:39cfb384$1@12.41.20.38...
> > > The target platform option does not support Windows Me, Is this being
> > > addressed quickly ?
> > >
>
> Meaning we can not install on Windows ME now?

NewsArchive
10-20-2000, 12:00 AM
Did not know you could do that......No I have not
"Olga-InstallShield" <supportnews@installshield.com> wrote in message
news:39f0cc54$1@12.41.20.38...
> Hello Shane,
>
> Did you try SYSINFO.WIN9X.bWinMe?
>
> --
> Sincerely,
>
> Olga K.
> InstallSheild Technical Support
>
> "Shane Rose" <moab_runner@hotmail.com> wrote in message
> news:39f0bac0$1@12.41.20.38...
> > How do you tell the difference between Windows 98 and Windows ME? The
> > sysinfo returns Windows 98.
> > Thanks,
> > Shane
> >
> >
>
>

NewsArchive
10-20-2000, 12:00 AM
I am using installshield 6.1, it does won't compile with bWinMe or bWinME.
Is there a newer version that takes care of this or maybe a patch. It says
that is cannot find the member name bWinMe.
Thanks,
Shane
"Olga-InstallShield" <supportnews@installshield.com> wrote in message
news:39f0cc54$1@12.41.20.38...
> Hello Shane,
>
> Did you try SYSINFO.WIN9X.bWinMe?
>
> --
> Sincerely,
>
> Olga K.
> InstallSheild Technical Support
>
> "Shane Rose" <moab_runner@hotmail.com> wrote in message
> news:39f0bac0$1@12.41.20.38...
> > How do you tell the difference between Windows 98 and Windows ME? The
> > sysinfo returns Windows 98.
> > Thanks,
> > Shane
> >
> >
>
>

NewsArchive
10-21-2000, 12:00 AM
WinME is Windows 9x version 4.90. Checking WINMAJOR and WINMINOR should tell
you the difference.
Win95 = 4.0
Win98 = 4.10
WinME = 4.90

--
Stefan Krueger - Independent Setup Consultant
<<reply-to address is invalid to avoid spam>>

Visit InstallSite at http://www.installsite.org to download
free code samples, tips, tools and more...
For information about individual support and consulting services
please send a blank mail to the autoresponder at info@installsite.org

Stefan Krueger and the InstallSite.org web site are not affiliated
with InstallShield Software Corporation.

Shane Rose <moab_runner@hotmail.com> schrieb in im Newsbeitrag:
39f0d1f8$1@12.41.20.38...
> I am using installshield 6.1, it does won't compile with bWinMe or bWinME.
> Is there a newer version that takes care of this or maybe a patch. It
says
> that is cannot find the member name bWinMe.
> Thanks,
> Shane
> "Olga-InstallShield" <supportnews@installshield.com> wrote in message
> news:39f0cc54$1@12.41.20.38...
> > Hello Shane,
> >
> > Did you try SYSINFO.WIN9X.bWinMe?
> >
> > --
> > Sincerely,
> >
> > Olga K.
> > InstallSheild Technical Support
> >
> > "Shane Rose" <moab_runner@hotmail.com> wrote in message
> > news:39f0bac0$1@12.41.20.38...
> > > How do you tell the difference between Windows 98 and Windows ME? The
> > > sysinfo returns Windows 98.
> > > Thanks,
> > > Shane
> > >
> > >
> >
> >
>
>

NewsArchive
11-27-2000, 01:00 AM
I'm using InstallShield 6.12 and when I use SYSINFO, I've got the following
error : bWinMe : member name not found.

Where's the problem ?

Guillaume.

"Arpe-InstallShield" <supportnews@installshield.com> a écrit dans le message
news: 3a22879c$1@12.41.20.38...
> Guillaume,
>
> Please look at the help document for the functin SYSINFO. The following
> code will detect Windows ME:
>
> if (SYSINFO.WIN9X.bWinMe ) then
> MessageBox("Installing on Windows ME",INFORMATION);
> endif;
>
> Sincerely,
>
> --
> Arpe
> InstallShield Technical Support
>
> "Guillaume" <gmarie@genilink.com> wrote in message
> news:3a227ed5@12.41.20.38...
> > Hi,
> >
> > I'm sorry to post a message about that again but is anyone can explain
to
> me
> > how I can detect Windows Me because I don't have access to the old post
?
> >
> > Thanx
> >
> > Guillaume
> >
> >
>
>

NewsArchive
11-27-2000, 01:00 AM
bWinMe was introduced with IS 6.22.

You may also want to read the article at
http://www.installshield.com/email/0011.htm#eight

--
Stefan Krueger - Independent Setup Consultant
<<reply-to address is invalid to avoid spam>>

Visit InstallSite at http://www.installsite.org to download
free code samples, tips, tools and more...
For information about individual support and consulting services
please send a blank mail to the autoresponder at info@installsite.org

Stefan Krueger and the InstallSite.org web site are not affiliated
with InstallShield Software Corporation.

"Guillaume" <gmarie@genilink.com> schrieb im Newsbeitrag
news:3a228b84@12.41.20.38...
> I'm using InstallShield 6.12 and when I use SYSINFO, I've got the
following
> error : bWinMe : member name not found.
>
> Where's the problem ?
>
> Guillaume.
>
> "Arpe-InstallShield" <supportnews@installshield.com> a écrit dans le
message
> news: 3a22879c$1@12.41.20.38...
> > Guillaume,
> >
> > Please look at the help document for the functin SYSINFO. The
following
> > code will detect Windows ME:
> >
> > if (SYSINFO.WIN9X.bWinMe ) then
> > MessageBox("Installing on Windows ME",INFORMATION);
> > endif;
> >
> > Sincerely,
> >
> > --
> > Arpe
> > InstallShield Technical Support
> >
> > "Guillaume" <gmarie@genilink.com> wrote in message
> > news:3a227ed5@12.41.20.38...
> > > Hi,
> > >
> > > I'm sorry to post a message about that again but is anyone can
explain
> to
> > me
> > > how I can detect Windows Me because I don't have access to the
old post
> ?
> > >
> > > Thanx
> > >
> > > Guillaume
> > >
> > >
> >
> >
>
>

NewsArchive
11-27-2000, 01:00 AM
Guillaume,

ME came out after IS 6.1x was released. Using SYSINFO to detect Windows ME
with IS 6.2X works. Sorry, I wasn't aware of the version you were using.

Sincerely,

--
Arpe
InstallShield Technical Support


"Guillaume" <gmarie@genilink.com> wrote in message
news:3a228b84@12.41.20.38...
> I'm using InstallShield 6.12 and when I use SYSINFO, I've got the
following
> error : bWinMe : member name not found.
>
> Where's the problem ?
>
> Guillaume.
>
> "Arpe-InstallShield" <supportnews@installshield.com> a écrit dans le
message
> news: 3a22879c$1@12.41.20.38...
> > Guillaume,
> >
> > Please look at the help document for the functin SYSINFO. The following
> > code will detect Windows ME:
> >
> > if (SYSINFO.WIN9X.bWinMe ) then
> > MessageBox("Installing on Windows ME",INFORMATION);
> > endif;
> >
> > Sincerely,
> >
> > --
> > Arpe
> > InstallShield Technical Support
> >
> > "Guillaume" <gmarie@genilink.com> wrote in message
> > news:3a227ed5@12.41.20.38...
> > > Hi,
> > >
> > > I'm sorry to post a message about that again but is anyone can explain
> to
> > me
> > > how I can detect Windows Me because I don't have access to the old
post
> ?
> > >
> > > Thanx
> > >
> > > Guillaume
> > >
> > >
> >
> >
>
>

NewsArchive
11-30-2000, 01:00 AM
Well, I tried the 6.2 version, but still get the same problem..
again, only on Windows ME.. here is the code I am using to try to
browse the network for a network printer:

function DialogShowAskPath()

STRING szTitle, szMsg;
NUMBER nCreateDialog, nId, nResult;
BOOL bDone;

begin
nCreateDialog = EzDefineDialog(CUST_DIAG_PORT, ISUSER,"",30001);

//Display dialog
bDone = FALSE;
while (bDone=FALSE)
nId = WaitOnDialog(CUST_DIAG_PORT);
switch(nId)
case DLG_INIT:

case SD_PBUT_CONTINUE:
bDone = TRUE;
case SD_PBUT_BACK:
bDone = TRUE;
nResult = SD_PBUT_BACK;
case SD_PBUT_EXITSETUP:
Do(EXIT);
case BROWSEBUTTON:
DialogNetworkPrinter( svPrinterPath );
CtrlSetText(CUST_DIAG_PORT, 30130,
svPrinterPath);
case DLG_ERR:
MessageBox(ERROR_DIALOG, SEVERE);
bDone = TRUE;
endswitch;

endwhile;
CtrlGetText(CUST_DIAG_PORT, 30130, svPrinterPath);
EndDialog(CUST_DIAG_PORT);
ReleaseDialog(CUST_DIAG_PORT);
return nResult;
end;

This works fine on all other versions of Windows, but on ME it simply
browses to the Desktop, and does not allow me to see the Network or
Local system drives...

On Wed, 29 Nov 2000 19:30:49 -0600, "Kevin-InstallShield"
<supportnews@installshield.com> wrote:

>Hello Benny,
>
>Windows ME came out after IS Pro 6.1x. Therefore InstallShield begins
>Windows ME support with 6.22. To prove that this will work for you you can
>download the eval version of 6.22 and try it. To get the eval version visit
>our web site, www.installshield.com and you can download it from our
>Products tab.
>
>Have a good day Benny.
>
>-Kevin
>InstallShield Tech Support
>
>
>"Benny Nabours" <nabours1@earthlink.net> wrote in message
>news:3a25587f.592809915@news.installshield.com...
>> Hi everyone.
>>
>> I have an interesting predicament...
>>
>> I have a Browse Network dialog in my installation, when the install is
>> running, the Browse for Network Printer dialog comes up. This works
>> fine on all versions of Windows EXCEPT Windows ME. When I run the
>> install on all other version, if you click browse, it brings up the
>> following:
>>
>> Desktop -
>> My Computer-
>> <floppy drive>
>> <hard drive>
>> <Network Neighborhood>
>> <Mapped drives, etc...>
>>
>> When I run this command on Windows ME , it brings up the Desktop, with
>> all desktop shortcuts only, no access to My Computer, no access to
>> Network Neghborhood, etc... Any idea why this might be happening?
>> Is there a bug with IS 6.10 and Windows ME? Would upgrading to 6.22
>> fix this problem?
>>
>> If I can supply you with more information, I would be happy to..
>>
>> Thank you in advance for ANY assistance or advice you may be able to
>> offer.
>>
>> -Benny
>
>

NewsArchive
11-30-2000, 01:00 AM
Oops.. the DialogNetworkPrinter code is as follows:

///////////////////////////////////////////////////////////////////////////////
//
// Function: DialogNetworkPrinter
//
// Purpose: Gets the path to the network printer and returns a string
// location
//
//
///////////////////////////////////////////////////////////////////////////////
function DialogNetworkPrinter( svPrinterPath )

LONG lpIDList;
STRING sBuffer[MAX_PATH];
STRING szTitle;
BrowseInfo tBrowseInfo;


begin
szTitle = "";
tBrowseInfo.hWndOwner = GetWindowHandle ( HWND_INSTALL );
tBrowseInfo.lpszTitle = &szTitle;
tBrowseInfo.ulFlags = BIF_BROWSEFORPRINTER;

if ( UseDLL ( FILENAME_SHELL ) < 0 ) then
MessageBox(ERROR_SHELL_NOLOAD, SEVERE );
endif;

lpIDList = SHBrowseForFolder(&tBrowseInfo);
if (lpIDList) then
SHGetPathFromIDList(lpIDList, sBuffer);

svPrinterPath = sBuffer; // string path
endif;
UnUseDLL(FILENAME_SHELL);



end;

On Thu, 30 Nov 2000 18:13:48 GMT, nabours1@earthlink.net (Benny
Nabours) wrote:

>Well, I tried the 6.2 version, but still get the same problem..
>again, only on Windows ME.. here is the code I am using to try to
>browse the network for a network printer:
>
>function DialogShowAskPath()
>
> STRING szTitle, szMsg;
> NUMBER nCreateDialog, nId, nResult;
> BOOL bDone;
>
>begin
> nCreateDialog = EzDefineDialog(CUST_DIAG_PORT, ISUSER,"",30001);
>
> //Display dialog
> bDone = FALSE;
> while (bDone=FALSE)
> nId = WaitOnDialog(CUST_DIAG_PORT);
> switch(nId)
> case DLG_INIT:
>
> case SD_PBUT_CONTINUE:
> bDone = TRUE;
> case SD_PBUT_BACK:
> bDone = TRUE;
> nResult = SD_PBUT_BACK;
> case SD_PBUT_EXITSETUP:
> Do(EXIT);
> case BROWSEBUTTON:
> DialogNetworkPrinter( svPrinterPath );
> CtrlSetText(CUST_DIAG_PORT, 30130,
>svPrinterPath);
> case DLG_ERR:
> MessageBox(ERROR_DIALOG, SEVERE);
> bDone = TRUE;
> endswitch;
>
> endwhile;
> CtrlGetText(CUST_DIAG_PORT, 30130, svPrinterPath);
> EndDialog(CUST_DIAG_PORT);
> ReleaseDialog(CUST_DIAG_PORT);
> return nResult;
>end;
>
>This works fine on all other versions of Windows, but on ME it simply
>browses to the Desktop, and does not allow me to see the Network or
>Local system drives...
>
>On Wed, 29 Nov 2000 19:30:49 -0600, "Kevin-InstallShield"
><supportnews@installshield.com> wrote:
>
>>Hello Benny,
>>
>>Windows ME came out after IS Pro 6.1x. Therefore InstallShield begins
>>Windows ME support with 6.22. To prove that this will work for you you can
>>download the eval version of 6.22 and try it. To get the eval version visit
>>our web site, www.installshield.com and you can download it from our
>>Products tab.
>>
>>Have a good day Benny.
>>
>>-Kevin
>>InstallShield Tech Support
>>
>>
>>"Benny Nabours" <nabours1@earthlink.net> wrote in message
>>news:3a25587f.592809915@news.installshield.com...
>>> Hi everyone.
>>>
>>> I have an interesting predicament...
>>>
>>> I have a Browse Network dialog in my installation, when the install is
>>> running, the Browse for Network Printer dialog comes up. This works
>>> fine on all versions of Windows EXCEPT Windows ME. When I run the
>>> install on all other version, if you click browse, it brings up the
>>> following:
>>>
>>> Desktop -
>>> My Computer-
>>> <floppy drive>
>>> <hard drive>
>>> <Network Neighborhood>
>>> <Mapped drives, etc...>
>>>
>>> When I run this command on Windows ME , it brings up the Desktop, with
>>> all desktop shortcuts only, no access to My Computer, no access to
>>> Network Neghborhood, etc... Any idea why this might be happening?
>>> Is there a bug with IS 6.10 and Windows ME? Would upgrading to 6.22
>>> fix this problem?
>>>
>>> If I can supply you with more information, I would be happy to..
>>>
>>> Thank you in advance for ANY assistance or advice you may be able to
>>> offer.
>>>
>>> -Benny
>>
>>
>

NewsArchive
12-01-2000, 01:00 AM
Have you tried the built in function SelectDirEx with
BIF_BROWSEFORPRINTER?
In your code I don't see where you specify the sBuffer for
tBrowseInfo.

--
Stefan Krueger - Independent Setup Consultant
<<reply-to address is invalid to avoid spam>>

Visit InstallSite at http://www.installsite.org to download
free code samples, tips, tools and more...
For information about individual support and consulting services
please send a blank mail to the autoresponder at info@installsite.org

Stefan Krueger and the InstallSite.org web site are not affiliated
with InstallShield Software Corporation.

"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
news:3a26a896.72637006@news.installshield.com...
> Oops.. the DialogNetworkPrinter code is as follows:
>
>
//////////////////////////////////////////////////////////////////////
/////////
> //
> // Function: DialogNetworkPrinter
> //
> // Purpose: Gets the path to the network printer and returns a
string
> // location
> //
> //
>
//////////////////////////////////////////////////////////////////////
/////////
> function DialogNetworkPrinter( svPrinterPath )
>
> LONG lpIDList;
> STRING sBuffer[MAX_PATH];
> STRING szTitle;
> BrowseInfo tBrowseInfo;
>
>
> begin
> szTitle = "";
> tBrowseInfo.hWndOwner = GetWindowHandle ( HWND_INSTALL );
> tBrowseInfo.lpszTitle = &szTitle;
> tBrowseInfo.ulFlags = BIF_BROWSEFORPRINTER;
>
> if ( UseDLL ( FILENAME_SHELL ) < 0 ) then
> MessageBox(ERROR_SHELL_NOLOAD, SEVERE );
> endif;
>
> lpIDList = SHBrowseForFolder(&tBrowseInfo);
> if (lpIDList) then
> SHGetPathFromIDList(lpIDList, sBuffer);
>
> svPrinterPath = sBuffer; // string path
> endif;
> UnUseDLL(FILENAME_SHELL);
>
>
>
> end;
>
> On Thu, 30 Nov 2000 18:13:48 GMT, nabours1@earthlink.net (Benny
> Nabours) wrote:
>
> >Well, I tried the 6.2 version, but still get the same problem..
> >again, only on Windows ME.. here is the code I am using to try to
> >browse the network for a network printer:
> >
> >function DialogShowAskPath()
> >
> > STRING szTitle, szMsg;
> > NUMBER nCreateDialog, nId, nResult;
> > BOOL bDone;
> >
> >begin
> > nCreateDialog = EzDefineDialog(CUST_DIAG_PORT,
ISUSER,"",30001);
> >
> > //Display dialog
> > bDone = FALSE;
> > while (bDone=FALSE)
> > nId = WaitOnDialog(CUST_DIAG_PORT);
> > switch(nId)
> > case DLG_INIT:
> >
> > case SD_PBUT_CONTINUE:
> > bDone = TRUE;
> > case SD_PBUT_BACK:
> > bDone = TRUE;
> > nResult = SD_PBUT_BACK;
> > case SD_PBUT_EXITSETUP:
> > Do(EXIT);
> > case BROWSEBUTTON:
> > DialogNetworkPrinter( svPrinterPath );
> > CtrlSetText(CUST_DIAG_PORT, 30130,
> >svPrinterPath);
> > case DLG_ERR:
> > MessageBox(ERROR_DIALOG, SEVERE);
> > bDone = TRUE;
> > endswitch;
> >
> > endwhile;
> > CtrlGetText(CUST_DIAG_PORT, 30130, svPrinterPath);
> > EndDialog(CUST_DIAG_PORT);
> > ReleaseDialog(CUST_DIAG_PORT);
> > return nResult;
> >end;
> >
> >This works fine on all other versions of Windows, but on ME it
simply
> >browses to the Desktop, and does not allow me to see the Network or
> >Local system drives...
> >
> >On Wed, 29 Nov 2000 19:30:49 -0600, "Kevin-InstallShield"
> ><supportnews@installshield.com> wrote:
> >
> >>Hello Benny,
> >>
> >>Windows ME came out after IS Pro 6.1x. Therefore InstallShield
begins
> >>Windows ME support with 6.22. To prove that this will work for
you you can
> >>download the eval version of 6.22 and try it. To get the eval
version visit
> >>our web site, www.installshield.com and you can download it from
our
> >>Products tab.
> >>
> >>Have a good day Benny.
> >>
> >>-Kevin
> >>InstallShield Tech Support
> >>
> >>
> >>"Benny Nabours" <nabours1@earthlink.net> wrote in message
> >>news:3a25587f.592809915@news.installshield.com...
> >>> Hi everyone.
> >>>
> >>> I have an interesting predicament...
> >>>
> >>> I have a Browse Network dialog in my installation, when the
install is
> >>> running, the Browse for Network Printer dialog comes up. This
works
> >>> fine on all versions of Windows EXCEPT Windows ME. When I run
the
> >>> install on all other version, if you click browse, it brings up
the
> >>> following:
> >>>
> >>> Desktop -
> >>> My Computer-
> >>> <floppy drive>
> >>> <hard drive>
> >>> <Network Neighborhood>
> >>> <Mapped drives, etc...>
> >>>
> >>> When I run this command on Windows ME , it brings up the
Desktop, with
> >>> all desktop shortcuts only, no access to My Computer, no access
to
> >>> Network Neghborhood, etc... Any idea why this might be
happening?
> >>> Is there a bug with IS 6.10 and Windows ME? Would upgrading to
6.22
> >>> fix this problem?
> >>>
> >>> If I can supply you with more information, I would be happy to..
> >>>
> >>> Thank you in advance for ANY assistance or advice you may be
able to
> >>> offer.
> >>>
> >>> -Benny
> >>
> >>
> >
>

NewsArchive
12-01-2000, 01:00 AM
Well, I use the SelectDirEx function, and it seems to be ok, but it
does not return the Network Printer location as a fully qualified
value.

IE , I browse network, select Printer on Computer1 named Printer, I
would want it to return
"\\Computer1\Printer" but it just returns "Printer"

Any idea how to force it to return the fully qualified name?

Here is what I am doing:

///////////////////////////////////////////////////////////////////////////////
//
// Function: DialogNetworkPrinter
//
// Purpose: Gets the path to the network printer and returns a string
location
//
//
///////////////////////////////////////////////////////////////////////////////
function DialogNetworkPrinter( svPrinterPath )
LONG lpIDList;
STRING szTitle, szMsg, nFlags, svDir;
STRING szEditBoxStaticText, szTreeControlStaticText;
BOOL bCreate, bFolderExists;
NUMBER nResult;

begin
repeat
szTitle="Select Printer";
szMsg= "";
nFlags= "BIF_BROWSEFORPRINTER";


nResult = (SelectDirEx (szTitle, szMsg, szEditBoxStaticText,
szTreeControlStaticText, BIF_BROWSEFORPRINTER, svDir) > 0);

if nResult = 0 then
bFolderExists = ExistsDir (nFlags);
if bFolderExists = NOTEXISTS then
szMsg = "%s does not exist.\nPlease choose an existing
Printer.";
SprintfBox (WARNING, szTitle, szMsg, nFlags);
endif;
endif;

until (nResult = CANCEL) || (bFolderExists = EXISTS);

svPrinterPath = svDir;

end;

On Fri, 1 Dec 2000 10:57:41 +0100, "Stefan Krueger" <@> wrote:

>Have you tried the built in function SelectDirEx with
>BIF_BROWSEFORPRINTER?
>In your code I don't see where you specify the sBuffer for
>tBrowseInfo.
>
>--
>Stefan Krueger - Independent Setup Consultant
><<reply-to address is invalid to avoid spam>>
>
>Visit InstallSite at http://www.installsite.org to download
>free code samples, tips, tools and more...
>For information about individual support and consulting services
>please send a blank mail to the autoresponder at info@installsite.org
>
>Stefan Krueger and the InstallSite.org web site are not affiliated
>with InstallShield Software Corporation.
>
>"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
>news:3a26a896.72637006@news.installshield.com...
>> Oops.. the DialogNetworkPrinter code is as follows:
>>
>>
>//////////////////////////////////////////////////////////////////////
>/////////
>> //
>> // Function: DialogNetworkPrinter
>> //
>> // Purpose: Gets the path to the network printer and returns a
>string
>> // location
>> //
>> //
>>
>//////////////////////////////////////////////////////////////////////
>/////////
>> function DialogNetworkPrinter( svPrinterPath )
>>
>> LONG lpIDList;
>> STRING sBuffer[MAX_PATH];
>> STRING szTitle;
>> BrowseInfo tBrowseInfo;
>>
>>
>> begin
>> szTitle = "";
>> tBrowseInfo.hWndOwner = GetWindowHandle ( HWND_INSTALL );
>> tBrowseInfo.lpszTitle = &szTitle;
>> tBrowseInfo.ulFlags = BIF_BROWSEFORPRINTER;
>>
>> if ( UseDLL ( FILENAME_SHELL ) < 0 ) then
>> MessageBox(ERROR_SHELL_NOLOAD, SEVERE );
>> endif;
>>
>> lpIDList = SHBrowseForFolder(&tBrowseInfo);
>> if (lpIDList) then
>> SHGetPathFromIDList(lpIDList, sBuffer);
>>
>> svPrinterPath = sBuffer; // string path
>> endif;
>> UnUseDLL(FILENAME_SHELL);
>>
>>
>>
>> end;
>>
>> On Thu, 30 Nov 2000 18:13:48 GMT, nabours1@earthlink.net (Benny
>> Nabours) wrote:
>>
>> >Well, I tried the 6.2 version, but still get the same problem..
>> >again, only on Windows ME.. here is the code I am using to try to
>> >browse the network for a network printer:
>> >
>> >function DialogShowAskPath()
>> >
>> > STRING szTitle, szMsg;
>> > NUMBER nCreateDialog, nId, nResult;
>> > BOOL bDone;
>> >
>> >begin
>> > nCreateDialog = EzDefineDialog(CUST_DIAG_PORT,
>ISUSER,"",30001);
>> >
>> > //Display dialog
>> > bDone = FALSE;
>> > while (bDone=FALSE)
>> > nId = WaitOnDialog(CUST_DIAG_PORT);
>> > switch(nId)
>> > case DLG_INIT:
>> >
>> > case SD_PBUT_CONTINUE:
>> > bDone = TRUE;
>> > case SD_PBUT_BACK:
>> > bDone = TRUE;
>> > nResult = SD_PBUT_BACK;
>> > case SD_PBUT_EXITSETUP:
>> > Do(EXIT);
>> > case BROWSEBUTTON:
>> > DialogNetworkPrinter( svPrinterPath );
>> > CtrlSetText(CUST_DIAG_PORT, 30130,
>> >svPrinterPath);
>> > case DLG_ERR:
>> > MessageBox(ERROR_DIALOG, SEVERE);
>> > bDone = TRUE;
>> > endswitch;
>> >
>> > endwhile;
>> > CtrlGetText(CUST_DIAG_PORT, 30130, svPrinterPath);
>> > EndDialog(CUST_DIAG_PORT);
>> > ReleaseDialog(CUST_DIAG_PORT);
>> > return nResult;
>> >end;
>> >
>> >This works fine on all other versions of Windows, but on ME it
>simply
>> >browses to the Desktop, and does not allow me to see the Network or
>> >Local system drives...
>> >
>> >On Wed, 29 Nov 2000 19:30:49 -0600, "Kevin-InstallShield"
>> ><supportnews@installshield.com> wrote:
>> >
>> >>Hello Benny,
>> >>
>> >>Windows ME came out after IS Pro 6.1x. Therefore InstallShield
>begins
>> >>Windows ME support with 6.22. To prove that this will work for
>you you can
>> >>download the eval version of 6.22 and try it. To get the eval
>version visit
>> >>our web site, www.installshield.com and you can download it from
>our
>> >>Products tab.
>> >>
>> >>Have a good day Benny.
>> >>
>> >>-Kevin
>> >>InstallShield Tech Support
>> >>
>> >>
>> >>"Benny Nabours" <nabours1@earthlink.net> wrote in message
>> >>news:3a25587f.592809915@news.installshield.com...
>> >>> Hi everyone.
>> >>>
>> >>> I have an interesting predicament...
>> >>>
>> >>> I have a Browse Network dialog in my installation, when the
>install is
>> >>> running, the Browse for Network Printer dialog comes up. This
>works
>> >>> fine on all versions of Windows EXCEPT Windows ME. When I run
>the
>> >>> install on all other version, if you click browse, it brings up
>the
>> >>> following:
>> >>>
>> >>> Desktop -
>> >>> My Computer-
>> >>> <floppy drive>
>> >>> <hard drive>
>> >>> <Network Neighborhood>
>> >>> <Mapped drives, etc...>
>> >>>
>> >>> When I run this command on Windows ME , it brings up the
>Desktop, with
>> >>> all desktop shortcuts only, no access to My Computer, no access
>to
>> >>> Network Neghborhood, etc... Any idea why this might be
>happening?
>> >>> Is there a bug with IS 6.10 and Windows ME? Would upgrading to
>6.22
>> >>> fix this problem?
>> >>>
>> >>> If I can supply you with more information, I would be happy to..
>> >>>
>> >>> Thank you in advance for ANY assistance or advice you may be
>able to
>> >>> offer.
>> >>>
>> >>> -Benny
>> >>
>> >>
>> >
>>
>

NewsArchive
12-01-2000, 01:00 AM
This is a known bug in the function (documented in the Bugs Bulletin
on http://www.installsite.org) that was fixed in IS 6.22. If you are
using IS 6.1x you can add the BIF_EDITBOX flag as a workaround. This
will cause the function to return the full path.

--
Stefan Krueger - Independent Setup Consultant
<<reply-to address is invalid to avoid spam>>

Visit InstallSite at http://www.installsite.org to download
free code samples, tips, tools and more...
For information about individual support and consulting services
please send a blank mail to the autoresponder at info@installsite.org

Stefan Krueger and the InstallSite.org web site are not affiliated
with InstallShield Software Corporation.


"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
news:3a27fb41.159335562@news.installshield.com...
> Well, I use the SelectDirEx function, and it seems to be ok, but it
> does not return the Network Printer location as a fully qualified
> value.
>
> IE , I browse network, select Printer on Computer1 named Printer, I
> would want it to return
> "\\Computer1\Printer" but it just returns "Printer"
>
> Any idea how to force it to return the fully qualified name?
>
> Here is what I am doing:
>
>
//////////////////////////////////////////////////////////////////////
/////////
> //
> // Function: DialogNetworkPrinter
> //
> // Purpose: Gets the path to the network printer and returns a
string
> location
> //
> //
>
//////////////////////////////////////////////////////////////////////
/////////
> function DialogNetworkPrinter( svPrinterPath )
> LONG lpIDList;
> STRING szTitle, szMsg, nFlags, svDir;
> STRING szEditBoxStaticText, szTreeControlStaticText;
> BOOL bCreate, bFolderExists;
> NUMBER nResult;
>
> begin
> repeat
> szTitle="Select Printer";
> szMsg= "";
> nFlags= "BIF_BROWSEFORPRINTER";
>
>
> nResult = (SelectDirEx (szTitle, szMsg, szEditBoxStaticText,
> szTreeControlStaticText, BIF_BROWSEFORPRINTER, svDir) > 0);
>
> if nResult = 0 then
> bFolderExists = ExistsDir (nFlags);
> if bFolderExists = NOTEXISTS then
> szMsg = "%s does not exist.\nPlease choose an existing
> Printer.";
> SprintfBox (WARNING, szTitle, szMsg, nFlags);
> endif;
> endif;
>
> until (nResult = CANCEL) || (bFolderExists = EXISTS);
>
> svPrinterPath = svDir;
>
> end;
>
> On Fri, 1 Dec 2000 10:57:41 +0100, "Stefan Krueger" <@> wrote:
>
> >Have you tried the built in function SelectDirEx with
> >BIF_BROWSEFORPRINTER?
> >In your code I don't see where you specify the sBuffer for
> >tBrowseInfo.
> >
> >--
> >Stefan Krueger - Independent Setup Consultant
> ><<reply-to address is invalid to avoid spam>>
> >
> >Visit InstallSite at http://www.installsite.org to download
> >free code samples, tips, tools and more...
> >For information about individual support and consulting services
> >please send a blank mail to the autoresponder at
info@installsite.org
> >
> >Stefan Krueger and the InstallSite.org web site are not affiliated
> >with InstallShield Software Corporation.
> >
> >"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
> >news:3a26a896.72637006@news.installshield.com...
> >> Oops.. the DialogNetworkPrinter code is as follows:
> >>
> >>
>
>/////////////////////////////////////////////////////////////////////
/
> >/////////
> >> //
> >> // Function: DialogNetworkPrinter
> >> //
> >> // Purpose: Gets the path to the network printer and returns a
> >string
> >> // location
> >> //
> >> //
> >>
>
>/////////////////////////////////////////////////////////////////////
/
> >/////////
> >> function DialogNetworkPrinter( svPrinterPath )
> >>
> >> LONG lpIDList;
> >> STRING sBuffer[MAX_PATH];
> >> STRING szTitle;
> >> BrowseInfo tBrowseInfo;
> >>
> >>
> >> begin
> >> szTitle = "";
> >> tBrowseInfo.hWndOwner = GetWindowHandle ( HWND_INSTALL );
> >> tBrowseInfo.lpszTitle = &szTitle;
> >> tBrowseInfo.ulFlags = BIF_BROWSEFORPRINTER;
> >>
> >> if ( UseDLL ( FILENAME_SHELL ) < 0 ) then
> >> MessageBox(ERROR_SHELL_NOLOAD, SEVERE );
> >> endif;
> >>
> >> lpIDList = SHBrowseForFolder(&tBrowseInfo);
> >> if (lpIDList) then
> >> SHGetPathFromIDList(lpIDList, sBuffer);
> >>
> >> svPrinterPath = sBuffer; // string path
> >> endif;
> >> UnUseDLL(FILENAME_SHELL);
> >>
> >>
> >>
> >> end;
> >>
> >> On Thu, 30 Nov 2000 18:13:48 GMT, nabours1@earthlink.net (Benny
> >> Nabours) wrote:
> >>
> >> >Well, I tried the 6.2 version, but still get the same problem..
> >> >again, only on Windows ME.. here is the code I am using to try
to
> >> >browse the network for a network printer:
> >> >
> >> >function DialogShowAskPath()
> >> >
> >> > STRING szTitle, szMsg;
> >> > NUMBER nCreateDialog, nId, nResult;
> >> > BOOL bDone;
> >> >
> >> >begin
> >> > nCreateDialog = EzDefineDialog(CUST_DIAG_PORT,
> >ISUSER,"",30001);
> >> >
> >> > //Display dialog
> >> > bDone = FALSE;
> >> > while (bDone=FALSE)
> >> > nId = WaitOnDialog(CUST_DIAG_PORT);
> >> > switch(nId)
> >> > case DLG_INIT:
> >> >
> >> > case SD_PBUT_CONTINUE:
> >> > bDone = TRUE;
> >> > case SD_PBUT_BACK:
> >> > bDone = TRUE;
> >> > nResult = SD_PBUT_BACK;
> >> > case SD_PBUT_EXITSETUP:
> >> > Do(EXIT);
> >> > case BROWSEBUTTON:
> >> > DialogNetworkPrinter( svPrinterPath );
> >> > CtrlSetText(CUST_DIAG_PORT, 30130,
> >> >svPrinterPath);
> >> > case DLG_ERR:
> >> > MessageBox(ERROR_DIALOG, SEVERE);
> >> > bDone = TRUE;
> >> > endswitch;
> >> >
> >> > endwhile;
> >> > CtrlGetText(CUST_DIAG_PORT, 30130, svPrinterPath);
> >> > EndDialog(CUST_DIAG_PORT);
> >> > ReleaseDialog(CUST_DIAG_PORT);
> >> > return nResult;
> >> >end;
> >> >
> >> >This works fine on all other versions of Windows, but on ME it
> >simply
> >> >browses to the Desktop, and does not allow me to see the Network
or
> >> >Local system drives...
> >> >
> >> >On Wed, 29 Nov 2000 19:30:49 -0600, "Kevin-InstallShield"
> >> ><supportnews@installshield.com> wrote:
> >> >
> >> >>Hello Benny,
> >> >>
> >> >>Windows ME came out after IS Pro 6.1x. Therefore InstallShield
> >begins
> >> >>Windows ME support with 6.22. To prove that this will work for
> >you you can
> >> >>download the eval version of 6.22 and try it. To get the eval
> >version visit
> >> >>our web site, www.installshield.com and you can download it
from
> >our
> >> >>Products tab.
> >> >>
> >> >>Have a good day Benny.
> >> >>
> >> >>-Kevin
> >> >>InstallShield Tech Support
> >> >>
> >> >>
> >> >>"Benny Nabours" <nabours1@earthlink.net> wrote in message
> >> >>news:3a25587f.592809915@news.installshield.com...
> >> >>> Hi everyone.
> >> >>>
> >> >>> I have an interesting predicament...
> >> >>>
> >> >>> I have a Browse Network dialog in my installation, when the
> >install is
> >> >>> running, the Browse for Network Printer dialog comes up.
This
> >works
> >> >>> fine on all versions of Windows EXCEPT Windows ME. When I
run
> >the
> >> >>> install on all other version, if you click browse, it brings
up
> >the
> >> >>> following:
> >> >>>
> >> >>> Desktop -
> >> >>> My Computer-
> >> >>> <floppy drive>
> >> >>> <hard drive>
> >> >>> <Network Neighborhood>
> >> >>> <Mapped drives, etc...>
> >> >>>
> >> >>> When I run this command on Windows ME , it brings up the
> >Desktop, with
> >> >>> all desktop shortcuts only, no access to My Computer, no
access
> >to
> >> >>> Network Neghborhood, etc... Any idea why this might be
> >happening?
> >> >>> Is there a bug with IS 6.10 and Windows ME? Would upgrading
to
> >6.22
> >> >>> fix this problem?
> >> >>>
> >> >>> If I can supply you with more information, I would be happy
to..
> >> >>>
> >> >>> Thank you in advance for ANY assistance or advice you may be
> >able to
> >> >>> offer.
> >> >>>
> >> >>> -Benny
> >> >>
> >> >>
> >> >
> >>
> >
>

NewsArchive
12-08-2000, 01:00 AM
Well, I went and got InstallShield 6.22, and guess what, it's STILL a
bug. This is getting quite frustrating. I feel like I'm sooo close,
yet so far away.

Is there another alternative to qualify the return value?

On Fri, 1 Dec 2000 22:30:18 +0100, "Stefan Krueger" <@> wrote:

>This is a known bug in the function (documented in the Bugs Bulletin
>on http://www.installsite.org) that was fixed in IS 6.22. If you are
>using IS 6.1x you can add the BIF_EDITBOX flag as a workaround. This
>will cause the function to return the full path.
>
>--
>Stefan Krueger - Independent Setup Consultant
><<reply-to address is invalid to avoid spam>>
>
>Visit InstallSite at http://www.installsite.org to download
>free code samples, tips, tools and more...
>For information about individual support and consulting services
>please send a blank mail to the autoresponder at info@installsite.org
>
>Stefan Krueger and the InstallSite.org web site are not affiliated
>with InstallShield Software Corporation.
>
>
>"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
>news:3a27fb41.159335562@news.installshield.com...
>> Well, I use the SelectDirEx function, and it seems to be ok, but it
>> does not return the Network Printer location as a fully qualified
>> value.
>>
>> IE , I browse network, select Printer on Computer1 named Printer, I
>> would want it to return
>> "\\Computer1\Printer" but it just returns "Printer"
>>
>> Any idea how to force it to return the fully qualified name?
>>
>> Here is what I am doing:
>>
>>
>//////////////////////////////////////////////////////////////////////
>/////////
>> //
>> // Function: DialogNetworkPrinter
>> //
>> // Purpose: Gets the path to the network printer and returns a
>string
>> location
>> //
>> //
>>
>//////////////////////////////////////////////////////////////////////
>/////////
>> function DialogNetworkPrinter( svPrinterPath )
>> LONG lpIDList;
>> STRING szTitle, szMsg, nFlags, svDir;
>> STRING szEditBoxStaticText, szTreeControlStaticText;
>> BOOL bCreate, bFolderExists;
>> NUMBER nResult;
>>
>> begin
>> repeat
>> szTitle="Select Printer";
>> szMsg= "";
>> nFlags= "BIF_BROWSEFORPRINTER";
>>
>>
>> nResult = (SelectDirEx (szTitle, szMsg, szEditBoxStaticText,
>> szTreeControlStaticText, BIF_BROWSEFORPRINTER, svDir) > 0);
>>
>> if nResult = 0 then
>> bFolderExists = ExistsDir (nFlags);
>> if bFolderExists = NOTEXISTS then
>> szMsg = "%s does not exist.\nPlease choose an existing
>> Printer.";
>> SprintfBox (WARNING, szTitle, szMsg, nFlags);
>> endif;
>> endif;
>>
>> until (nResult = CANCEL) || (bFolderExists = EXISTS);
>>
>> svPrinterPath = svDir;
>>
>> end;
>>
>> On Fri, 1 Dec 2000 10:57:41 +0100, "Stefan Krueger" <@> wrote:
>>
>> >Have you tried the built in function SelectDirEx with
>> >BIF_BROWSEFORPRINTER?
>> >In your code I don't see where you specify the sBuffer for
>> >tBrowseInfo.
>> >
>> >--
>> >Stefan Krueger - Independent Setup Consultant
>> ><<reply-to address is invalid to avoid spam>>
>> >
>> >Visit InstallSite at http://www.installsite.org to download
>> >free code samples, tips, tools and more...
>> >For information about individual support and consulting services
>> >please send a blank mail to the autoresponder at
>info@installsite.org
>> >
>> >Stefan Krueger and the InstallSite.org web site are not affiliated
>> >with InstallShield Software Corporation.
>> >
>> >"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
>> >news:3a26a896.72637006@news.installshield.com...
>> >> Oops.. the DialogNetworkPrinter code is as follows:
>> >>
>> >>
>>
>>/////////////////////////////////////////////////////////////////////
>/
>> >/////////
>> >> //
>> >> // Function: DialogNetworkPrinter
>> >> //
>> >> // Purpose: Gets the path to the network printer and returns a
>> >string
>> >> // location
>> >> //
>> >> //
>> >>
>>
>>/////////////////////////////////////////////////////////////////////
>/
>> >/////////
>> >> function DialogNetworkPrinter( svPrinterPath )
>> >>
>> >> LONG lpIDList;
>> >> STRING sBuffer[MAX_PATH];
>> >> STRING szTitle;
>> >> BrowseInfo tBrowseInfo;
>> >>
>> >>
>> >> begin
>> >> szTitle = "";
>> >> tBrowseInfo.hWndOwner = GetWindowHandle ( HWND_INSTALL );
>> >> tBrowseInfo.lpszTitle = &szTitle;
>> >> tBrowseInfo.ulFlags = BIF_BROWSEFORPRINTER;
>> >>
>> >> if ( UseDLL ( FILENAME_SHELL ) < 0 ) then
>> >> MessageBox(ERROR_SHELL_NOLOAD, SEVERE );
>> >> endif;
>> >>
>> >> lpIDList = SHBrowseForFolder(&tBrowseInfo);
>> >> if (lpIDList) then
>> >> SHGetPathFromIDList(lpIDList, sBuffer);
>> >>
>> >> svPrinterPath = sBuffer; // string path
>> >> endif;
>> >> UnUseDLL(FILENAME_SHELL);
>> >>
>> >>
>> >>
>> >> end;
>> >>
>> >> On Thu, 30 Nov 2000 18:13:48 GMT, nabours1@earthlink.net (Benny
>> >> Nabours) wrote:
>> >>
>> >> >Well, I tried the 6.2 version, but still get the same problem..
>> >> >again, only on Windows ME.. here is the code I am using to try
>to
>> >> >browse the network for a network printer:
>> >> >
>> >> >function DialogShowAskPath()
>> >> >
>> >> > STRING szTitle, szMsg;
>> >> > NUMBER nCreateDialog, nId, nResult;
>> >> > BOOL bDone;
>> >> >
>> >> >begin
>> >> > nCreateDialog = EzDefineDialog(CUST_DIAG_PORT,
>> >ISUSER,"",30001);
>> >> >
>> >> > //Display dialog
>> >> > bDone = FALSE;
>> >> > while (bDone=FALSE)
>> >> > nId = WaitOnDialog(CUST_DIAG_PORT);
>> >> > switch(nId)
>> >> > case DLG_INIT:
>> >> >
>> >> > case SD_PBUT_CONTINUE:
>> >> > bDone = TRUE;
>> >> > case SD_PBUT_BACK:
>> >> > bDone = TRUE;
>> >> > nResult = SD_PBUT_BACK;
>> >> > case SD_PBUT_EXITSETUP:
>> >> > Do(EXIT);
>> >> > case BROWSEBUTTON:
>> >> > DialogNetworkPrinter( svPrinterPath );
>> >> > CtrlSetText(CUST_DIAG_PORT, 30130,
>> >> >svPrinterPath);
>> >> > case DLG_ERR:
>> >> > MessageBox(ERROR_DIALOG, SEVERE);
>> >> > bDone = TRUE;
>> >> > endswitch;
>> >> >
>> >> > endwhile;
>> >> > CtrlGetText(CUST_DIAG_PORT, 30130, svPrinterPath);
>> >> > EndDialog(CUST_DIAG_PORT);
>> >> > ReleaseDialog(CUST_DIAG_PORT);
>> >> > return nResult;
>> >> >end;
>> >> >
>> >> >This works fine on all other versions of Windows, but on ME it
>> >simply
>> >> >browses to the Desktop, and does not allow me to see the Network
>or
>> >> >Local system drives...
>> >> >
>> >> >On Wed, 29 Nov 2000 19:30:49 -0600, "Kevin-InstallShield"
>> >> ><supportnews@installshield.com> wrote:
>> >> >
>> >> >>Hello Benny,
>> >> >>
>> >> >>Windows ME came out after IS Pro 6.1x. Therefore InstallShield
>> >begins
>> >> >>Windows ME support with 6.22. To prove that this will work for
>> >you you can
>> >> >>download the eval version of 6.22 and try it. To get the eval
>> >version visit
>> >> >>our web site, www.installshield.com and you can download it
>from
>> >our
>> >> >>Products tab.
>> >> >>
>> >> >>Have a good day Benny.
>> >> >>
>> >> >>-Kevin
>> >> >>InstallShield Tech Support
>> >> >>
>> >> >>
>> >> >>"Benny Nabours" <nabours1@earthlink.net> wrote in message
>> >> >>news:3a25587f.592809915@news.installshield.com...
>> >> >>> Hi everyone.
>> >> >>>
>> >> >>> I have an interesting predicament...
>> >> >>>
>> >> >>> I have a Browse Network dialog in my installation, when the
>> >install is
>> >> >>> running, the Browse for Network Printer dialog comes up.
>This
>> >works
>> >> >>> fine on all versions of Windows EXCEPT Windows ME. When I
>run
>> >the
>> >> >>> install on all other version, if you click browse, it brings
>up
>> >the
>> >> >>> following:
>> >> >>>
>> >> >>> Desktop -
>> >> >>> My Computer-
>> >> >>> <floppy drive>
>> >> >>> <hard drive>
>> >> >>> <Network Neighborhood>
>> >> >>> <Mapped drives, etc...>
>> >> >>>
>> >> >>> When I run this command on Windows ME , it brings up the
>> >Desktop, with
>> >> >>> all desktop shortcuts only, no access to My Computer, no
>access
>> >to
>> >> >>> Network Neghborhood, etc... Any idea why this might be
>> >happening?
>> >> >>> Is there a bug with IS 6.10 and Windows ME? Would upgrading
>to
>> >6.22
>> >> >>> fix this problem?
>> >> >>>
>> >> >>> If I can supply you with more information, I would be happy
>to..
>> >> >>>
>> >> >>> Thank you in advance for ANY assistance or advice you may be
>> >able to
>> >> >>> offer.
>> >> >>>
>> >> >>> -Benny
>> >> >>
>> >> >>
>> >> >
>> >>
>> >
>>
>

NewsArchive
12-08-2000, 01:00 AM
True, it doesn't work for printer (I hadn't tested for printers), but
for file system paths the bug is fixed in 6.22.
Maybe calling the WinAPI directly would be the only way then. If you
can't get it to work: have you tried to place the API call in a DLL?

I've also noticed some strange things in your code below, like the
following:

nFlags= "BIF_BROWSEFORPRINTER";
// nFlags should be a NUMBER, and BIF_BROWSEFORPRINTER should not have
quotes. But you're not using nFlags in the function call.

bFolderExists = ExistsDir (nFlags);
// I guess you meant: ExistsDir(svDir); however I doubt that this will
work for printers

--
Stefan Krueger - Independent Setup Consultant
<<reply-to address is invalid to avoid spam>>

Visit InstallSite at http://www.installsite.org to download
free code samples, tips, tools and more...
For information about individual support and consulting services
please send a blank mail to the autoresponder at info@installsite.org

Stefan Krueger and the InstallSite.org web site are not affiliated
with InstallShield Software Corporation.

"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
news:3a302cb1.92567845@news.installshield.com...
> Well, I went and got InstallShield 6.22, and guess what, it's STILL
a
> bug. This is getting quite frustrating. I feel like I'm sooo
close,
> yet so far away.
>
> Is there another alternative to qualify the return value?
>
> On Fri, 1 Dec 2000 22:30:18 +0100, "Stefan Krueger" <@> wrote:
>
> >This is a known bug in the function (documented in the Bugs
Bulletin
> >on http://www.installsite.org) that was fixed in IS 6.22. If you
are
> >using IS 6.1x you can add the BIF_EDITBOX flag as a workaround.
This
> >will cause the function to return the full path.
> >
> >--
> >Stefan Krueger - Independent Setup Consultant
> ><<reply-to address is invalid to avoid spam>>
> >
> >Visit InstallSite at http://www.installsite.org to download
> >free code samples, tips, tools and more...
> >For information about individual support and consulting services
> >please send a blank mail to the autoresponder at
info@installsite.org
> >
> >Stefan Krueger and the InstallSite.org web site are not affiliated
> >with InstallShield Software Corporation.
> >
> >
> >"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
> >news:3a27fb41.159335562@news.installshield.com...
> >> Well, I use the SelectDirEx function, and it seems to be ok, but
it
> >> does not return the Network Printer location as a fully qualified
> >> value.
> >>
> >> IE , I browse network, select Printer on Computer1 named Printer,
I
> >> would want it to return
> >> "\\Computer1\Printer" but it just returns "Printer"
> >>
> >> Any idea how to force it to return the fully qualified name?
> >>
> >> Here is what I am doing:
> >>
> >>
>
>/////////////////////////////////////////////////////////////////////
/
> >/////////
> >> //
> >> // Function: DialogNetworkPrinter
> >> //
> >> // Purpose: Gets the path to the network printer and returns a
> >string
> >> location
> >> //
> >> //
> >>
>
>/////////////////////////////////////////////////////////////////////
/
> >/////////
> >> function DialogNetworkPrinter( svPrinterPath )
> >> LONG lpIDList;
> >> STRING szTitle, szMsg, nFlags, svDir;
> >> STRING szEditBoxStaticText, szTreeControlStaticText;
> >> BOOL bCreate, bFolderExists;
> >> NUMBER nResult;
> >>
> >> begin
> >> repeat
> >> szTitle="Select Printer";
> >> szMsg= "";
> >> nFlags= "BIF_BROWSEFORPRINTER";
> >>
> >>
> >> nResult = (SelectDirEx (szTitle, szMsg,
szEditBoxStaticText,
> >> szTreeControlStaticText, BIF_BROWSEFORPRINTER, svDir) > 0);
> >>
> >> if nResult = 0 then
> >> bFolderExists = ExistsDir (nFlags);
> >> if bFolderExists = NOTEXISTS then
> >> szMsg = "%s does not exist.\nPlease choose an existing
> >> Printer.";
> >> SprintfBox (WARNING, szTitle, szMsg, nFlags);
> >> endif;
> >> endif;
> >>
> >> until (nResult = CANCEL) || (bFolderExists = EXISTS);
> >>
> >> svPrinterPath = svDir;
> >>
> >> end;
> >>
> >> On Fri, 1 Dec 2000 10:57:41 +0100, "Stefan Krueger" <@> wrote:
> >>
> >> >Have you tried the built in function SelectDirEx with
> >> >BIF_BROWSEFORPRINTER?
> >> >In your code I don't see where you specify the sBuffer for
> >> >tBrowseInfo.
> >> >
> >> >--
> >> >Stefan Krueger - Independent Setup Consultant
> >> ><<reply-to address is invalid to avoid spam>>
> >> >
> >> >Visit InstallSite at http://www.installsite.org to download
> >> >free code samples, tips, tools and more...
> >> >For information about individual support and consulting services
> >> >please send a blank mail to the autoresponder at
> >info@installsite.org
> >> >
> >> >Stefan Krueger and the InstallSite.org web site are not
affiliated
> >> >with InstallShield Software Corporation.
> >> >
> >> >"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
> >> >news:3a26a896.72637006@news.installshield.com...
> >> >> Oops.. the DialogNetworkPrinter code is as follows:
> >> >>
> >> >>
> >>
>
>>////////////////////////////////////////////////////////////////////
/
> >/
> >> >/////////
> >> >> //
> >> >> // Function: DialogNetworkPrinter
> >> >> //
> >> >> // Purpose: Gets the path to the network printer and returns
a
> >> >string
> >> >> // location
> >> >> //
> >> >> //
> >> >>
> >>
>
>>////////////////////////////////////////////////////////////////////
/
> >/
> >> >/////////
> >> >> function DialogNetworkPrinter( svPrinterPath )
> >> >>
> >> >> LONG lpIDList;
> >> >> STRING sBuffer[MAX_PATH];
> >> >> STRING szTitle;
> >> >> BrowseInfo tBrowseInfo;
> >> >>
> >> >>
> >> >> begin
> >> >> szTitle = "";
> >> >> tBrowseInfo.hWndOwner = GetWindowHandle ( HWND_INSTALL );
> >> >> tBrowseInfo.lpszTitle = &szTitle;
> >> >> tBrowseInfo.ulFlags = BIF_BROWSEFORPRINTER;
> >> >>
> >> >> if ( UseDLL ( FILENAME_SHELL ) < 0 ) then
> >> >> MessageBox(ERROR_SHELL_NOLOAD, SEVERE );
> >> >> endif;
> >> >>
> >> >> lpIDList = SHBrowseForFolder(&tBrowseInfo);
> >> >> if (lpIDList) then
> >> >> SHGetPathFromIDList(lpIDList, sBuffer);
> >> >>
> >> >> svPrinterPath = sBuffer; // string path
> >> >> endif;
> >> >> UnUseDLL(FILENAME_SHELL);
> >> >>
> >> >>
> >> >>
> >> >> end;
> >> >>
> >> >> On Thu, 30 Nov 2000 18:13:48 GMT, nabours1@earthlink.net
(Benny
> >> >> Nabours) wrote:
> >> >>
> >> >> >Well, I tried the 6.2 version, but still get the same
problem..
> >> >> >again, only on Windows ME.. here is the code I am using to
try
> >to
> >> >> >browse the network for a network printer:
> >> >> >
> >> >> >function DialogShowAskPath()
> >> >> >
> >> >> > STRING szTitle, szMsg;
> >> >> > NUMBER nCreateDialog, nId, nResult;
> >> >> > BOOL bDone;
> >> >> >
> >> >> >begin
> >> >> > nCreateDialog = EzDefineDialog(CUST_DIAG_PORT,
> >> >ISUSER,"",30001);
> >> >> >
> >> >> > //Display dialog
> >> >> > bDone = FALSE;
> >> >> > while (bDone=FALSE)
> >> >> > nId = WaitOnDialog(CUST_DIAG_PORT);
> >> >> > switch(nId)
> >> >> > case DLG_INIT:
> >> >> >
> >> >> > case SD_PBUT_CONTINUE:
> >> >> > bDone = TRUE;
> >> >> > case SD_PBUT_BACK:
> >> >> > bDone = TRUE;
> >> >> > nResult = SD_PBUT_BACK;
> >> >> > case SD_PBUT_EXITSETUP:
> >> >> > Do(EXIT);
> >> >> > case BROWSEBUTTON:
> >> >> > DialogNetworkPrinter( svPrinterPath );
> >> >> > CtrlSetText(CUST_DIAG_PORT, 30130,
> >> >> >svPrinterPath);
> >> >> > case DLG_ERR:
> >> >> > MessageBox(ERROR_DIALOG, SEVERE);
> >> >> > bDone = TRUE;
> >> >> > endswitch;
> >> >> >
> >> >> > endwhile;
> >> >> > CtrlGetText(CUST_DIAG_PORT, 30130, svPrinterPath);
> >> >> > EndDialog(CUST_DIAG_PORT);
> >> >> > ReleaseDialog(CUST_DIAG_PORT);
> >> >> > return nResult;
> >> >> >end;
> >> >> >
> >> >> >This works fine on all other versions of Windows, but on ME
it
> >> >simply
> >> >> >browses to the Desktop, and does not allow me to see the
Network
> >or
> >> >> >Local system drives...
> >> >> >
> >> >> >On Wed, 29 Nov 2000 19:30:49 -0600, "Kevin-InstallShield"
> >> >> ><supportnews@installshield.com> wrote:
> >> >> >
> >> >> >>Hello Benny,
> >> >> >>
> >> >> >>Windows ME came out after IS Pro 6.1x. Therefore
InstallShield
> >> >begins
> >> >> >>Windows ME support with 6.22. To prove that this will work
for
> >> >you you can
> >> >> >>download the eval version of 6.22 and try it. To get the
eval
> >> >version visit
> >> >> >>our web site, www.installshield.com and you can download it
> >from
> >> >our
> >> >> >>Products tab.
> >> >> >>
> >> >> >>Have a good day Benny.
> >> >> >>
> >> >> >>-Kevin
> >> >> >>InstallShield Tech Support
> >> >> >>
> >> >> >>
> >> >> >>"Benny Nabours" <nabours1@earthlink.net> wrote in message
> >> >> >>news:3a25587f.592809915@news.installshield.com...
> >> >> >>> Hi everyone.
> >> >> >>>
> >> >> >>> I have an interesting predicament...
> >> >> >>>
> >> >> >>> I have a Browse Network dialog in my installation, when
the
> >> >install is
> >> >> >>> running, the Browse for Network Printer dialog comes up.
> >This
> >> >works
> >> >> >>> fine on all versions of Windows EXCEPT Windows ME. When I
> >run
> >> >the
> >> >> >>> install on all other version, if you click browse, it
brings
> >up
> >> >the
> >> >> >>> following:
> >> >> >>>
> >> >> >>> Desktop -
> >> >> >>> My Computer-
> >> >> >>> <floppy drive>
> >> >> >>> <hard drive>
> >> >> >>> <Network Neighborhood>
> >> >> >>> <Mapped drives, etc...>
> >> >> >>>
> >> >> >>> When I run this command on Windows ME , it brings up the
> >> >Desktop, with
> >> >> >>> all desktop shortcuts only, no access to My Computer, no
> >access
> >> >to
> >> >> >>> Network Neghborhood, etc... Any idea why this might be
> >> >happening?
> >> >> >>> Is there a bug with IS 6.10 and Windows ME? Would
upgrading
> >to
> >> >6.22
> >> >> >>> fix this problem?
> >> >> >>>
> >> >> >>> If I can supply you with more information, I would be
happy
> >to..
> >> >> >>>
> >> >> >>> Thank you in advance for ANY assistance or advice you may
be
> >> >able to
> >> >> >>> offer.
> >> >> >>>
> >> >> >>> -Benny
> >> >> >>
> >> >> >>
> >> >> >
> >> >>
> >> >
> >>
> >
>

NewsArchive
12-11-2000, 01:00 AM
Well, by completely bypassing the InstallShield script, and calling
the WINAPI call SHBrowseForFolder, I was able to get the job done..

here is the complete code I ended up using, it forces the browse
command to start from the network level instead of at the "My Desktop"
level which is default for the SelectFolderEx/SHBrowseForFolder calls
(It will return a value of svPrinterPath):

prototype DialogNetworkPrinter( BYREF STRING );
prototype WINAPI.AddPrinterConnection(BYVAL STRING);
prototype BOOL Shell32.SHItemID(BYVAL STRING );
prototype GetFolderValue(long);
prototype shell32.SHGetPathFromIDList(long, byref string);
prototype shell32.SHGetSpecialFolderLocation(byval long, byval
long,long);
prototype shell32.SHBrowseForFolder(long);

typedef SHITEMID //' mkid
begin
LONG cb; // ' Size of the ID (including cb itself)
CHAR abID(); //' The item ID (variable length)
end;

typedef ITEMIDLIST //' idl
begin
SHITEMID mkid ;
end;


typedef BROWSEINFO // ' bi
begin
long hOwner;
long pidlRoot;
LPSTR pszDisplayName;
LPSTR lpszTitle;
long ulFlags;
long lpfn;
long lParam;
long iImage;
end;

#define NOERROR 0
#define CSIDL_DESKTOP 0x0
#define CSIDL_PROGRAMS 0x2
#define CSIDL_CONTROLS 0x3
#define CSIDL_PRINTERS 0x4
#define CSIDL_PERSONAL 0x5
#define CSIDL_FAVORITES 0x6
#define CSIDL_STARTUP 0x7
#define CSIDL_RECENT 0x8
#define CSIDL_SENDTO 0x9
#define CSIDL_BITBUCKET 0xA
#define CSIDL_STARTMENU 0xB
#define CSIDL_DESKTOPDIRECTORY 0x10
#define CSIDL_DRIVES 0x11
#define CSIDL_NETWORK 0x12
#define CSIDL_NETHOOD 0x13
#define CSIDL_FONTS 0x14
#define CSIDL_TEMPLATES 0x15 // ' (ShellNew folder)

///////////////////////////////////////////////////////////////////////////////
//
// Function: DialogNetworkPrinter
//
// Purpose: Gets the path to the network printer and returns a string
location
//
//
///////////////////////////////////////////////////////////////////////////////
function DialogNetworkPrinter( svPrinterPath )

BROWSEINFO BI;
long nFolder;
ITEMIDLIST IDL;
long pIdl;
STRING sPath[MAX_PATH];
STRING sCBValue[MAX_PATH];
begin
//The dialog's owner window...
BI.hOwner = GetWindowHandle ( HWND_INSTALL );

//' Set the Browse dialog root folder
nFolder = GetFolderValue(2);

nFolder=18;

SHGetSpecialFolderLocation(GetWindowHandle(HWND_INSTALL),nFolder,&IDL);
BI.pidlRoot = IDL.mkid.cb;

BI.ulFlags = BIF_BROWSEFORPRINTER;

pIdl = SHBrowseForFolder(&BI);

if(pIdl==0) then
MessageBox ("You must select a valid Printer" + "", WARNING);
endif;

SHGetPathFromIDList(pIdl,sPath);

svPrinterPath = sPath;
end;

///////////////////////////////////////////////////////////////////////////////
//
// Function: GetFolderValue
//
// Purpose: Get's the ID handle of a specific folder
//
///////////////////////////////////////////////////////////////////////////////

function GetFolderValue(wIdx)
//' Returns the value of the system folder constant specified by wIdx
//' See BrowsDlg.bas for the system folder nFolder values
begin
//' The Desktop
if (wIdx < 2) then
return 0;
//' Programs Folder --> Start Menu Folder
else
if (wIdx < 12) then
return wIdx;
//' Desktop Folder --> ShellNew Folder
else // wIdx >= 12
return (wIdx + 4);
endif;
endif;

end;



This seems to work for for the printer installation.
I hope it helps someone else someday. :)

-Benny Nabours


On Fri, 8 Dec 2000 12:02:24 +0100, "Stefan Krueger" <@> wrote:

>True, it doesn't work for printer (I hadn't tested for printers), but
>for file system paths the bug is fixed in 6.22.
>Maybe calling the WinAPI directly would be the only way then. If you
>can't get it to work: have you tried to place the API call in a DLL?
>
>I've also noticed some strange things in your code below, like the
>following:
>
>nFlags= "BIF_BROWSEFORPRINTER";
>// nFlags should be a NUMBER, and BIF_BROWSEFORPRINTER should not have
>quotes. But you're not using nFlags in the function call.
>
>bFolderExists = ExistsDir (nFlags);
>// I guess you meant: ExistsDir(svDir); however I doubt that this will
>work for printers
>
>--
>Stefan Krueger - Independent Setup Consultant
><<reply-to address is invalid to avoid spam>>
>
>Visit InstallSite at http://www.installsite.org to download
>free code samples, tips, tools and more...
>For information about individual support and consulting services
>please send a blank mail to the autoresponder at info@installsite.org
>
>Stefan Krueger and the InstallSite.org web site are not affiliated
>with InstallShield Software Corporation.
>
>"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
>news:3a302cb1.92567845@news.installshield.com...
>> Well, I went and got InstallShield 6.22, and guess what, it's STILL
>a
>> bug. This is getting quite frustrating. I feel like I'm sooo
>close,
>> yet so far away.
>>
>> Is there another alternative to qualify the return value?
>>
>> On Fri, 1 Dec 2000 22:30:18 +0100, "Stefan Krueger" <@> wrote:
>>
>> >This is a known bug in the function (documented in the Bugs
>Bulletin
>> >on http://www.installsite.org) that was fixed in IS 6.22. If you
>are
>> >using IS 6.1x you can add the BIF_EDITBOX flag as a workaround.
>This
>> >will cause the function to return the full path.
>> >
>> >--
>> >Stefan Krueger - Independent Setup Consultant
>> ><<reply-to address is invalid to avoid spam>>
>> >
>> >Visit InstallSite at http://www.installsite.org to download
>> >free code samples, tips, tools and more...
>> >For information about individual support and consulting services
>> >please send a blank mail to the autoresponder at
>info@installsite.org
>> >
>> >Stefan Krueger and the InstallSite.org web site are not affiliated
>> >with InstallShield Software Corporation.
>> >
>> >
>> >"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
>> >news:3a27fb41.159335562@news.installshield.com...
>> >> Well, I use the SelectDirEx function, and it seems to be ok, but
>it
>> >> does not return the Network Printer location as a fully qualified
>> >> value.
>> >>
>> >> IE , I browse network, select Printer on Computer1 named Printer,
>I
>> >> would want it to return
>> >> "\\Computer1\Printer" but it just returns "Printer"
>> >>
>> >> Any idea how to force it to return the fully qualified name?
>> >>
>> >> Here is what I am doing:
>> >>
>> >>
>>
>>/////////////////////////////////////////////////////////////////////
>/
>> >/////////
>> >> //
>> >> // Function: DialogNetworkPrinter
>> >> //
>> >> // Purpose: Gets the path to the network printer and returns a
>> >string
>> >> location
>> >> //
>> >> //
>> >>
>>
>>/////////////////////////////////////////////////////////////////////
>/
>> >/////////
>> >> function DialogNetworkPrinter( svPrinterPath )
>> >> LONG lpIDList;
>> >> STRING szTitle, szMsg, nFlags, svDir;
>> >> STRING szEditBoxStaticText, szTreeControlStaticText;
>> >> BOOL bCreate, bFolderExists;
>> >> NUMBER nResult;
>> >>
>> >> begin
>> >> repeat
>> >> szTitle="Select Printer";
>> >> szMsg= "";
>> >> nFlags= "BIF_BROWSEFORPRINTER";
>> >>
>> >>
>> >> nResult = (SelectDirEx (szTitle, szMsg,
>szEditBoxStaticText,
>> >> szTreeControlStaticText, BIF_BROWSEFORPRINTER, svDir) > 0);
>> >>
>> >> if nResult = 0 then
>> >> bFolderExists = ExistsDir (nFlags);
>> >> if bFolderExists = NOTEXISTS then
>> >> szMsg = "%s does not exist.\nPlease choose an existing
>> >> Printer.";
>> >> SprintfBox (WARNING, szTitle, szMsg, nFlags);
>> >> endif;
>> >> endif;
>> >>
>> >> until (nResult = CANCEL) || (bFolderExists = EXISTS);
>> >>
>> >> svPrinterPath = svDir;
>> >>
>> >> end;
>> >>
>> >> On Fri, 1 Dec 2000 10:57:41 +0100, "Stefan Krueger" <@> wrote:
>> >>
>> >> >Have you tried the built in function SelectDirEx with
>> >> >BIF_BROWSEFORPRINTER?
>> >> >In your code I don't see where you specify the sBuffer for
>> >> >tBrowseInfo.
>> >> >
>> >> >--
>> >> >Stefan Krueger - Independent Setup Consultant
>> >> ><<reply-to address is invalid to avoid spam>>
>> >> >
>> >> >Visit InstallSite at http://www.installsite.org to download
>> >> >free code samples, tips, tools and more...
>> >> >For information about individual support and consulting services
>> >> >please send a blank mail to the autoresponder at
>> >info@installsite.org
>> >> >
>> >> >Stefan Krueger and the InstallSite.org web site are not
>affiliated
>> >> >with InstallShield Software Corporation.
>> >> >
>> >> >"Benny Nabours" <nabours1@earthlink.net> schrieb im Newsbeitrag
>> >> >news:3a26a896.72637006@news.installshield.com...
>> >> >> Oops.. the DialogNetworkPrinter code is as follows:
>> >> >>
>> >> >>
>> >>
>>
>>>////////////////////////////////////////////////////////////////////
>/
>> >/
>> >> >/////////
>> >> >> //
>> >> >> // Function: DialogNetworkPrinter
>> >> >> //
>> >> >> // Purpose: Gets the path to the network printer and returns
>a
>> >> >string
>> >> >> // location
>> >> >> //
>> >> >> //
>> >> >>
>> >>
>>
>>>////////////////////////////////////////////////////////////////////
>/
>> >/
>> >> >/////////
>> >> >> function DialogNetworkPrinter( svPrinterPath )
>> >> >>
>> >> >> LONG lpIDList;
>> >> >> STRING sBuffer[MAX_PATH];
>> >> >> STRING szTitle;
>> >> >> BrowseInfo tBrowseInfo;
>> >> >>
>> >> >>
>> >> >> begin
>> >> >> szTitle = "";
>> >> >> tBrowseInfo.hWndOwner = GetWindowHandle ( HWND_INSTALL );
>> >> >> tBrowseInfo.lpszTitle = &szTitle;
>> >> >> tBrowseInfo.ulFlags = BIF_BROWSEFORPRINTER;
>> >> >>
>> >> >> if ( UseDLL ( FILENAME_SHELL ) < 0 ) then
>> >> >> MessageBox(ERROR_SHELL_NOLOAD, SEVERE );
>> >> >> endif;
>> >> >>
>> >> >> lpIDList = SHBrowseForFolder(&tBrowseInfo);
>> >> >> if (lpIDList) then
>> >> >> SHGetPathFromIDList(lpIDList, sBuffer);
>> >> >>
>> >> >> svPrinterPath = sBuffer; // string path
>> >> >> endif;
>> >> >> UnUseDLL(FILENAME_SHELL);
>> >> >>
>> >> >>
>> >> >>
>> >> >> end;
>> >> >>
>> >> >> On Thu, 30 Nov 2000 18:13:48 GMT, nabours1@earthlink.net
>(Benny
>> >> >> Nabours) wrote:
>> >> >>
>> >> >> >Well, I tried the 6.2 version, but still get the same
>problem..
>> >> >> >again, only on Windows ME.. here is the code I am using to
>try
>> >to
>> >> >> >browse the network for a network printer:
>> >> >> >
>> >> >> >function DialogShowAskPath()
>> >> >> >
>> >> >> > STRING szTitle, szMsg;
>> >> >> > NUMBER nCreateDialog, nId, nResult;
>> >> >> > BOOL bDone;
>> >> >> >
>> >> >> >begin
>> >> >> > nCreateDialog = EzDefineDialog(CUST_DIAG_PORT,
>> >> >ISUSER,"",30001);
>> >> >> >
>> >> >> > //Display dialog
>> >> >> > bDone = FALSE;
>> >> >> > while (bDone=FALSE)
>> >> >> > nId = WaitOnDialog(CUST_DIAG_PORT);
>> >> >> > switch(nId)
>> >> >> > case DLG_INIT:
>> >> >> >
>> >> >> > case SD_PBUT_CONTINUE:
>> >> >> > bDone = TRUE;
>> >> >> > case SD_PBUT_BACK:
>> >> >> > bDone = TRUE;
>> >> >> > nResult = SD_PBUT_BACK;
>> >> >> > case SD_PBUT_EXITSETUP:
>> >> >> > Do(EXIT);
>> >> >> > case BROWSEBUTTON:
>> >> >> > DialogNetworkPrinter( svPrinterPath );
>> >> >> > CtrlSetText(CUST_DIAG_PORT, 30130,
>> >> >> >svPrinterPath);
>> >> >> > case DLG_ERR:
>> >> >> > MessageBox(ERROR_DIALOG, SEVERE);
>> >> >> > bDone = TRUE;
>> >> >> > endswitch;
>> >> >> >
>> >> >> > endwhile;
>> >> >> > CtrlGetText(CUST_DIAG_PORT, 30130, svPrinterPath);
>> >> >> > EndDialog(CUST_DIAG_PORT);
>> >> >> > ReleaseDialog(CUST_DIAG_PORT);
>> >> >> > return nResult;
>> >> >> >end;
>> >> >> >
>> >> >> >This works fine on all other versions of Windows, but on ME
>it
>> >> >simply
>> >> >> >browses to the Desktop, and does not allow me to see the
>Network
>> >or
>> >> >> >Local system drives...
>> >> >> >
>> >> >> >On Wed, 29 Nov 2000 19:30:49 -0600, "Kevin-InstallShield"
>> >> >> ><supportnews@installshield.com> wrote:
>> >> >> >
>> >> >> >>Hello Benny,
>> >> >> >>
>> >> >> >>Windows ME came out after IS Pro 6.1x. Therefore
>InstallShield
>> >> >begins
>> >> >> >>Windows ME support with 6.22. To prove that this will work
>for
>> >> >you you can
>> >> >> >>download the eval version of 6.22 and try it. To get the
>eval
>> >> >version visit
>> >> >> >>our web site, www.installshield.com and you can download it
>> >from
>> >> >our
>> >> >> >>Products tab.
>> >> >> >>
>> >> >> >>Have a good day Benny.
>> >> >> >>
>> >> >> >>-Kevin
>> >> >> >>InstallShield Tech Support
>> >> >> >>
>> >> >> >>
>> >> >> >>"Benny Nabours" <nabours1@earthlink.net> wrote in message
>> >> >> >>news:3a25587f.592809915@news.installshield.com...
>> >> >> >>> Hi everyone.
>> >> >> >>>
>> >> >> >>> I have an interesting predicament...
>> >> >> >>>
>> >> >> >>> I have a Browse Network dialog in my installation, when
>the
>> >> >install is
>> >> >> >>> running, the Browse for Network Printer dialog comes up.
>> >This
>> >> >works
>> >> >> >>> fine on all versions of Windows EXCEPT Windows ME. When I
>> >run
>> >> >the
>> >> >> >>> install on all other version, if you click browse, it
>brings
>> >up
>> >> >the
>> >> >> >>> following:
>> >> >> >>>
>> >> >> >>> Desktop -
>> >> >> >>> My Computer-
>> >> >> >>> <floppy drive>
>> >> >> >>> <hard drive>
>> >> >> >>> <Network Neighborhood>
>> >> >> >>> <Mapped drives, etc...>
>> >> >> >>>
>> >> >> >>> When I run this command on Windows ME , it brings up the
>> >> >Desktop, with
>> >> >> >>> all desktop shortcuts only, no access to My Computer, no
>> >access
>> >> >to
>> >> >> >>> Network Neghborhood, etc... Any idea why this might be
>> >> >happening?
>> >> >> >>> Is there a bug with IS 6.10 and Windows ME? Would
>upgrading
>> >to
>> >> >6.22
>> >> >> >>> fix this problem?
>> >> >> >>>
>> >> >> >>> If I can supply you with more information, I would be
>happy
>> >to..
>> >> >> >>>
>> >> >> >>> Thank you in advance for ANY assistance or advice you may
>be
>> >> >able to
>> >> >> >>> offer.
>> >> >> >>>
>> >> >> >>> -Benny
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >
>> >>
>> >
>>
>
>
>

NewsArchive
01-30-2001, 01:00 AM
OK thanks Stefan.

Could you tell me where I can find documentation on what to do under WinME?

I guess I can either:

(1) edit the autoexec.bat and set the PATH and COMSPEC variables, then ask
the user to reboot

(2) change PATH and COMSPEC under

HKEY_LOCAL_MACHINE\system\currentconrtrolset\control\sessionmanager\environm
ent\

but which is the correct way to do it?

Thanks, Andrew

Stefan Krueger <@> wrote in message <3a75a602@12.41.20.38>...
>Windows ME no longer stores the PATH in autoexec.bat (it moves any
>entries you make there to the registry on next reboot). I guess that#s
>the cause of your problem...
>
>--
>Stefan Krueger - Independent Setup Consultant
><<reply-to address is invalid to avoid spam>>
>
>Visit InstallSite at http://www.installsite.org to download
>free code samples, tips, tools and more...
>For information about individual support and consulting services
>please send a blank mail to the autoresponder at info@installsite.org
>
>Stefan Krueger and the InstallSite.org web site are not affiliated
>with InstallShield Software Corporation.
>
>"Andrew Dunn" <adunn@abingdon.geoquest.slb.com> schrieb im Newsbeitrag
>news:3a70368d@12.41.20.38...
>> Hello,
>>
>> I have IS 6.22 working on NT and 9X targets, but WinME doesn't seem
>to be a
>> supported target. All I need to do is to change the PATH and
>increase the
>> environment space (equivalent of SHELL COMMAND.COM /P /E:2048) on
>WinME,
>> since everything else seems to work. Could someone tell me how to do
>this
>> please?
>>
>> Also, the space required for installation that's reported by IS 6.22
>> SdComponentTree is completely wrong (way too small a number or
>zero). Any
>> idea why?
>>
>> Thanks for your help, Andrew
>>
>>
>

NewsArchive
05-02-2001, 12:00 AM
Thanks for the help everybody.

Regards,

Aaron Young

"Bryan Kennedy" <kennedy@cisco.com> wrote in message
news:3af0367e@12.41.20.38...
> Al the values you need to check this are in the registry.
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
> or
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
>
> "Aaron Young" <aaron@merlininteractive.fsbusiness.co.uk> wrote in message
> news:3aef3619@12.41.20.38...
> Hi all,
>
> Is there anyway I can use 6.1 to recognise Windows XP and allow an
> installation to proceed ? Can "new" operating system definitions be added
to
> IS without having to wait for an update ?
>
> Thanks in advance.
>
> Aaron Young
>
>
>
>

NewsArchive
05-04-2001, 12:00 AM
Sure it will RUN but not correctly.

I have IS Pro 6.12 and even though it does not support WinMe it can still
install on WinMe. BUT uninstall is not possible. So...your fact that IS can
install on ANY OS is true but you have to add that UNINSTALL do not work for
new OS.

/M

"Ted" <ted__w@home.com> wrote in message news:3af22897@12.41.20.38...
> Biggest Myth: your Installshield setup won't run on any new OS.
>
> FACT: Any version of Installshield setup runs on any operating system,
it's
> just that you can't have automatic OS specific file groups for new
operating
> systems. In fact my original IS 5.5 install that only has support for
> Windows 95 and NT 4 still runs on every OS. I'll repeat it again: The
> supported OS is NOT a limiting choice. It only gives you the convenience
of
> having OS specific groups/components (through ComponentFilterOS).
>
> Also one thing to remember is to not put any specific script code like if
> not equal NT 4 then stop. I've seen many an install that cannot be
forced
> to install on Windows 2000 because of it. Always use greater than or
equal
> to conditions. I don't trust Installshield's sysinfo variables like
> bWin2000 because who knows if they'll be true or false for XP or beyond.
> Always use GetSystemInfo with OS, WINMAJOR, and WINMINOR instead.
>
> Ted.
>
>
> "Aaron Young" <aaron@merlininteractive.fsbusiness.co.uk> wrote in message
> news:3aef3619@12.41.20.38...
> > Hi all,
> >
> > Is there anyway I can use 6.1 to recognise Windows XP and allow an
> > installation to proceed ? Can "new" operating system definitions be
added
> to
> > IS without having to wait for an update ?
> >
> > Thanks in advance.
> >
> > Aaron Young
> >
> >
>
>

NewsArchive
06-14-2001, 12:00 AM
I'll send this to IS bug reports as well but, the example code in the KB
(Q101296), that detects the operating system, won't ever work because XP
Beta2 is currently returning 5.5 for Major and Minor. This is the same
exact response for Windows 2000.

Dwight Funk
POWERWAY, Inc.


"Kevin-InstallShield" <supportnews@installshield.com> wrote in message
news:3b158852@12.41.20.38...
> Hello,
>
> XP is still in Beta version but we fully plan on supporting XP with our
> products. To help eliminate bugs before we release we are asking that any
> user who uses an InstallShield product (preferrably latest version) on the
> XP OS to submit the bugs/troubles they are having to:
> http://support.installshield.com/contact/bugrpt.asp
>
> -Kevin
> ISTS
>
> "Al Christoph" <ac2@wwnet.com> wrote in message
> news:3b0d4583$1@12.41.20.38...
> > I ask in my ignorance: When is support for Windows XP expected? Or does
it
> > look so much like Windows ?? that there will be no additional support?
How
> > does one detect it in InstallShield 6.X x<=3???
> >
> > Regards,
> > Al Christoph
> >
> >
>
>

NewsArchive
06-15-2001, 12:00 AM
I was wrong...
XP = 5.1
and
2000 = 5.0.

Does anyone know what ME returns for the minor version ?

This means that the KB article could be updated to reflect this.

Dwight Funk
POWERWAY, Inc.



"Kevin-InstallShield" <supportnews@installshield.com> wrote in message
news:3b158852@12.41.20.38...
> Hello,
>
> XP is still in Beta version but we fully plan on supporting XP with our
> products. To help eliminate bugs before we release we are asking that any
> user who uses an InstallShield product (preferrably latest version) on the
> XP OS to submit the bugs/troubles they are having to:
> http://support.installshield.com/contact/bugrpt.asp
>
> -Kevin
> ISTS
>
> "Al Christoph" <ac2@wwnet.com> wrote in message
> news:3b0d4583$1@12.41.20.38...
> > I ask in my ignorance: When is support for Windows XP expected? Or does
it
> > look so much like Windows ?? that there will be no additional support?
How
> > does one detect it in InstallShield 6.X x<=3???
> >
> > Regards,
> > Al Christoph
> >
> >
>
>

NewsArchive
06-17-2001, 12:00 AM
See attachment. Hope this helps!

-Nathan Lewis
http://www.ticz.com/~nlewis



"Dwight Funk" <defunk@powerway.com> wrote in message
news:3b2a74be$1@12.41.20.38...
> I was wrong...
> XP = 5.1
> and
> 2000 = 5.0.
>
> Does anyone know what ME returns for the minor version ?
>
> This means that the KB article could be updated to reflect this.
>
> Dwight Funk
> POWERWAY, Inc.
>
>
>
> "Kevin-InstallShield" <supportnews@installshield.com> wrote in message
> news:3b158852@12.41.20.38...
> > Hello,
> >
> > XP is still in Beta version but we fully plan on supporting XP with our
> > products. To help eliminate bugs before we release we are asking that
any
> > user who uses an InstallShield product (preferrably latest version) on
the
> > XP OS to submit the bugs/troubles they are having to:
> > http://support.installshield.com/contact/bugrpt.asp
> >
> > -Kevin
> > ISTS
> >
> > "Al Christoph" <ac2@wwnet.com> wrote in message
> > news:3b0d4583$1@12.41.20.38...
> > > I ask in my ignorance: When is support for Windows XP expected? Or
does
> it
> > > look so much like Windows ?? that there will be no additional support?
> How
> > > does one detect it in InstallShield 6.X x<=3???
> > >
> > > Regards,
> > > Al Christoph
> > >
> > >
> >
> >
>
>

NewsArchive
08-10-2001, 12:00 AM
Joshua:

Is "7" currently available or is XP support planned for 6X in the immediate
future? XP is drawing nearer (we're testing software on the betas) and I
would like to be able to use something other than the version number (betas
show 5.5, apparently) to know where we are.

Inquiring minds want to know...

Andy

--
---------------------------------------------------------------
Andy Marchant-Shapiro andyms@firstlogic.com
Programmer/Analyst __o 608.782.5000.x2585
Firstlogic, Inc. _-\<,_ La Crosse, WI
______________________________(*)/_(+)_________________________


"Joshua - InstallShield" <VB@installshield.com> wrote in message
news:3b7304e5$1@news.installshield.com...
> George,
>
> We fully support Windows XP only in InstallShield Developer 7 at the
moment.
> Other versions of InstallShield should work correctly, as Windows should
be
> fully backwards-compatible, but they have not been fully testing under
this
> operating system so problems could occur.
>
> Regards,
>
> Joshua
> InstallShield
>
> "George" <gtaro@pacbell.net> wrote in message
> news:3b7300ca@news.installshield.com...
> > Hello,
> >
> > I have a project in InstallShield 6.1. Will my project work on Windows
> XP?
> >
> >
>
>

NewsArchive
08-10-2001, 12:00 AM
Andy,

InstallShield Developer 7 is currently available at the link below:

http://www.installshield.com/isd

Regards,

Joshua
InstallShield

"Andy Marchant-Shapiro" <andyms@firstlogic.com> wrote in message
news:3b73f1d6$1@news.installshield.com...
> Joshua:
>
> Is "7" currently available or is XP support planned for 6X in the
immediate
> future? XP is drawing nearer (we're testing software on the betas) and I
> would like to be able to use something other than the version number
(betas
> show 5.5, apparently) to know where we are.
>
> Inquiring minds want to know...
>
> Andy
>
> --
> ---------------------------------------------------------------
> Andy Marchant-Shapiro andyms@firstlogic.com
> Programmer/Analyst __o 608.782.5000.x2585
> Firstlogic, Inc. _-\<,_ La Crosse, WI
> ______________________________(*)/_(+)_________________________
>
>
> "Joshua - InstallShield" <VB@installshield.com> wrote in message
> news:3b7304e5$1@news.installshield.com...
> > George,
> >
> > We fully support Windows XP only in InstallShield Developer 7 at the
> moment.
> > Other versions of InstallShield should work correctly, as Windows should
> be
> > fully backwards-compatible, but they have not been fully testing under
> this
> > operating system so problems could occur.
> >
> > Regards,
> >
> > Joshua
> > InstallShield
> >
> > "George" <gtaro@pacbell.net> wrote in message
> > news:3b7300ca@news.installshield.com...
> > > Hello,
> > >
> > > I have a project in InstallShield 6.1. Will my project work on
Windows
> > XP?
> > >
> > >
> >
> >
>
>

NewsArchive
08-10-2001, 12:00 AM
Joshua:

Thanks--discovered this. However...

***Will IS Professional 6.x support Windows XP at some point in the near
future?*** My experience over the past six years or so is that major
version transitions in IS are more than a little painful...I'd like to
prepare for the pain, if necessary.

Andy

"Joshua - InstallShield" <VB@installshield.com> wrote in message
news:3b73f72a$1@news.installshield.com...
> Andy,
>
> InstallShield Developer 7 is currently available at the link below:
>
> http://www.installshield.com/isd
>
> Regards,
>
> Joshua
> InstallShield
>
> "Andy Marchant-Shapiro" <andyms@firstlogic.com> wrote in message
> news:3b73f1d6$1@news.installshield.com...
> > Joshua:
> >
> > Is "7" currently available or is XP support planned for 6X in the
> immediate
> > future? XP is drawing nearer (we're testing software on the betas) and
I
> > would like to be able to use something other than the version number
> (betas
> > show 5.5, apparently) to know where we are.
> >
> > Inquiring minds want to know...
> >
> > Andy
> >
> > --
> > ---------------------------------------------------------------
> > Andy Marchant-Shapiro andyms@firstlogic.com
> > Programmer/Analyst __o 608.782.5000.x2585
> > Firstlogic, Inc. _-\<,_ La Crosse, WI
> > ______________________________(*)/_(+)_________________________
> >
> >
> > "Joshua - InstallShield" <VB@installshield.com> wrote in message
> > news:3b7304e5$1@news.installshield.com...
> > > George,
> > >
> > > We fully support Windows XP only in InstallShield Developer 7 at the
> > moment.
> > > Other versions of InstallShield should work correctly, as Windows
should
> > be
> > > fully backwards-compatible, but they have not been fully testing under
> > this
> > > operating system so problems could occur.
> > >
> > > Regards,
> > >
> > > Joshua
> > > InstallShield
> > >
> > > "George" <gtaro@pacbell.net> wrote in message
> > > news:3b7300ca@news.installshield.com...
> > > > Hello,
> > > >
> > > > I have a project in InstallShield 6.1. Will my project work on
> Windows
> > > XP?
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
08-13-2001, 12:00 AM
Dear Sir:
When I test my installer which made by InstallShield Professional 6 on
Windows XP,I got some errors as the attached files.
Would you please help me to check it??

Thank you!

Amy



"Joshua - InstallShield" <VB@installshield.com> ¼¶¼g©ó¶l¥ó
news:3b744279$1@news.installshield.com...
> George,
>
> Your IPSE 6.1x project should work with Windows XP, however it is not
> officially supported. Therefore you may encounter problems as this
version
> has never been fully tested with XP.
>
> At this time our InstallShield Developer 7 product officially supports
> Windows XP. More information on this product can be found at
> http://www.installshield.com/isd
>
> Regards,
>
> Joshua
> InstallShield
>
> "George" <gtaro@pacbell.net> wrote in message
> news:3b72e048@news.installshield.com...
> > Will my Installshield 6.1 project work on Windows XP?
> >
> > George
> >
> >
>
>

NewsArchive
10-11-2001, 12:00 AM
It also means that support for Windows XP as the target OS is provided as
well. This is only true for version 6.31 in IS Pro.

Alain
InstallShield Software Corporation

"Alain Breillatt" <alainb@installshield.com> wrote in message
news:3bc4d89a$1@news.installshield.com...
> Ramani,
>
> If you're asking whether setups authored using IS Pro 6.31 are supported
in
> Windows XP, the answer is yes.
>
> http://www.installshield.com/downloads/isp/is6.31_relnotes.asp
> See the last bullet point under other enhancements. It could be more
> explicit, but that's what it means.
>
> Alain
> InstallShield Software Corporation
>
> "Ramani" <rgujjula@resonate.com> wrote in message
> news:3bc38a64$1@news.installshield.com...
> > Is InstallShield 6.31 supported on Windows XP?
> >
> >
>
>