INFactoryM has been created for the developers that do not use eVB also and for
the ones that need more features than the one offered by INFactory single Cab.
The program remain easy to use and all the procedures are always fully driven,
that means that the user may use a button only to complete each program's step.
The informatios that the user must insert are only his program and target device's
details, the full list of the required files (NS runtime also if any) and the association
of each file with the the type requesed for WinCE system.
WHAT IS NEW in this version ?
- No steps buttons required, use only NEXT to change
screens and create code.
- You can now extract and install INFactory program
under any folder you like.
- No longer required to load manually the Runtime fles,
simply Check a Box
- You can create now two types of INI files. The first to
get immediate installer package. The second to test
the results and pass files to EZinstall if you like.
- More instructions available for each screens' program.
- Corrected a bug in Setup.exe that does not enabled
the use with multiple Cab files
Unzip the program and extract all the files to get a directory tree of wich
'INFactory' is the main folder. (see above)
ATTENTION !! Before using INFactory you must store all the required NSBasic
Runtime files and the others commonly used Dll into the relative subDirs
respecting their O.S. (If you wish to see how to get the files you need seeHERE).
As this version can create cab files for multiple O.S. or Cpu it is important that
the storage subDirs contain all the same files for each O.S. and Cpu.
If it is not so you will get an error and the cab files will not be created.
Your program(s) .nsb will be stored into the subDir 'ApplicationFiles' , the
resulting installation code will be available in the suDir 'CodeResult' at the
end of the procedure. The INFactoryMCI program is into the main folder .
You must add here now only the Cabwiz.exe files that INFactory will call to
create the CAB file. You should find it in the NSBasic CD, or in the eVB dirs
if you use it. Remember that you must accept Microsoft licence before use it.
As soon as the above has been done you are ready to use INFactoryMCI so
click on the exe file. You will see the following:
click NEXT
This last window requires to type some information about your application and to
select target device O.S. and relative CPU.
You can use the 'ALL Devices" and 'ALL' selection also respectively for O.S. and Cpu
but be carefully because you could obtain a very big installation package.
(Usually the best is to select an O.S. (pocketPC for example) and apply the 'ALL' option to Cpu
to leave the program select authomatically the commonly used Cpu.)
In this detail image you can see the little windows that show how many CPU you selected
and below the box that you must check if you wish to add authomatically the NSB Runtime
to your installation package.
As soon as you typed the information click on the button NEXT again.
You will see the following screen:
The two images represent the same screen. If you get the first and you see listed on the right
all the files that your project requires (Runtime also if any) you can go over clicking on the
NEXT button .
Otherwise click the ADD Files button on the left to change the screen to show the second image.
In this window you must select, in the top left list, the folder(s) path that contains the files
and/or other required Dlls that you stored therein. A click by the mouse on the file's name in
the list below will add the file name in the List at side. If you make a mistake clicking on the
file name in the list you may delete the same from the selection list.
As already said It is necessary, to create multiple Cab files, that any SubDir contain the same
files for each selected CPU otherwise you will get an error and the Cab files will be not created.
Please note anyway that it is not necessary to select the same file for each Cpu as the files you
add to the list will be applied authomatically to all the O.S. or Cpu previously selected, so you
need to open a path only to add th files names you wish.
At the end you should get a list with Your .nsb program name, the files DialogX.ocx,MSCEfile.dll
MSCEPicture.dll, Regsvrce.exe (Runtime Files directly added by the program) and all other Dll that
you program can need added by you. As soon as all the requested files are listed click on NEXT.
The list of the selected files on the right remain unchanged while on the left some Files.Type
will be shown. What you have to do here is to click on a file.type ( Files.Application for example),
confirm the adding at the prompt (see image above) and by a mouse's click on the Files' list to
associate a selected file name with the file.type ( in the example it may be Files.Application
<- with .> 'YourProgram.nsb').
Dlls, ocx and regsvr,exe are commonly to associate to Files.Windows while Basic.exe must be
associated with the files.NSbasic. For the shorcut associate the type with the program's name file.
To associate multiple files'name you do not need to click any time on the file.type. Click instead
sequantially on all the files'names only.
ATTENTION: there is no error adjustment for this operation.This is the reason of the prompt to confirm the
Files.Type to add. Anyway carefully click each files' name to avoid error.
At the end of the association click on NEXT
click SEE CODE
The code of your .INF file just created will be listed in the program's window and you can also
print it using the PRINT button below. To continue click again the 'see code' button now showing
caption 'HIDE CODE'.
This window shows the NEXT button disabled while there is a new button with the caption
'Create INF file'.
Click on it to effectively create the YourProg.INF file (it wil be saved into INFactory Dir).
The shown window remain unchanged but the button caption quotes now 'Create CAB file'
Click againt on the button and you will see start the black DOS windowof Cabwiz.exe that will
create your Cab file loading into the same all the files selected by you using the previuos steps.
As soon as the DOS window hides you will see a new window with the same button showing
the caption 'Create INI file'
This last window allows the user to choice which INI file(s) will be created.
The Default type must be used with the SetUp.exe file to perform a common installation directly.
The second type of INI file instead can be used to test the Cabs directly with AppMgr or to pass
the file(s) with the relative Cabs to EZsetUp to create better installation packages.
(the button below are still disabled in this Beta but will be available to authomatize the mentioned actions)
Click 'Create INI file'. No new window will be shown but you will see in the instruction space at
the bottom the word 'DONE !!' to inform you the end of the process.
Well. Go now to see the folder 'C:\INFactory\CodeResult using explorer.
You will see an image like the one below. The Cab files, the Setup.Ini and the Setup.exe file
are the ones you need to assemble your installer. As you can see below the same files, if you
Zip them will be about the 50 pct of their original dimension.
NOTE.: This is a working preview of the BETA program. It will be subject to others upgrade,
so if you test it remember that : 'ANY FEEDBACK WILL BE GREATLY APPRECIATED'
Upto now i tested the program on a Aero1550 Mips PPC and on a HP565 Arm PC2002 only.
YOU MAY DOWNLOAD THE PROGRAMHERE but note that this version version has been discontinued owing to the issuance of the new INFactoryW2003 version.
The easiest way to create an NSB Installer
click NEXT
This last window requires to type some information about your application and to select target device O.S. and relative CPU. You can use the 'ALL Devices" and 'ALL' selection also respectively for O.S. and Cpu but be carefully because you could obtain a very big installation package. (Usually the best is to select an O.S. (pocketPC for example) and apply the 'ALL' option to Cpu to leave the program select authomatically the commonly used Cpu.)
In this detail image you can see the little windows that show how many CPU you selected and below the box that you must check if you wish to add authomatically the NSB Runtime to your installation package. As soon as you typed the information click on the button NEXT again. You will see the following screen:
The two images represent the same screen. If you get the first and you see listed on the right all the files that your project requires (Runtime also if any) you can go over clicking on the NEXT button . Otherwise click the ADD Files button on the left to change the screen to show the second image. In this window you must select, in the top left list, the folder(s) path that contains the files and/or other required Dlls that you stored therein. A click by the mouse on the file's name in the list below will add the file name in the List at side. If you make a mistake clicking on the file name in the list you may delete the same from the selection list. As already said It is necessary, to create multiple Cab files, that any SubDir contain the same files for each selected CPU otherwise you will get an error and the Cab files will be not created. Please note anyway that it is not necessary to select the same file for each Cpu as the files you add to the list will be applied authomatically to all the O.S. or Cpu previously selected, so you need to open a path only to add th files names you wish. At the end you should get a list with Your .nsb program name, the files DialogX.ocx,MSCEfile.dll MSCEPicture.dll, Regsvrce.exe (Runtime Files directly added by the program) and all other Dll that you program can need added by you. As soon as all the requested files are listed click on NEXT.
The list of the selected files on the right remain unchanged while on the left some Files.Type will be shown. What you have to do here is to click on a file.type ( Files.Application for example), confirm the adding at the prompt (see image above) and by a mouse's click on the Files' list to associate a selected file name with the file.type ( in the example it may be Files.Application <- with .> 'YourProgram.nsb'). Dlls, ocx and regsvr,exe are commonly to associate to Files.Windows while Basic.exe must be associated with the files.NSbasic. For the shorcut associate the type with the program's name file. To associate multiple files'name you do not need to click any time on the file.type. Click instead sequantially on all the files'names only. ATTENTION: there is no error adjustment for this operation.This is the reason of the prompt to confirm the Files.Type to add. Anyway carefully click each files' name to avoid error. At the end of the association click on NEXT
click SEE CODE
The code of your .INF file just created will be listed in the program's window and you can also print it using the PRINT button below. To continue click again the 'see code' button now showing caption 'HIDE CODE'. This window shows the NEXT button disabled while there is a new button with the caption 'Create INF file'. Click on it to effectively create the YourProg.INF file (it wil be saved into INFactory Dir).
The shown window remain unchanged but the button caption quotes now 'Create CAB file' Click againt on the button and you will see start the black DOS window of Cabwiz.exe that will create your Cab file loading into the same all the files selected by you using the previuos steps. As soon as the DOS window hides you will see a new window with the same button showing the caption 'Create INI file'
This last window allows the user to choice which INI file(s) will be created. The Default type must be used with the SetUp.exe file to perform a common installation directly. The second type of INI file instead can be used to test the Cabs directly with AppMgr or to pass the file(s) with the relative Cabs to EZsetUp to create better installation packages. (the button below are still disabled in this Beta but will be available to authomatize the mentioned actions) Click 'Create INI file'. No new window will be shown but you will see in the instruction space at the bottom the word 'DONE !!' to inform you the end of the process. Well. Go now to see the folder 'C:\INFactory\CodeResult using explorer. You will see an image like the one below. The Cab files, the Setup.Ini and the Setup.exe file are the ones you need to assemble your installer. As you can see below the same files, if you Zip them will be about the 50 pct of their original dimension.
NOTE.: This is a working preview of the BETA program. It will be subject to others upgrade, so if you test it remember that : 'ANY FEEDBACK WILL BE GREATLY APPRECIATED' Upto now i tested the program on a Aero1550 Mips PPC and on a HP565 Arm PC2002 only. YOU MAY DOWNLOAD THE PROGRAM HERE but note that this version version has