You can find the first part of the instructions in the entry “Basic setup of toolstar®bootcast PXE environment”.
Copy the source files
First, create a directory called testLX or shredderLX in the same directory as the toolstar®bootCAST .EXE files. Then copy the program source files into this folder. You will receive the source files for toolstar®test and shredderLX from a previously created bootable, fully set up USB stick. Simply mark the entire contents of the USB stick and then copy it into the previously created folder.
Windows sharing setup
So that you have access to the actual program files after starting the operating system, you still need to create a simple Windows share. The process differs depending on whether you allow passwordless sharing in your company or not. An excellent guide to sharing resources on Windows can be found here: https://www.thomas-krenn.com/de/wiki/netzwerkfreigabe_unter_Windows_erstellen
Passwordless sharing is permitted
In the Network and Sharing Center, enable the option to allow shares to be valid without a username and password. Then release the testlx folder (see Copying the source files) with the name lxbootloc. Set the permissions to Everyone and Full Access for Read and Write.
Passwordless sharing is NOT permitted
Create a suitable local user or domain user, for example with the name bootcast, and also give it a password. You then have to enter the user name and password in the user.bootcast.mini file. Please make a temporary note of this information. Next, share the testlx folder (see Copying the source files) named lxbootloc. Set the permissions to the user you created and activate full access for reading and writing (depending on whether you want to allow the booted programs to write to the network directory).
Setting up the user.bootcast.mini file
Next you need to create/edit a bootset in the user.bootcast.mini file. To do this, please open the file with a text editor and change the following entries:
- Under the point [fab.config] with the line start [“[[ROOT_PATH]]
Please enter the name of the release here. If you used the standard name lxbootloc, then this is already entered. - Under the point [fab.config] with the line start [“[[ROOT_USER]]
Depending on whether you have activated passwordless sharing or not, you will either have to enter a user name (“USER_NAME”) or nothing (“”) here. - Under the point [fab.config] with the line start [„[[ROOT_PASS]]
Depending on whether you have activated passwordless sharing or not, you will either have to enter a user name (“PASSWORD”) or nothing (“”) here.
Apply a toolstar®test or shredderLX update
To replace the files on the PXE server with new ones, please proceed as follows:
- Request the current files at licinger.de.
- Depending on which update type this is, download either just the program package or the program package including the stick image and the image writer. If you are not sure, it is best to always download all files and create the stick from scratch.
- Create a bootable USB stick as described in the customer portal instructions.
- Delete all files from the [BOOTCAST_ROOT]\testlx directory
- Copy all files from the stick to the [BOOTCAST_ROOT]\testlx directory
Please note that there may be personal files in the [BOOTCAST_ROOT]\testlx directory. You should save this before step 4 and copy it again to the same location after step 5.
Known issues and solutions
- Messages related to DHCP discover and missing IP addresses
Make sure you have a correctly configured DHCP server on the network or have bootCAST's DHCP server enabled (see instructions here). - Error message at startup: Mount error: Bad option -ouser
If you receive this message, then there is no access to the Windows® share. Please check the Windows® sharing settings as well as the users and passwords stored in user.bootcast.mini. - Error when saving reports within toolstar®test and shredderLX
If you receive an error message when saving within the program, the Windows® share may not be set to write. Please check the permissions of the Windows® share. Under certain circumstances, this behavior is also desired so that a user cannot modify options and endurance tests.
