I've replaced the INI file that powers the download system, so you should now be able to get the packages you wanted. Apologies for the delay, it's been a busy week.
Mailbag
BoeserWest wrote:
I wrote a batch file witch starts the fp82.cmd. Now my Problem is, that i have much more code in my batch file. The code wouldnt run as log the fp82.cmd file open.Have you tried to use "Call c:\faatpush\fp82.cmd" in your batch file? That will run Fastpush from within your script and then return to the original script.
ken degel wrote:
after I deploy a few computers the xCmd.exe file in the /utils directory disappearsThat's a new one on me Ken! Have you tried making the xCMD.exe file read only? It may also be worth checking the script to ensure that there are no 'move' commands.
Darren King wrote:
But I am having issues pushing out the VNCConfig settings to prompt users to accept connections.Darren, these settings are likely to be kept in the VNC section of the registry. I think you could get this to work by configuring a client as you like it. Then, use REGDIR to dump out the settings to a new INI file. Have a look on the web site for information about exporting a configuration.
Roman wrote:
I just realized, that the script works as it should in german operation system versions, if you put in "mode con codepage select=1252" at the top of your scriptThanks for the tip, Roman. Would any German users like to road test that theory please?
Sigg3 wrote:
To get fastpush (and VNC) working on a default Windows XP Professional installation, I had to enable Internet Control Message Protocol.That's the first I've heard of that issue, but there are so many variations in XP installs that it doesn't surprise me. BTW, you can tell Fastpush to skip the ICMP test by using /NOPING.
Anton Tilstra wrote:
Hi! I've stumbled across what looks like a bug to me: when not updating shortcuts (shortcut=no), the XP Firewall Tweak gets bypassed regardless of its setting; this seems to be because the XP Firewall portion of the script is "embedded" inside the Shortcut section. I've moved it up to right above it (because it's easiest), which works, but logically it should come after, to stay consistent with the order of the rest of the script.Thanks for pointing that one out. I'll look into that when I come to do the next release. To be honest, I'm running out of features to add, but bug fixes would be a good idea.