The
reasons of the upgrade
The
reasons of the upgrade
When i started to develop Infactory Wizard there were 2 reasons to justify
this programming work.
First, NSBasic CE language did not use an easy procedure to create its
own installers. Second, i needed an easy way to create installer packages
for my programs (usually standalone) plus the NSB runtime.
INFactoryW was exactly what i needed allowing me (and users) to create
an installer by three mouse's click only.
Many developers need something as above but there are others also that
need to install, at the same time, not only a standalone .nsb file but also
images, sound, help or text files etc.
So INFactoryW has been upgraded to INFactoryW Plus
Program's specification
The basic rules remain unchanged
1) Program must be little and to use no additional dll if possible so to enable to
install, delete or update it quickly by few click of mouse.(actually 88Kb)
2) Nothing must be written or changed in the user's system enabling anybody to
use or try the program without problems.(unistall simply deleting added files/folders)
3) The user need to know few informations to use the program. No INF files' sintax
or other knowledgement required to get the final result exactly as required.
Trying to respect the above points the new program adds:
1) Fully compatible with the previous version using Wizard option.If you do not need
the new features you can use program as the old INFactoryW.
2) More flexibility. User can add to the installation any type of file selecting the option
Advanced and simply copying files' extentions in the relative input's boxes.
3) Files usually loaded into Application and Windows folder but user can add a third
target dir if he needs. (Documents, Storage Card etc)
4) The default Application install folder is 'My Programs' but user can select and change
it if necessary.
5) The program include a simple single line Registry editor (use if advanced programmer
only to avoid trouble on your device)
6) Before creating installer user can select the output result that may be a set of files to
be joined in a zip file to unzip and use with the enclosed SetUp file.
Otherwise user can select the ezsetup output that configure the file to use them with
ezsetup program.
7) If the above 2nd option has been selected and user works on a Win2000 or more O.S.
a new button will open an windows interface to ezsetup program and will allow to
get directly a more professional compressed exe file as installer result.
8) An included Help (or this page if any) will drive you step by step to use program.
9) Remain unchanged the possibility to add all Runtime files by a simgle click and in the
same way to add a shorcut with NSB icon and program name.
System Requirement
Win 98/ME/NT/2000 with VB6.0 Runtime installed (tested on Win98/2000 only)
Cabwiz file (usually available with PocketPc SDK or in the NSBasic CD)
All the DLL/OCX that your program uses must be duly stored into the relative Sys/Cpu folders
that unzipped INFactory program will create in your HD.
ezsetup into the FileResult folder if you use Win2000/NT
YOU MAY DOWNLOAD THE PROGRAM HERE but note that this version version has
been discontinued owing to the issuance of the new INFactoryW2003 version.
PROGRAM's tour STEP by STEP
Copy Cabwiz.exe in the Infactory folder, copy all Cpu dependent files (Dll/Ocx )
that your program uses into the correct subfolders ( If you wish to create multi
Cab installer you must have the same set of files in any subfolder).
If you will include in the installer the NSB Runtime the relative files also must
stored into each OS_Cpu folder that will be used.
The above actions must be performed the first time and only one time.
You may now copy your .nsb program's file and all the other additional files,
as images,sounds,texts,data archive etc into the applicationfile folder.
Run INFactortW+ and you will see the new starting page :
It looks like the previous program except for the following two items
if you use the default 'Wizard' option (use this if your pogram is a standalone item
only) and you fill all input text boxes as requested, when you click on 'Next' button
you will see the following page showing the Next caption changed in 'Done'
(Take note of the ALL in the CPU ComboBox that allows the program to
choice the Cpu used by PocketPC authomatically)
Clicking on the Create Cab, thence the same command showing Create INI you will get
the files of the installer as happens with the old version.
If you use instead the option 'Advanced' and you fill the relative input text
boxes you will see the window below
Note that now the Device Default Directory name is customizable, so to load your program
into its own folder you have to add your " \program's name" or what you like after the
default \Program Files.(suggested to create application Dir's subfolder also)
* Attention Read this note to create PocketPC2003 installers
if this is not your case go over otherwise read details
As you can note the first window of the program show a check box that in the previous version
of INFactoryW+ was by default disabled.
The current version now can use this box, if checked, to add to your installer project the files
that you need to run an NSBasic application under the new Microsoft operating system that
now support eVB only if manually added.
The installer so created (you must check the option to add NSB runtime also) will install your
program and will enable your device to run it in a single step. To do the job you must add to the
INFactoryW+ Subdir PocketPC_ARM the following files:vbscript.dll,pvbhost2.dll,pvbform2.dll,
Pvbload.exe,Pvbdecl.dll,Pvbctrl.exe,Pvbkill.exe
If you installed new NSBasic or Runtime you should find these files in your device otherwise you
can download the new MSVB runtime and use the files therein.
This files will be authomatically added during the installer creation so you have nothing to do
except to remember to not use the AllDevices and ALL options for O.S. and Cpu and to select
only PocketPC and Arm option.
This will create a single Cab installer only. A new full featured upgrade will be posted later.
Take note that i tested this version of Infactory loading and running a program of mine on my
new H2210 tha surely does not include any eVB items but for the moment this is the only
test executed as i have no other 2003 devices.So this last upgraded version is Twice a BETA!!
Click NEXT and you will see the following window
This page is the real main console of the program's new features.
Starting from the top you find a line of Text boxes as shown here
The A and W labels means respectively ''Application'' and ''Windows''
folders and all the files with the quoted extentions in the following text
boxes will be by default loaded in the relative device folders.
In namy cases these settings do not require any change.
If some files used by your program have extention not mentioned here you
may cancel and substitute it as you like and you can also move an extention
type from A to W if necessary.
In the event that you have to load some files (by extention) into a different
folder you can use the ? label. Click on it to show a combobox where you
can select a new third folder.
You may now: 1st Select one of the listed folder in the combobox
(the selected files will be loaded into that folder)
2nd Write your customized folder name
(the folder will be created and files loaded therein)
3rd Select the Device Installation Dir and add to the path
a new folder name
(a subfolder under Installion Dir will be created and there
will be loaded the files with wanted extention)
Thence you can write into the blank text boxes on top the required extention(s).
Note that it is not allowed to show the same extention in two folders at the
same time so you have to cancel the old one to move it with the following
result
You can not modify the yellow back boxes that show default extentions.
Under the above set of boxes you can see the following list boxes
The list on the left shows, using the above buttons, the programs additional files
(if you modified some type of extention use the Other File button to refresh the
list) and the system files whose name is the same for all CPU you may use.
(Will be the program to choice the right ones).
Click a file's name, confirm in the prompt window and you will see the file with its
full path added to your program's files' list on the right.
(To cancel a file erroneously added click on it and confirn to delete).
When this last list will contain all the files your program needs click NEXT again.
The window shown will not change but you will see each of the added prorgram's
files marked by <-+.
If all listed files are duly marked this means that each file has been correctly linked
to its destination folder shown on the left, so click again the NEXT button.
You will see now the following windows:
On the top of the window you will find a single line registry editor that allows you
to add customized keys if your program needs them. I suggest the use to advance
programmer only because a wrong keys may hang your user device, so be carefully
Below you see two option button that you can use to select the output type.
The default will give you a set of files and relative .ini file that you have to use with
the SetUp file that you find into the INFactory\FileResult\ folder.
The second option instead will create the same set of files but an .ini constructed to
be used with ezsetup.exe to get a compressed selfinstalling .exe file.
Make your choice and press NEXT for the last time.
At this point you can also see the full INF code text using the button on right top
captioned 'See Code'. To close the view you may click same button again or if
you wish to PRINT the code use the relative command at the left bottom corner
While the INF text is shown.
The listing of the code will look as follows:
Under the command button showing the 'DONE' caption you will see now a new
button labelled 'Create Cab File'. Click on it
You will see one or more DOS windows which will confirm you that Cabwiz is
working correctly and, at the end, the NEXT button caption will show ' DONE '
Click again and the sets of files you need will be available into
the FileResult folder.
If you selected the INI default option or, anyway, you are running INFactoryW+ under
Win98 O.S you will come back to the starting window to Exit from the program.
If you selected the Ezsetup instead and you are running the program on Win2k
the last program's window will be visible and a new command with the label
'Call ezsetup' will be available. Click on it and you will get a little panel that will
allow you to select the User.text file and the Eula.txt file that will be handled by
ezsetup program. ( you must store previously these files into the FileResult
folder to allow ezsetup to create authomatically the exe installer.
No matter which is the name but use Text format only).
The panel has a command button with caption 'Create EXE file'. Click on it.
You will see a minimized icon of a Dos session and when the same hides,
in the above mentioned directory, you will find the final EXE installer along
with all the other files (INI, CAB) used to create the file .exe.
And this is all.
More informations can be found in the program's help file.
Follows.....
