Lunchbox

Hello! I have discovered WPI recently! I've spend this evening looking through these forums for answers to questions, but didn't really find what I was looking for. Instead of writing an HTA from the ground up, I wanted to evaluate WPI first. Right now, I have these questions 1. I have some installers located on a network share, I would like WPI to run them. What would be the best way to go about either mapping a driver or otherwise "net use"ing to the share? Can I provide an interface for a user to enter credentials? 2. Is it possible to hide the config and options menus? What config options would I need to change? I don't want end users able to see or possibly change these menus. 3. I would like to explore the possibility of storing config files on the network, so that I don't have to actually touch my the disk image if I want to change what's getting installed when they come up. How would I go about this? Thank you very much! As I explore WPI, I am sure I will come up with more questions

This isn't exactly true in all situations. 32-bit applications that are LAA (large address aware) can address up to 4GB of memory on Windows x64. True, but there aren't many. Most apps compiled this way are server-type apps (like SQL Server or Exchange, for instance). I was trying to keep it simple . A lot of CAD applications are written that way. AutoCAD, Revit, 3DSMax, etc, etc. I deal with all of those on a regular basis

This isn't exactly true in all situations. 32-bit applications that are LAA (large address aware) can address up to 4GB of memory on Windows x64.