1. Devang Modi
  2. PowerBuilder
  3. Tuesday, 17 April 2018 13:59 PM UTC

HI Team,

When I select WIN.INI in PowerServer Toolkit Configuration, same WIN.INI is not loaded in AEM. 

I can see below WIN.INI content in AEM INI Files. 

 

[aedebug]
[clock]
[colors]
activeborder=180 180 180
activetitle=153 180 209
appworkspace=171 171 171
background=0 0 0
buttonalternateface=0 0 0
buttondkshadow=105 105 105
buttonface=240 240 240
buttonhilight=255 255 255
buttonlight=227 227 

[console]
facename=__DefaultTTFont__

[cursors]
[desktop]
blocksendinputresets=0
coolswitchcolumns=7
coolswitchrows=3
cursorblinkrate=530
dockmoving=1
dragfrommaximize=1
dragfullwindows=1
dragheight=4
dragwidth=4
fontsmoothing=2
leftoverlapchars=3
menushowdelay=400

[devices]
send to onenote 2016=winspool,nul:
microsoft xps document writer=winspool,Ne00:
microsoft print to pdf=winspool,Ne01:
fax=winspool,Ne02:
\\printsrvind\printit_black=winspool,Ne04:
epson m200 series=winspool,Ne03:

[embedding]
[extensions]
[fonts]
arial (truetype)=arial.ttf
arial black (truetype)=ariblk.ttf
arial bold (truetype)=arialbd.ttf
arial bold italic (truetype)=arialbi.ttf
arial italic (truetype)=ariali.ttf
calibri (truetype)=calibri.ttf

[fontsubstitutes]
arabic transparent=Arial
arabic transparent bold=Arial Bold
arabic transparent bold,0=Arial Bold,178
arabic transparent,0=Arial,178
arial baltic,186=Arial,186
arial ce,238=Arial,238
arial cyr,204=Arial,204

[gre_initialize]
[intl]
locale=00000409
localename=en-US
s1159=AM
s2359=PM
scountry=United States
scurrency=$
sdate=/
sdecimal=.
sgrouping=3;0
slanguage=ENU
slist=,
slongdate=dddd, MMMM d, yyyy
smondecimalsep=.
smongrouping=3;0

[ioprocs]
[mci extensions]
3g2=MPEGVideo
3gp=MPEGVideo
3gp2=MPEGVideo
3gpp=MPEGVideo
aac=MPEGVideo
adt=MPEGVideo
adts=MPEGVideo
aif=MPEGVideo
aifc=MPEGVideo
aiff=MPEGVideo
asf=MPEGVideo
asx=MPEGVideo
au=MPEGVideo
avi=avivideo
cda=CDAudio

[modulecompatibility]
[mscharmap]
[net_files]
[nwcs]
[ports]
com1:=9600,n,8,1
com2:=9600,n,8,1
com3:=9600,n,8,1
com4:=9600,n,8,1
file:=
lpt1:=
lpt2:=
lpt3:=
portprompt:=
ne00:=
ne01:=
ne02:=
nul:=
ne03:=
ne04:=

[printerports]
send to onenote 2016=winspool,nul:,15,45
microsoft xps document writer=winspool,Ne00:,15,45
microsoft print to pdf=winspool,Ne01:,15,45
fax=winspool,Ne02:,15,45
\\printsrvind\printit_black=winspool,Ne04:,15,45

[sounds]
[true]

 

Due to this my application is not able to run becoz application is not able to find expected content in WIN.INI

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 18 April 2018 14:03 PM UTC
  2. PowerBuilder
  3. # 1

Hi Devang;

    FWIW: The name "WIN.INI" is an MS-Windows reserved file name since way to the days of MS-Windows 3.0. My suggestion would be to rename your INI to something that matches your application name (basically anything other than Win.ini) and try again. I have been using Appeon Web and now PowerServer Web since 2008 and never had an INI file issue.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Appeon Support Team Accepted Answer Pending Moderation
  1. Wednesday, 18 April 2018 01:20 AM UTC
  2. PowerBuilder
  3. # 2

Hi,

Thanks for reporting this problem! We reproduced it on our end and will do further research to figure it out. We will keep you posted about the progress. 

Please temporary workaround this issue by using another name, for example: mywin.ini.

Regards,
ZhaoKai

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.