chetbaker

I really liked all the work done so far, and would like to share some of my thougts about improvements also We could implement a variation of the GetOsVer(), maybe GetOsVerNum() that only returns a predifined number so that we can avoid lengthy cond[pn] statements if we want to check if os is greater (meaning newer) then the required. An explample of what i mean would be the comandlinetool from Xteq.....but wy not implement it in java ? I beleave most people that actually use this funciton do not want to check for GetOSVer()='XP' but would rather prefer to search for GetOsVer()>6 ? Or am i only missing a buid in java function ? ....more used to VB i would love to see bernr's fork with configs implemented in one of the actual versions maybe the arraynames, for example in config.js, could be renamed a bit, before all people get used to the new fields and need to reedit them. textl[pn] > txtl[pn] texti[pn] > txti[pn] to try to have them all with names not longer then 4 chars (merely optical reasons) in case of bernr's version configs[pn] > cfgs[pn] I for myself am using some additional fields to later ease the update of the installation packages and maybe automate even better the config selection (bernr's version) not only taken into account computername put also OS Bits and Regional Settings: licp[pn]=['freeware'] // license type for private use licc[pn]=['freeware'] // license type for comercial enviroment lico[pn]=['false'] // online registration normaly required licd[pn]=['yes incl. mod'] // Distribution allowed link[pn]=['URL'] // to ad to the image, textpopup with downloadlocation plng[pn]=['EN', 'BR'] // Languages supported by program, comma separated pbit[pn]=['32'] // compiled fore OS with xx bits chng[pn]=['DATE'] // Date of last check/change And to close the message one little question. When or in wich fields of the config.js am i suposed to use the single quotes around the values ? As it seems everywhere exept in ordr[pn] - right ?