PnP

Plug and Play

Collection

zero Useful+1

zero

This entry is made by Compilation and application of scientific encyclopedia entries of "Science Popularization China" to examine.

PnP， The full name is Plug and Play, which is translated as Plug and Play.

PnP is used to automatically configure lower layers computer In card And other devices, and then tell the corresponding devices what they have done. PnP's task is to Physical devices And software Device Driver And operate the device to establish a communication channel between each device and its driver. Then, PnP allocates the following resources to devices and hardware: I/O address 、 IRQ 、 DMA channel And memory segments.

Chinese name: Plug and Play
Foreign name: Plug-and-Play

Abbreviation: PnP
Presenter: Microsoft
Role: Automatic configuration (bottom layer)

catalog

one definition
two analysis
three origin

▪ Solution
▪ Manual programming

definition

Announce

edit

PNP is created by Microsoft It means that the system automatically detects peripheral devices and boards and automatically installs them Device Driver . It can be plugged in and used without manual intervention. It is a built-in technology of Windows. Plug and play refers to the automatic setting of the operating system when peripheral devices such as PC card conforming to the PNP standard are installed on the computer System structure Technology. When users install new hardware, they do not need to set any Jumper It is also unnecessary to use software configuration Interrupt request (IRQ)、 Memory address or Direct memory access (DMA) channel, Windows will notify applications of new changes in hardware devices, and will automatically coordinate IRQ, memory address and DMA channel Conflict between.

analysis

Announce

edit

Before PnP technology appeared, interrupt and I/O port The allocation of is done manually. For example, if you want this sound card to occupy interrupt 5, you need to find a small Jumper Insert the pin marked Interrupt 5 on the card. Such operations require users to know about interrupts and I/O ports, and be able to assign interrupt addresses without conflict. It is unrealistic for ordinary users to put forward such requirements.

PnP technology is used to solve this problem. PnP technology will automatically find a non conflicting interrupt and I/O address to assign peripheral , without human intervention. Today, when interrupt resources are very tight, even with PnP technology, you may not be able to find a suitable interrupt to assign to the device you just inserted. Therefore, it is very helpful to release unnecessary interrupts as far as possible for PnP to work normally.

Some PnP conflicts originate from the design of the motherboard. Many mainboards have an AGP slot , five PCI slot And two ISA slots, of which AGP slot Generally, it shares an interrupt with a PCI slot, that is, the interrupts of the two slots can be any reasonable value, but must be the same. When you insert a display card in the AGP slot, if you insert a sound card in the PCI slot with the same interrupt, it will definitely generate Interruption conflict 。 For most motherboards with five PCI slots, the first and fifth slots share interrupts with the AGP slot, and the fourth slot shares interrupts with the USB slot. Although you can force interrupts to be assigned to each PCI slot in BIOS settings, this is a difficult task for most users. Moreover, since the second and third slots do not share interrupts with other devices, In most cases, the graphics card is inserted in the AGP slot, and the sound card and other PCI cards, such as the network card, should be inserted in the second and third PCI slots, that is, the second and third PCI slots from the AGP slot to the ISA slot. In this way, these cards can work normally without changing the PnP settings in the BIOS.^[1]

origin

Announce

edit

For many PC users, if you need to add some new functions to your PC, such as listening to CDs, watching VCDs, sending and receiving faxes, etc., you need to add some new devices to your PC, such as sound cards CD-ROM MPEG hardware Unzip card , FAX/MODEM fax card and a series of new equipment. Generally speaking, the process of installing new equipment is as follows:

1. Set the switch and Jumper 。

2. Correctly insert the new device into the motherboard expansion slot as required.

3. Install the Driver 。

4. Reboot the system.

Then, you may have to spend a lot of time and energy to deal with various problems in the installation process. For example, manually change the switch or jumper of the equipment to track CONFIG. SYS file to resolve internal Resident program Conflicts, etc. The reason is that a PC has at least one or more bus devices (BUSDEVICE), and multiple bus devices may share the same system bus (SYSTEMBUS), which inevitably leads to hardware resource conflicts. The lesser one is that the newly installed equipment cannot be used or the system cannot be started. In serious cases, the system will crash. How to solve this problem? It is hoped that the system can provide information about the underlying hardware resources, including IRQ（ Interrupt request ）The intelligent management capability of I/O ports, DMA channels, and content, etc., eliminates the user's troubles caused by installing new hardware devices.

With the introduction of WINDOWS95/98, Microsoft also publicized the intelligent management capability of the underlying hardware resources provided by WINDOWS95/98 for users, that is, WINDOWS95/98 has the function of Plug and Play (PNP: PlugandPlay), so plug and play is widely valued.

Plug and play has been put forward for a long time, and its standards start from several Dongting Lake Solution to PC hardware configuration problems, including IBM's microchannel bus and COMPAQ's EISA (Extended Standard Industry system bus ）Unremitting efforts.

It was only in 1991 that MICROSOFT formulated the plug and play specification, which prompted MICROSOFT to develop plug and play. In its advertisement, APPLE claimed that MICROSOFTWINDOWS system was not as easy to configure and use as APPLE's MACOS operating system, It is simple to modify the system settings on Apple's MACINTOSH microcomputer to just insert or pull out the expansion card, and the machine can work well under its SYSTEM series operating system, thus eliminating the need to set switches Jumper Or the trouble of allocating system resources can be said to be the complete plug and play at this stage. Although the legend belongs to the legend, in the final analysis, the reason is that the progress of technology makes MICROSOFT want to monopolize the operating system of personal PC.

To make the system a leap in ease of use, it must solve the problem of sharing multiple bus devices system bus The allocation and reallocation of the underlying resources of the system caused by the. The alliance of MICROSOFT with INTEL and COMPAQ prompted it to praise the Plug and Play specification one after another after 1993, including other bus types such as ISA, EISA, PCMCIA, PCI, VESA and SCSI. However, at this stage, the full sense of Plug and Play may take some time to further improve.

MICROSOFT has started to try some tests on equipment detection and configuration on WINDOWSFORWORKGROUPS and WINDOWSNT. In WINDOWSFORWORKGROUPS, the operating system can automatically detect the video adapter , mouse, keyboard and Network adapter card Type of, etc. WINDOWSNT goes a step further. It can detect SCSI devices and other hardware. When WINDOWS95/98 arrives, it can almost automatically install and dynamically reconfigure the system.

Although it is impossible for WINDOWS95 to correctly identify all the old devices, and even sometimes turn to users, plug and play itself is a real leap. The current WIDNOWS 98/2000 has further developed in PNP.

evaluate

Announce

edit

Plug and Play is an industrial standard used to automatically handle the installation of PC hardware equipment, which is jointly developed by Intel and Microsoft. Generally, when you need to install new hardware, you should always consider the DMA and IRQ resources used by the device to avoid conflicts between devices due to competition, or even cause the machine to fail to work properly.

With "Plug and Play" (PnP), the installation of hardware devices is greatly simplified, and you don't need to do it again Jumper , it is not necessary to use software configuration However, the new hardware you install must comply with the PnP specification, or it will not work.

Plug and play represents the main progress of current interface technology. But it is not a new concept. It is a key feature of the interface design between MCA and EISA, but the limited attraction of MCA and EISA has not made it an industry standard. Therefore, mainstream PC users still worry about the settings of I/O address, DMA channel and IRQ. Early PCI based systems also used a PnP configuration method, but many users are still worried about some configuration problems because they did not provide management measures for conflicts between PCI cards and ISA cards. However, the current Plug and Play specification can be used in systems based on ISA, PCI, SCSI, IDE and PCMCIA, and buyers of all new computers no longer need to worry about hardware settings.

parts

Announce

edit

In order for Plug and Play to work properly, the following components are required:

·Plug and play hardware.

·Plug and Play BIOS.

·Plug and Play operating system.

These components are required to be plug and play compatible, which means they should obey the plug and play specification.

1. Hardware components

Hardware components include computer system and adapter 。 This does not mean that older ISA adapter cards cannot be used in Plug and Play systems. You can use these cards. In fact, the Plug and Play BIOS automatically reassigns the settings of the Plug and Play compatible cards around the existing legacy components. In addition, many later ISA cards can also be switched to Plug and Play mode. The Plug and Play adapter card communicates with the system BIOS and the operating system to disseminate information about the required system resources. Then, the BIOS and the operating system resolve the conflict (if any) and notify the adapter which specific resources should be used. The adapter changes its own configuration to use specific resources.

2. BIOS components

BIOS components mean that most users of older PCs need to upgrade their BIOS, or purchase new machines with PnP BIOS. To be compatible, BIOS must support 13 additional system function calls, which can be used by the operating system components of the Plug and Play system. The PnP BIOS specification was jointly developed by Compaq, Intel and Phoenix Technologies.

The PnP feature of BIOS is implemented through an extended POST. BIOS is responsible for identifying, isolating and configuring PnP adapter 。 The BIOS implements these tasks through the following steps:

1. Disable all devices configured on the motherboard and adapter card.

2. Identify all PnP PCI or ISA devices.

3. Generate an initial resource allocation diagram for ports, IRQ, DMA and memory.

4. Enable I/O device 。

5. Scan the ROM of ISA device.

6. Configure the initial manned program equipment for later system startup.

7. Enable configurable devices by notifying which resources are allocated.

8. Start loading the startup program.

9. Transfer control to the operating system.

3. Operating system components

Operating system components can be implemented by most new systems, such as Windows 9x/Me/2000/XP. Sometimes, system vendors provide extensions to the operating system for their designated hardware, especially in notebook systems. If required by the system, ensure that these extensions have been installed in the system.

It is the responsibility of the operating system to notify the user of conflicts that cannot be resolved by the BIOS. Depending on the experience of using the operating system, users can manually set conflicting cards, or turn off the system and set switches on the cards. When the system restarts, the system detects the remaining (or new) conflicts, which prompt the user to pay attention. Through this process, all system conflicts can be resolved.

Technical issues

Check whether the system has detected the network card

Enter system properties and click Device Manager Check whether there is a "PCI Ethernet Controller" in the list of unknown devices. If there is no PCI Ethernet Controller, it means that WIN98 has not detected your network card. The network card may not be installed correctly or has been damaged. The unknown device in the list is a network card that has not been driven but is not displayed under normal conditions.

Save the registry key of the existing network card

Click Start, select Run, enter regedit, and enter Registry Editor , find the following primary key

[HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10]

Export it as a file PCI8139.REG

Replace network card driver

Find the driver of the RTL8139 network card of the previous version of WIN95A, copy the RTL8139.SYS to the WIN98 directory on the network card disk, and overwrite the RTL8139 network card driver of the existing NDIS5.

Install the replaced network card driver

Install the replaced network card driver in the normal way, and still use the WIN98 directory on the network card disk. After installation, add other network protocols such as IPX. However, it is recommended not to install those network protocols that cannot be used at all, such as NETBETUI, MS DLC. If these protocols are not necessary, they will affect the network speed. After installation, restart the computer.

Modify Registry Key

Run Regedit to enter Registry Editor , find the following square key

[HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10]

Export it and save it as PNP8139.REG, edit the PNP8139.REG file, replace PCI, VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10 and BUS_00&DEV_08&FUNC_00 in the primary key with ROOT, NET and 0000 respectively, and replace PCI VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10 BUS_00&DEV_08&FUNC_00 LogConfig]

The key value is deleted and saved. The following is the content of the sample file before and after modification

PNP8139.REG before modification

REGEDIT4

[HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10]

[HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\BUS_00&DEV_08&FUNC_00]

"Capabilities"=hex:14,00,00,00

"HardwareID"="PCI\\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10,PCI\\VEN_10EC&DEV_8139&SUBSYS_813910EC,PCI\\VEN_10EC&DEV_8139&REV_10&CC_0200,PCI\\VEN_10EC&DEV_8139&CC_020000,PCI\\VEN_10EC&DEV_8139&CC_0200"

"CompatibleIDs"="PCI\\VEN_10EC&DEV_8139&REV_10,PCI\\VEN_10EC&DEV_8139,PCI\\VEN_10EC&CC_020000,PCI\\VEN_10EC&CC_0200,PCI\\VEN_10EC,PCI\\CC_020000,PCI\\CC_0200,PCI\\VEN_10EC&DEV_8139&SUBSYS_813910EC""DeviceDesc"="Realtek RTL8139(A/B/C/8130) PCI Fast Ethernet NIC"

"HWRevision"="016"

"Class"="Net"

"ConfigFlags"=hex:10,00,00,00

"ClassGUID"=""

"Driver"="Net\\0000"

"Mfg"="Realtek"

[HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\BUS_00&DEV_08&FUNC_00\LogConfig]

"0000"=hex:00,04,00,00,00,30,00,00,10,00,00,00,04,00,00,00,03,00,00,00,ff,ff,\

00,00,30,00,00,00,01,00,00,00,01,00,14,00,00,00,80, d4,ff,00,80,d4,01,00,00,\

00,00, ff,ff,ff,00,01,00,00,00,00,00,00,ff,ff,ff,ff,01,00,00,00,14,00,00,00,\

24,00,00,00,02,00,00,00,01,00,0c,00,00, e8,ff,e8,00,00,ff,00,00,ff,00,01,00,\

00, ff,ff,00,00,ff,00,10,00,00,00,30,00,00,00,01,00,00,00,01,00,14,00,00,c0,\

0c,00, ff,5f,0d,00,00,00,00,00,ff,ff,ff,ff,00,a0,00,00,00,c0,0c,00,ff,5f,0d,\

00,00,00,00,00, ff,00,00,00,00,00,00,00

[HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\BUS_00&DEV_08&FUNC_00\Bindings]

"NWLINK\\0000"=""

"MSTCP\\0000"=""

Revised PNP8139.REG

REGEDIT4

[HKEY_LOCAL_MACHINE\Enum\ROOT\NET]

[HKEY_LOCAL_MACHINE\Enum\ROOT\NET\0000]

"Capabilities"=hex:14,00,00,00

"CompatibleIDs"="PCI\\VEN_10EC&DEV_8139&REV_10,PCI\\VEN_10EC&DEV_8139,PCI\\VEN_10EC&CC_020000,PCI\\VEN_10EC&CC_0200,PCI\\VEN_10EC,PCI\\CC_020000,PCI\\CC_0200,PCI\\VEN_10EC&DEV_8139&SUBSYS_813910EC"

"HWRevision"="016"

"Class"="Net"

"ConfigFlags"=hex:10,00,00,00

"ClassGUID"=""

"Driver"="Net\\0000"

"Mfg"="Realtek"

[HKEY_LOCAL_MACHINE\Enum\ROOT\NET\0000\Bindings]

"NWLINK\\0000"=""

"MSTCP\\0000"=""

Import network card registration item

Import the PNP8139.REG file and delete the original network card registration key in the registry

[HKEY_LOCAL_MACHINE\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10]

At the same time, import the PCI8139.REG file. The purpose of importing this file is to stop viewing the network card as a new PNP device when Windows starts up, and to stop looking for the device as an existing unknown device Driver , so, in Diskless When starting, there will be no network interruption due to driver update; The previously imported PNP8139.REG file has no interrupt information. Our goal is to let Windows drive the network card as a non PNP device. Next time Windows finds the same hardware device, but the interrupt information is different, it can use the device as a non PNP device, call the existing driver, and force the device to drive, When a new driver cannot be found, the existing driver will not be updated, so that on any available slot on any motherboard, WINDOWS can force this network card to drive, so that the diskless WIN98 can plug and play this network card. When the motherboard or slot is changed, the error such as "Can't Find Krnl386. exe" will not appear, and the GUI interface of WINDOWS cannot be accessed.

Clear the drive information of the existing network card

The driver information about RTL8139 in the WIN98 system directory in the registry can be found Network card driver The information search path is cleared and the system is restarted.

So far, this hard disk system has forcibly driven the network card in any available PCI slot of any motherboard, and connected to the network normally.

The PNP system that can drive local hard disks has been installed in the previous section. The following is to upload local files to the file server with the help of Litenet upload work

1. Modify AUTOEXEC BAT file, whose contents are as follows

@EHCO OFF

SET WINDIR=C:\WINDOWS ； Set the directory where WINDOWS is located

SET DRIVE=C: ； Set the location of WINDOWS Driver

SET NETCARD=RTSND.DOS ； Set the network card driver in real mode

SET SERVER=LEITHER ； set up File server NETBIOS name of

SET SHARE=PNP98 ； Set the upload target directory, that is, the shared WINDOWS directory

2. Create and import SNAPSOT REG file, and copy SNASHOT, VXD file

The following is SNAPSHOT REG content

REGEDIT4

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\SNAPSHOT]

"NetClean"=hex:01

"Start"=hex:00

"StaticVxD"="SNAPSHOT.VXD"

Establish SNAPSOT REG file can be imported into the registry, and then SNAPSHOT The VXD file is copied to the C: WINDOWS SYSTEM directory.

3. Create Litenet.reg file as follows

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Qualystem\LiteNET PC]

"Step"="2"

"Version"="1.15"

Import Litenet.reg file. This step is mainly for normal use of Litenet upload tool, because QSYNCH When EXE is running, it is necessary to determine whether Litenet has been installed in the system. Importing this file can trick QSYNCH EXE， Make it not awkward.

4. Copy the files used by Litenet to the WINDOWS directory, restart the system, and run Qsynch.exe to upload the local files.

5. Use WIN95A Driver RTL8139.SYS replaces RTL8139.SYS in Litenet software.

If you have been here successfully, congratulations. Your client's WIN98 has been installed. With the existing startup package, you can start the real PNP diskless WIN98. You can install drivers for video cards and sound cards without disks!

Solution

Litenet automatically generates a startup for the user floppy disk , use this floppy disk to generate a boot image before starting in PXE mode Diskless WIN98， Because the startup package needs to be copied every time during startup system registry , and will Secondary login , so it is reduced Starting speed In this section, we will introduce how to, quick start The diskless WIN98, how to make it automatically identify and install various PNP hardware, and the solutions to common problems.

1、 Modify existing startup package

Delete unnecessary files

During the startup process of Litenet generation, you will be asked to insert the WIN98 The second version of the CD will write a file to the floppy disk. In the startup package, these files can only be used by some programs of Litenet. If Litenet is not currently used, these files can also be removed. These files are:

KEYBCOM,KEYBOARD.SYS,KEYBRD2.SYS,SETVARS.BAT,TUNING.BAT

Some Litenet's Executable It can also be deleted. These documents are:

QAUTOLOG.EXE,QUALCNX.EXE,QUALREG.EXE

Add and replace some documents

Some Litenet files have been removed and some files we need have been added accordingly. There is only one file: SETMDIR EXE, This file can Diskless Found in the startup package of WIN95, and then used WIN95A Driver Replace the existing RTL8139.SYS file in the startup package, because the PNP function of the network card cannot be realized with this file, and the PNP of the network card is a crucial part of the PNP diskless WIN98

Modify the Autoexec.bat file

Modify its contents as follows

@echo off

CTTY NUL ; Mask all startup information

cd \winboot

SET WINDIR=C:\WINDOWS

SET SERVER=Leither ; Set file server name

SET SHARE=Pnp98 ; Set the directory of shared C:

@md %WINDIR% > NUL

@md %WINDIR%\SYSTEM > NUL

COPY A:\WINBOOT\RTL8139.SYS %WINDIR%\SYSTEM > NUL

@CALL STARTNET. BAT ; Go to the Startup Network section

Then create a STARTNET BAT file is as follows

@echo off

set comspec=a:\command　set temp=a:\winboot

SNAPSHOT /S /B:A /M:124

NET START IPX

NET LOGON ADMIN ADMIN PASS /YES /SAVEPW:NO ; Log in as Admin and the password is PASS

NET USE C: \\%SERVER%\%SHARE% /Y ; Force mapping C: to a shared directory, and hide the RAM disk

set path=

path=%windir%;%windir%\command;%path%

set comspec=%windir%\command　setmdir /m /r:c:\Windows

set temp=%windir%\temp

set tmp=%windir%\temp

cd %windir%

Win.bat

Edit and modify the Win.bat file

QSetBD C:

Net use E: \\%Server%\MicroNet /y ; Map the MICRONET shared directory to E:, which contains all users; Directory to facilitate the management of user files during login

Net use F: \\%Server%\APPL /y ; Common application Installation directory

NET USE G: \\%Server%\GAME /Y ; game

NET USE H: \\%Server%\CAI /Y ; computer assisted instruction

Net use I: \\%Server%\Film /Y ; Movie Library

Freemem

CTTY CON

%Windir%\Wincom

So far, the startup package has been completed and can be placed in File server The directory where the PXE startup package is located, but your Diskless WIN98, you can install a video card sound card Driver However, if you are doing a template system (you can clone everywhere after installing it), it is recommended not to install the motherboard driver, otherwise cloning motherboards of different chipsets may cause some unexpected problems.

Optimization of modifying the minimum registry and batch file

Although the diskless WIN98 made in the previous step can do the same things as the disk system, it can only be used by one user. But once you start and enter, you will find that all the drive characters just mapped are missing, that is, in WIN just now All network disks mapped in BAT fail under Windows. This is caused by insufficient static system drive letters in the minimum registry. Import the following section into the minimum registry to solve the problem

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Network\Real Mode Net]

"transport"="*nwlink,ndishlp.sys"

"netcard"="rtsnd.dos"

"LoadRMDrivers"=hex:00,00,00,00

"preferredredir"="NWREDIR"

"Transition"=hex:01

"SetupN"=hex:01

"SetupNPath"="C:\\WINDOWS\\"

"StaticDrive"="C,D,E,F,G,H,I" ; Here you can adjust the system's static drive letter from C to Z

After the above adjustment, you can have as many drive letters as you want, but this does not solve the problem of multiple users sharing the WINDOWS directory. To successfully solve this problem, there are two ways: one is to use QUALCNX of Litenet EXE file can be used to automatically number computers with different network card numbers. On this basis, the corresponding batch file can be modified to achieve this; The second is to manually program, read out the MAC address of the network card, and then determine the machine number according to the existing network card database, so as to achieve multi-user login. With this method, different users can really login without having to Secondary login It is convenient for management and accelerates the startup speed; The two methods are described below:

Methods of using Litenet's partial files

To use this method, you need to recompile the existing STARTNET BAT and WIN BAT file. The rewritten file is as follows

STARTNET.BAT

@echo off

set comspec=a:\commandcom

SET NETBUFF=124

set temp=a:\winboot

CTTY CON ; Turn on the screen display for debugging

lh qualcnx ADMIN PASS >nul ; Log in with user name ADMIN and password PASS, and generate USERNAME BAT,; It can be manually programmed here

CTTY NUL ; Close the screen display and start the screen information

Call% TEMP% username.bat; USERNAME.BAT can set the variable CHN as the user name

QAUTOLOG ; This is Secondary login ； Manual programming can remove

NET USE E: \\%SERVER%\%CHN% ; Connect user directory to E:

SET UserName=%CHN% ; Set User Name Variable

SET Inited=NO ; Set the initialization flag to NO

@if exist E:\WINDOWS\SYSTEM. DAT goto SKIPINIT ; Determine whether there is SYSTEM in the user directory DAT file, if; If yes, ignore initialization and directly execute the system startup part

CTTY CON ; Turn on the screen display for debugging

@ECHO Starting Initialize Workstation %CHN%....... ; Display initialization information

CTTY NUL

SET PATH=

SET PATH=%windir%;%windir%\COMMAND

MD E:\WINDOWS ; Create a WINDOWS directory in E: to store system registration

MD E:\WINDOWS\TEMP ; Create a TEMP directory under E: WINDOWS

set temp=E:\WINDOWS\TEMP ; Directs the system temporary directory to E: WINDOWS TEMP

set tmp=E:\WINDOWS\TEMP

*lh %windir%\qualreg E:\WINDOWS /R /A ; Copy and modify with QUALREG system registry To the user directory, this command; It can be replaced by COPY command, but later WIN The part marked with * in BAT; Cannot be removed; It can be manually programmed here

set winbootdir=%windir%

SET Inited=YES ; Set the initialization completed flag Inited to YES

CTTY CON ; Turn on the screen display function

@Echo Workstation %CHN% Has Been Initiliazed! ; Display the completion initial information

:SKIPINIT ; Ignore initialization jump label

CTTY NUL

@%Windir%\Win.bat ; Go to execute WIN under C: WINDOWS BAT file

The content of WIN.BAT file is as follows:

set path=

path=%windir%;%windir%\command;%windir%\system

setmdir /m /r:E:\Windows ; The registry is redirected to E: WINDOWS

set comspec=%windir%\commandcom ; command interpreter Redirect to C: WINDOWS COMMANDCOM

IF %Inited%==NO GOTO SKIPINIT ; Judge whether to jump according to the initialization flag

MD E:\ My Documents ; Create a "My Documents" directory in E: to store documents

*QPATCH %Windir%\Client.reg E:\Windows\%CHN%. REG ; If in the previous STARTNET Used in BAT file; The part with * can be omitted, and the part with * can also be omitted; You can use it here; It can also imitate the stupid method of Chinese education and use the ECHO command

*Regedit E:\Windows\%CHN%. REG ; Import client configuration Registry file

*regedit %Windir%\Policies. POL ; Import system policy file

:SKIPINIT ; Ignore initialization jump label

QSetBD %DRIVE% ; Set the startup drive letter to C:, and there is no program to replace

Net use D: \\%SERVER%\SYS/y ; Map the SYS shared directory to D:, where the source files of WIN98 are stored,; And various PNP hardware drivers, so that WIN98 can

; Automatically identify and install drivers for various PNP hardware

NET USE G: \\%Server%\GAME /Y ; game

NET USE H: \\%Server%\CAI /Y ; computer assisted instruction

Net use I: \\%Server%\Film /Y ; Movie Library

NET USE H: \\%Server%\Music /Y ; Music Library

Freemem ; Eliminate A in memory: can be replaced by QRESTALL

CTTY CON ; Turn on the screen display function to enter WINDOWS

%Windir%\Winom ; Run WINCOM to enter WINDOWS;

So far, use some Litenet files to enable different users to log in and share the WINDOWS directory Diskless The method of starting has been introduced. Before using, you must also set the BAT and WIN Copy the files used in BAT to the corresponding directory, otherwise the system will have problems, or it will not start, or it will start abnormally.

Manual programming

To program manually to realize the above functions Litenet can achieve, it is necessary to write programs with the same or similar functions as Litenet. Where manual programming is required, the author has already made notes on the above methods. In the appendix of this book, there will be source code Tuobo Pascal v6.0 is used. As for the implementation method, it is similar to the above method, but not different. The following lists some of the above methods Registry file These files are essential in manual programming methods

The following is the content of the Client.reg file:

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Mpsoft]

[HKEY_LOCAL_MACHINE\Software\Mpsoft\Smenu]

"computernum"="{%CHN%}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Winlogon]

"AutoAdminLogon"="{%CHN%}"

"DefaultUserName"="{%CHN%}"

"DefaultPassword"="{%CHN%}"

[HKEY_LOCAL_MACHINE\Network\Logon]

"DontShowLastUser"=dword:00000000

"UserName"="{%CHN%}"