Buy Now
What's New
Data Recovery
DVD Burners
Reseller Application
Purchasing FAQ
Product FAQ
Bug Reports

Portlock Boot Wizardô Frequently Asked Questions

Q) What is the purpose of the Portlock Boot Wizardô?

A) The Portlock Boot Wizardô has several purposes:

  • Create a TCP/IP boot diskette preconfigured for a particular network adapter for Portlock Storage Managerô.
    • Portlock Storage Manager supports TCP/IP communication for remote control, Server-to-Server Migration, Image Creation and Image Restoration. The process of creating the TCP/IP Boot Diskette is complicated, requiring knowledge about the Novell Client32 files, NetWare LAN drivers, etc. By automating this procedure, customers will have a better experience with Portlock products.
  • Create a Portlock Storage Managerô diskette with the correct files for execution under DOS.
    • Portlock Storage Manager executes on NetWare as an NLM (NetWare Loadable Module) or on DOS. Determining which files to copy to a diskette is not intuitive and requires consulting the user guide.
  • Create a Bootable Image File to be downloaded as part of the PXE boot process.
    • Most computers and servers manufactured since 1998 have the ability to boot from the network using the PXE (Preboot Execution Environment) and TFTP (Trivial FTP Protocol). Portlock Boot Wizardô can create image files that can then be downloaded and executed by a remote computer. Future Portlock products, including Portlock Boot Serverô and Portlock Consoleô, will support full remote booting / control of computer systems.

Q) What does the Portlock Boot Wizardô cost?

A) Nothing. It is a no cost download from Portlock Software.

Portlock Boot Wizardô is a copyrighted software product. You may not distribute Portlock Boot Wizardô to others without prior written agreement from Portlock Software.

Q) What are the system requirements to install Portlock Boot Wizardô?

A) Portlock Boot Wizardô can be installed on Windows 98 / NT / ME / 2000 / XP / 2003.

Q) Why doesn't the Portlock Boot Wizard include MS-DOS?

A) MS-DOS is a copyrighted Microsoft product that would require royalties. Portlock Boot Wizardô includes an automated method of loading and saving the DOS files for creating bootable diskettes and image files.

Q) What is the best version of DOS to use?

A) MS-DOS is no longer being developed by Microsoft. The most compatible version of DOS is Microsoft's MS-DOS. Portlock recommends using the version of MS-DOS from Windows 98 Second Edition. Portlock Boot Wizardô also supports creating bootable diskettes and image files with IBM's PC-DOS and DR-DOS.

Q) Why is HIMEM.SYS required?

A) HIMEM.SYS, which is a memory manager, is not required for all Portlock Boot Wizardô operations.

  • The Novell Client32 TCP/IP stack requires a memory manager.
  • Portlock Storage Manager does not require a memory manager.
    • Portlock Storage Manager has its own built-in memory manager and we do not recommend loading HIMEM.SYS from CONFIG.SYS for Portlock Storage Managerô, as this will limit the amount of physical memory that can be accessed.

Q) What is PCISCAN?

A) PCISCAN.EXE and PCISCAN.NLM are software tools that scan the system's PCI bus, recording the PCI devices that it finds. These tools can be used on any DOS or NetWare system to determine which network adapters are installed. By creating a file 'PCISCAN.DAT', Portlock Boot Wizardô can load this file and then determine the network adapter to use.

Q) What is PCISCAN.SYS and why does Portlock Boot Wizardô recommend using it?

A) The PCISCAN.SYS is a Windows device driver for Windows NT / 2000 / XP / 2003 that supports directly accessing the PCI bus on Windows-based systems. If this device driver is not installed, then Portlock Boot Wizardô will attempt to determine the PCI devices from the Windows registry. Windows NT does not keep PCI device information in its registry, so this driver is required if the Portlock Boot Wizardô is installed on Windows NT.

Q) How does Portlock Boot Wizardô scan other computer systems?

A) Portlock Boot Wizard uses various methods depending on the target operating system.

Note: You may be required to login or authenticate with a remote computer system.

  • DOS: Remote scanning is not supported.
    • Create a PCISCAN diskette, execute PCISCAN from DOS and then load PCISCAN.DAT PCI device information with Portlock Boot Wizard.
  • Windows 95: Remote scanning is not supported.
    • Create a PCISCAN diskette, execute PCISCAN from DOS and then load PCISCAN.DAT PCI device information with Portlock Boot Wizardô.
  • Windows NT: Remote scanning is not supported.
  • Windows 98 / ME / 2000 / XP / 2003: Portlock Boot Wizardô uses the Remote Registry Service to access the PCI device information stored in the Window's registry.
  • NetWare 3.x: Remote scanning is only supported if the NLM portlock.nlm is loaded manually.
  • NetWare 4.x thru 6.5: Portlock Boot Wizardô uses NCP (Novell Core Protocols) to install and execute the Portlock NLM (portlock.nlm) on the target NetWare server. Then using NCP, a request is made to portlock.nlm to scan the PCI bus and return the PCI devices found. Once the scan is complete, portlock.nlm is unloaded.

Q) How do I modify an Image File once I have created it?

A) Use the Portlock Boot Editorô to create / manage / modify image files.

Q) How do I boot a remote machine using an image file that I have created?

A) Use the Portlock Boot Serverô to manage booting remote machines. The Portlock Boot Serverô supports PXE and TFTP protocols embedded in most modern computer systems.

Note: You may need to enable PXE boot capabilities on each Workstation / Server in their BIOS setup.

Portlock Software is a trademark of Portlock Software. 
All other products mentioned are registered trademarks or trademarks of their respective companies.
Contact sales sales@portlock.com T: 406-723-5200 - F: 406-723-5205
Contact support support@portlock.com T: 406-723-5200 - F: 406-723-5205
Questions or problems regarding this web site should be directed to our Web Master.
Copyright © 2000 - 2006 Portlock Software. All rights reserved.
Last modified: Tuesday March 14, 2006.