• Jacs Packaging : 3.20.00 or 3.20.0.1
• HCI Packaging: 3.30 12/2/2010
• JSO Packaging: 3.30 12/2/2010
• SIM Packaging: 3.30 12/2/2010

• fix stop problem
• remove \bin from image run command. see JwvJACSOSInterface. Log files may need a progData ini file setting. the .exes should take care of them selves because they will all be in the startup directory.
• fix missing gdk messages in jacs.log
• add packaging instructions info to jacs.log

• Take a clean image and load the ST: Server Workbench Base feature
• Load the Jas Packaging Instructions config map.
• Create an Windows XD image with just the TCP/IP feature
• Switch back to the development side and save the image as something like xdPackaging.
• TO generate all possible statistics, add this class side method:

  statisticsPolicyName
  
  ^#'EpGenericStatisticsPolicy'

• Sim is an XD image

• VP is not an XD image
• Help shows info about maps and versions and dates

• JAS Dev: Video Playback R3.0 SR1.02 1.8 is the latest map WORKS

• HCI version must match sim, currently 3.20
• HCI is not an XD image
• Help→About JAS shows info about maps and versions and dates
• JAS Packaging HCI version 2022 04 22 WORKS

Below is Obsolete

• Load jas sr1.02b into a clean image.
• added sst web services feature to required maps in 1.02b
• load jas pkg instructions 1.00c
• packager creates 38360 icx which starts but then cannot find jacs.

• Load jas hci 9/ or sr1.02 into a clean image.
• load sst web services feature.
• add AbtImageConfigurationApp to app list in pkg instructions 1.00B
• load jas pkg instructions 1.00B
• packager create 38205 icx which blows up with in PamCore»preStartUp with nil DNU readIniFIle.

• Load jas hci 9/ or sr1.02 into a clean image.
• load sst web services feature
• load jas pkg instructions and use latest verssion of NT pkg instructions
• packager create 7929 icx which blows up with in PamCore»preStartUp with nil DNU readIniFIle.

• removed \pf2\jas\bin from path - no diff
• tried service command line with esvio and nodialog - no diff
• renamed whjacs.exe in progFiles and whjacs.icx in progData amd start failed so path seems to be ok
• try loading both jas dev jso and jas packaging

• add EsTimeZoneApp to jas pkg instructions, then load into a clean image. this adds xd
• load jacs 100d into dev
• create xd with tcp only. jacs will not load without it.
• load jacs 100d.
• Need to add SCI CommTCP [413]1 to make image stop.
• package creates 6410 with no gdk or packaging rule compile errors
• copy standard abt.ini into vmcfg.ini
• image starts and write continuous output to jacs.log
• image does respond to stop from services.
• jacs.log show connection from env but jas dev jso in open image cannot find jacs

• add EsTimeZoneApp to jas pkg instructions, then load into a clean image. this adds xd
• load jacs 100d into dev
• create xd with tcp only. jacs will not load without it.
• load jacs 100d.
• package creates 6410 with no gdk or packaging rule compile errors
• copy standard abt.ini into vmcfg.ini
• image starts and write continuous output to jacs.log
• image does not respond to stop from services.

• change SstWinSockSocketDemultiplexor»initialize to remove call to missing method timeout:
• load jas pkg instructions 3.94a into a clean image. this adds xd.
• create map jacs 100d from its subordinate maps
• load jacs 100d into dev
• create xd with tcp only. jacs will not load without it.
• load jacs 100d.
• package creates 6410 with no gdk or packaging rule compile errors
• copy standard abt.ini into vmcfg.ini
• blows up with cant find setTimeZoneFromOS

• load jas pkg instructions 3.94a into a clean image. this adds xd.
• load jacs 100c into dev
• create xd with tcp only. jacs will not load without it.
• load jacs 100c.
• package creates 6410 with no gdk or packaging rule compile errors
• copy standard abt.ini into vmcfg.ini
• image gets past error 126
• blows up with SstWinSockSocketDemultiplexor»initialze does not understand timeout:

• load jas pkg instructions 3.94a into a clean image. this adds xd.
• load jacs 100c into dev
• create xd with tcp only. jacs will not load without it.
• load jacs 100c.
• package creates 6410 with no gdk or packaging rule compile errors
• still blows up with 126

• load jas pkg instructions 3/4 into a clean image. this adds xd.
• load jacs 100c into dev
• create xd with tcp only. jacs will not load without it.
• load jacs 100c.
• package creates 6304 with no gdk or packaging rule compile errors
• still blows up with 126

• load jas pkg instructions 3/4 into a clean image. this adds xd.
• load jacs 100c into dev
• create xd with tcp, oracle and xml.
• load jacs 100c.
• package creates 6304 with no gdk or packaging rule compile errors
• still blows up with 126

• Load jas dev jso 2/15 into clean image.←— NO THIS DOES NOT WORK!
• save as 91xd and restart.
• load jas pkg instructions 3/4.
• load server workbench feature.
• create xd image with just tcp.
• load jacs 100c.
• package create 7929 icx which blows up with 126
• this icx is different than V1 even though they are the same size

• Load jas dev jso 2/15 into clean image.←— NO THIS DOES NOT WORK!
• save as 91xd and restart.
• load jas pkg instructions last good map.
• load server workbench feature.
• create xd image with just tcp.
• load jacs 100c.
• package create 7929 icx which blows up with 126

• Load JAS Dev: JSO(2/15/2021 7:56:42 PM) (with its required maps). ←— NO THIS DOES NOT WORK!
• In XD, load JAS Packaging: Jacs R3.0 SR1.00c (with its required maps).
• From Browse Packaged Images, select Instructions in Database.
• Under JwxPackaging, select JwxJacsNtHeadless.
• Click Reduce and wait about 30 seconds.
• Select Examine and Fix Problems.
• Change Show Errors and Fatal Errors to Show Only Fatal Errors.
• Click Output Image and wait about 3 minutes.
• The image will be in C:\jas\PackagedImage\whJACS.icx.
• Click Close to close the Packager.
• Do not save your image.

• neither jas dev jso or packaged hci appear to talk to jacs over 127.0.0.1
• wireshark shows traffic between env and jacs
• use netstat -ab -p tcp to see what pids exist
• try chuck's machine next.

• in a clean 9.1 image (413), load Server Workbench
• SciSocketManager is in app SocketCommunicationsInterface which is in config map Envy Image SCI. It gets loaded by the selecting the Comm TCP feature when creating an XD image.
• Load latest HW config map which is a version. Apps cannot be versions.
• packager creates helloworldxd.icx with size 1526.
• runs fine and prints “Host name M6800.

• in a clean 9.1 image (413), load Server Workbench
• then load Dmacq HelloWorldXDWindowsPackaging 1.1.
• create an xd image with no features.
• load latest HelloWorld config map.
• packager creates helloworldxd.icx with size 1448.
• runs fine with

  echo off
  ..\nodialog -ihelloworldxd.icx -ini:abt.ini -lhw.txt
  type hw.txt