Creating a stand-alone ins file and adding Dial-Up Connections

Creating a stand-alone ins file and adding Dial-Up Connections

Post by glenn.mant » Tue, 20 Jan 2004 20:40:08


I am trying to create an *.ins file to configure my unattened windows
xp build. I have used the profile manager to make the settings and
have selected to import the 3 dun connections i have on my machine.

When i save the ins file i copy over the cab to my iis server and make
usre the url for the cab files is the sames as specified inthe ins

however when i run the ins file on the mahine my dun setting are not
installed on the target machine.I have permission to access the cab
file from the url.

The cab file cotains a connect.ras file and the ins file has an entry
of importConnectionSettings(?)set to 1.

Any ideas

sorry for being vague


1. Is the stand-alone player TRULY stand ALONE?

2. Can Simulink create a stand-alone .EXE file?

My simulink model for the real-time embedded target is ready. I need
to make an exe file to download it to the board so that it can run,
but i dont want to do the "build-and-execute" thingy. I have most of
the relevant toolboxes, but no idea how to use them.

I looked on the internet but i found nothing specific and clear
pertaining to this board. Can anyone help me make some kind of exe
please, the target is the ti c6711, and the simulink model is an fir
filter which needs an input and output line during its runtime.


3. but if i want to create a stand-alone executable file(-)

4. Creating a stand-alone file

5. Create an Stand-Alone app from a GUI created in GUIDE

6. Can't open database connections after building stand-alone application

7. stand alone executable using pp doesn't stand alone

8. vb.NET stand alone .exe does NOT stand alone

9. Creating true stand-alone executables

10. PRoblems with creating Stand-Alone Applications

11. PRoblems with creating Stand-Alone Application

12. How to create stand-alone EXEUTABLE (*.exe) program?

13. ANN: Our solution to create stand-alone windows software

14. creating stand-alone extended tclsh

15. Tclapp in windows: How to wrap a custom interpreter to create a stand-alone executable