Ascii2

I want to automate Telnet commands. I was thinking of having it implemented via batch file. I want to emulate the procedure to set a mode via Telnet on a NETGEAR device with wireless radio. The procedure being emulated starts at item "10." on the following webpage: http://www.beatjunkie.de/Router_eng.htm Input to console from the keyboard would normally be the following (legend below): TELNET <CLIENT_IP_ADDRESS><ENTER>Gearguy<ENTER>Geardog<ENTER>wla<ENTER>set remoteAP <ROUTER MAC ADDRESS><ENTER>set oper sta<ENTER>..<ENTER>save<ENTER>reboot<ENTER> To understand the coded, the following legend of substitutions apply: <CLIENT_IP_ADDRESS>: IP Address of Wireless client being configured. <ROUTER MAC ADDRESS>: Router MAC Address. Contains colons and capital letters. <ENTER>: End of line character or "ENTER". How can the TELNET input be automated? EDIT: I think what I want implemented is done using the "echo" command with a pipe character ("|"), but I am not sure how it should be done.

It is "'coming from background to foreground'".

An Internet Explorer 6 with SP2 windows may come to front when working on something else (like typing a pot here for example). How can windows that are not at from be disallowed from coming to front on their own?

An associate of min has tried to send emails from Outlook 2007 (with SP2), but on attempt to send the messages, the messages got stuck in the Outbox. This happened on Windows Vista Home. I nor my associate not very familiar with Windows Vista or Outlook 2007. I have tried deleting the messages in Outbox and resending. Messages were only deleteable when Working Offline and resending cannot be done (messages get stuck again). What could be done to have Outlook 2007 send messages instead of retaining them in Outbox?

Rethinking about the problem after examing what the update is for, I have decided that the better solution is to remove the secdrv.sys driver/service (the service is hidden by default) from Windows XP with Service Pack 2. secdrv.sys is a third-party DRM driver, generally used to restrict use of games. DRM drivers for games has been reported to cause system instability. The commercial name of the secdrv.sys is "SafeDisc". It may be unwise to install the update patch and update the DRM (to SafeDisc V4.3.86); it would be best to completely remove SafeDisc from the system. More on SafeDisc: http://en.wikipedia.org/wiki/SafeDisc

It really is not so simple. The original file from the installation source should be deleted before starting the integration process. Otherwise, if deleting the file during the many patch integration process, there is a risk of not retaining versions of the secdrv.sys file newer than what is included in the defective patch.

So no Windows setup file has to be modified? Also, if an update patch is integrated into the installation source (and copy in SVCPACK directory), would the half-open connections patched TCPIP.SYS file be replaced (on Windows instance, not setup) with the update patch TCPIP.SYS?

How can half-open concurrent connections be increased in Windows XP Professional with Service Pack 2 without user intervention (unattended)? I have found patches and patched TCPIP.SYS files, but the concurrent connections do not seem to be applicable unattended.

From what I understand (please correct this if any information is incorrect), drivers and codecs must be 64-bit to function on Windows XP Professional x64 Edition. 32-bit software that are not drivers or codecs and compatible with Windows XP Professional may run on Windows XP Professional x64 Edition through emulation. Are theme styles for32-bit Windows XP and Windows Server 2003 (Luna, Windows Embedded Standard, Zune, Royale, Royale Noir, etc.) operating systems compatible with Windows XP Professional x64 Edition? Is there a software scanner or index that may be used to determine whether a software codec is 64-bit compatible?

I have examined the versions of QuickBooks and have determined that it does not truly require .NET Framework for the entire software suite(s). I did find that some things would use the .NET Framework (like QuickBooks database). I found it unusual that an application is designed to use .NET Framework, but not exclusively.

Your link appears to be defective. I am guessing you meant to refer to:http://www.netsetman.com/index.php?s=nsm I shall try NetSetMan 2.6.0. By "set my...printer", do you mean defining/installing a printer? It would be useful if the application could define printers for a user, but not for all users (Windows 2000/XP does not provide any easy way to do it).

I shall examine NET.EXE "USE" command.

I found no version of Microsoft .NET Framework installed on my computer.I attempted to remove files that may not have been cleaned up after an uninstall of .NET Framework using a cleanup tool found: http://www.raymond.cc/blog/archives/2008/1...r-cleanup-tool/ The tool produced a log. I have attached part of the the log. After cleaning for all versions of .NET Framework, I attempted to run QuickBooks 2005. QuickBooks 2005 ran without a problem. Would this indicate that QuickBooks 2005 really does not require .NET Framework installed? cleanup_main.zip

No. How is it that QuickBooks 2005 is able to run without Microsoft .NET Framework installed globally (Incorrectly specified system requirements?)?

Microsoft Corporation give the following description for "Common Language Runtime": Common Language Runtime seems to be related to Microsoft .NET Framework 1.1. The QuickBooks 2005 system requirements require: I have QuickBooks 2005 installed on and running on a computer with Windows XP Professional with Service Pack 1 without any apparent versions of .NET Framework installed. There is no item in Add or Remove Programs nor shortcuts to Microsoft .NET 1.1 configuration in "Administrative Tools" in Control Panel. Is Microsoft .NET Framework Common Language Runtime 1.1 installable without installing a .NET Framework to the system (globally)?

I would like to map, reconfigure, disconnect, backup, and restore network drives without using "Map Network Drive..." or "Disconnect Network Drive..." Windows dialogue boxes. An example of reconfiguration would be: changing the login information (username/password) used to connect the network drive. I would appreciate responses with methods or tools to map, reconfigure, disconnect, backup, and restore network drives. If the mapping, reconfiguring, disconnecting, backing up, and restoring can be also done unattended, I would like to know how. Any other comments, questions, etc. are welcome.

Thank you bacon_boy.I have tried the patch. I did not think the patch would work because I believed that after installation of the new "update.sys", System File Checker would replace (the patch did not come with a .CAT file). The patch updated "update.sys" without a problemand System File Checker did not revert "update.sys". It may be possible to get new cumulative security updates for Internet Explorer 6 with SP1 working on Windows XP with Service Pack 1 by using the Internet Explorer 6 with SP1 meant for Windows 2000 with Service Pack 4 (Windows 2000 with Service Pack 4 and Widows XP with Service Pack 1 use the same binaries and version for Internet Explorer 6 with SP1; official support for Windows XP with Service Pack 1 has been discontinued).

A Microsoft Knowledge Base article existed that had a link or information to download a patch for Windows 2000 family operating systems that contained a newer version of "update.sys", the Intel Microcode Update Device driver (driver used to load microcode into CPU, not system EEPROM), than what came with Windows 2000 Service Pack 4. I cannot seem to find the article with the information. I would appreciate assistance in determining where the article may be found.

I do not understand what dialog boxes are in color.Please clarify.

I tried an application converted from the AutoIT script posted by MHz above, and it failed to unhide the dialogue boxes. Perhaps the setup with the billboards is not the same setup without the billboard (this seems true of setup or mini-setup invoked by sysprep.exe); the dialogue boxes may not exist as dialogue boxes until [shift] + [F11] is sent.

The problem describe in the initial post to this thread is not uncommon. I often occurs due to the inability of NTLDR from operating systems with an NT version of 5.1 or greater to load greater than 16MB (most of which may be the SYSTEM registry hive) to boot the older NT-based operating systems. The problem is a defect of design of NTLDR from Windows XP and newer.

Windows XP Media Ceneter Edition and Windows XP Professional are almost the same product, differering only in the labeling of the product. The installation media meant for Windows XP Professional and Windows XP Media Center Edition differ, however. This I believe (but have not verified) is also true of Windows XP Tablet PC Edition. An installation disc intended for Windows XP Professional may be used to install Windows XP Media Center Edition. Also, if using the Windows XP Media Center Edition discs to install Windows XP Media Center Edition, only installing the first disc will install without media Center components. Installation media should be of OEM type.

This was also my conclusion. It would take a grossly inefficient program to casue a noticable slow down of setup. The page linked to is of interest. It shows what seems to be the only method of not showing the billboards for the entire GUI setup.The method of removing the use of the billboards during GUI setup shows the dialogue boxes centered both horizontally and vertically. Making the dialogue boxes hidden by the billboard visible by sending [shift] + [F11] results in the dialogue box visible aligned centered verticall, but not horizontally. Perhaps [shift] + [F11] invokes a repositioning of a dialogue box. Thanks, Given this information, I now intend to use versions of the setup with and without the billboards, but always displaying existing the dialogue boxes. Of interest is GrofLuigi's post here. GrofLuigi claims a "speeding up [of] the process" when billboards are removed. The process GrofLuigi was referring to, I believe to be the GUI part of setup. If my interpretation of his statement is correct and its significance valid, removing the billboards should reduce the time Windows setup takes to install Windows XP/Server 2003, all else equal. The modification to remove the billboards is, however, inconvenient for a frequently updated installation source when patch integration is performed. I shall schedule some time to try the script compiled to an application in a few days. Disabling of the billboard would have been a useful option for the WINNT.SIF answer file. EDIT: This post has been edited to fix a mispost. Not all words copied and pasted when copying and pasting text between a few applications (oddly).

Initial post has been updated with screenshots and text including and proceeded by "EDIT:".

Other entities than myself may derive a benefit. This is incorrect. I do not want to slow down the installation.I recognize that a slow down would occur (a cost) be believe it to be negligible (the slowdown would be the time to run a small program at from DetachedProgram and performing four unhiding operations). The benefit derived (answered below) is believed to greatly exceed the cost. The dialogue convey useful information. The dialogue boxes show progress of portions of the installation process and explain what the setup should be doing. The dialogue boxes also cover up the GUI setup advertisements that are not as useful. Microsoft Corporation would seek its own interest when deciding how it should act. Its interest is not necessarily what is good for the user (good example include Windows Product Activation, Windows Genuine Advantage, and requiring the input of a Product Key).I would speculate that the reason Microsoft Corporation set the dialogue boxes to run hidden is because it was less expensive and also would retained compatibility with processes of earlier NT-based Windows (like Windows 2000). To add a new Windows XP look to the GUI and advertise the product during setup, Microsoft simply set a background to cycle a new image (with advertisement) periodically and set the dialogue boxes to hidden because they would reduce the effectiveness of the advertisements. A mechanism was left to make visible the dialogue boxes (by sending [shift] + [F11]), but it is not so easily done unattended.