as United States
`a2) Patent Application Publication co) Pub. No.: US 2002/0194394 Al
`(43) Pub. Date: Dec. 19, 2002
`
`Chan
`
`US 20020194394A1
`
`(54) RUNNING RAMDISK-BASED MICROSOFT
`WINDOWS95/98/ME
`
`(52) US. Che
`
`cescssessssnssssnstnttnsseeneuee 709/319; 713/189
`
`(76)
`
`Inventor: Kam-fu Chan, Tsuen Wan (HK)
`
`(57)
`
`ABSTRACT
`
`Correspondence Address:
`BURNS DOANE SWECKER & MATHIS LL P
`POST OFFICE BOX 1404
`ALEXANDRIA,VA 22313-1404 (US)
`
`(21) Appl. No.:
`
`10/169,311
`
`A method, resulting in producing a customized running
`imageoffiles, is provided for running, through customized
`booting process. Microsoft Windows 95/98/ME on ramdisk
`in protected WINDOWS mode with additional advantages
`of either freedom of choice of access to non-volatile rewrite-
`
`(86) PCT No.:
`
`PCT/IB00/01966
`
`(30)
`
`Foreign Application Priority Data
`
`able storage medium orflexibility of preserving user con-
`(22) PCT Filed:—Dec. 27, 2000
`figuration in User Drive(s). The method and the booting
`process includethe steps of producing a customized copy of
`configuration files used by Microsoft Windows 95/98/ME;
`copying these configuration files, system files provided by
`Microsoft for setting up Windows 95/98/ME,other device
`drivers and programsto storage medium/mediato be used in
`computer
`system(s) or device(s)
`capable of
`running
`Microsoft Windows 95/98/ME; and with the use of these
`files from the storage medium/media, booting up in real
`DOS mode, preparing for and running off Microsoft Win-
`dows 95/98/ME on ramdisk in protected WINDOWSmode
`in the computer system(s) or device(s).
`
`Jan. 6, 2000
`Nov. 13, 2000
`Nov. 13, 2000
`
`(Qeeseeeesecsessessesseeseesene PCT/IB00/00010
`
`(Qeeeeeeseeeccsesseessesseeseesene PCT/IB00/01671
` (Qeeseceescseessseessssseserssnnen PCT/1B00/01647
`
`Publication Classification
`
`(51)
`
`Int. Ch? oe H04L 9/32; GO6F 9/00
`
`Google Exhibit 1023
`Google v. VirtaMove
`
`Google Exhibit 1023
`Google v. VirtaMove
`
`

`

`US 2002/0194394 Al
`
`Dec. 19, 2002
`
`RUNNING RAMDISK-BASED MICROSOFT
`WINDOWS95/98/ME
`
`TECHNICAL FIELD
`
`[0001] This invention relates to running Microsoft Win-
`dows 95/98/Millenium Edition (the operating system) in
`device(s), including computer system(s), capable of running
`the operating system. In particular, this invention relates to
`utilizing ramdisk as a storage medium for the running image
`of the operating system on which the full operating system
`can be run off. Access to other non-volatile storage medium
`is either not required or allowed for preserving user con-
`figuration and providing user flexibility for running ramdisk-
`based Microsoft Windows
`95/98/Millenium Edition
`(Microsoft Windows 95/98/ME) in protected WINDOWS
`mode.
`
`BACKGROUND ART
`
`[0002] For any computer system or device capable of
`running it, Microsoft Windows 95/98/MEis designed to be
`installed onto and to run on a non-volatile rewriteable
`storage medium with sufficient space and speed. Once the
`protected-mode portion of the operating system runs off on
`such storage medium, the medium cannot be removed from
`the computer system or device as the running system need
`gain access to it. In this sense, the storage medium need to
`be fixed with the computer system or device when the
`operating system starts running in protected WINDOWS
`mode. This description applies to local
`installation and
`running of the operating system in standalone computer
`system(s) or device(s) as well as Server-based Setup and
`running of the operating system for networked computer
`system(s) or device(s).
`
`[0003] The present invention provides for running the
`protected-mode Microsoft Windows 95/98/ME on ramdisk
`in two alternative ways. The first way is called the ‘Con-
`tained Style’, the second the ‘Split Style’.
`
`the protected-mode
`In the Contained Style,
`[0004]
`Microsoft Windows 95/98/ME can be run wholly on ram-
`disk without the need for accessing other storage medium.
`However,it allows non-volatile rewritable storage medium
`to be used, for instance, for the purposes of saving data
`derived from work done during using the operating system
`and of storing user applications. Running the operating
`system in the Contained Style however cannot suit all
`purposes and uses.
`
`[0005] For instance, the Contained Style cannot provide
`for easy userflexibility. Preservation of user configuration,
`for instance, in relation to user application(s) set up on
`non-volatile rewriteable storage medium during using the
`operating system requires an additional back-up step before
`shutting down the operating system and cannot be done
`automatically. In this way, if such information is not backed
`up and restored onto the running image of the operating
`system on ramdisk before it is started into protected WIN-
`DOWS mode next time again, modifications to user con-
`figuration during a previous session cannot be utilized.
`Starting up the operating system always in the same way
`may be suitable or actually required in certain cases and for
`certain purposes. However, for other cases and purposes,
`preservation of modifications to user configuration may be a
`necessity. If such modifications have to be backed up before
`
`shutting down every session and restored every time before
`another session, it will lead to maintenance inconvenience.
`
`for some computer system(s) or
`[0006] Furthermore,
`device(s), the amount of RAM, Random Access Memory,
`installed is limited and not sufficient to hold a full installa-
`tion of the operating system, not
`to mention other user
`applications.It is thus essential to separate the core part from
`other less essential part of the operating system. The core
`part of the operating system is to be stored in a ‘System
`Drive’ on RAM for fast running and the less essential part
`on a ‘User Drive’ on non-volatile rewriteable storage
`medium for access when there is a need. An exampleis the
`possibility of separating Internet Explorer (to be stored on
`User Drive for occasional access or replaced by other similar
`program of choice) from the system kernel of the operating
`system (to be stored in a System Drive on ramdisk for fast
`running). User applications and its configuration can also be
`stored on such User Drive. The storage of less essential part
`of the operating system and other user applications together
`with their configuration on a User Drive and the preservation
`of their settings from session to session of running the
`operating system relies on the possibility of preserving such
`user configuration on a User Drive created on a non-volatile
`rewriteable storage medium.
`
`[0007] The Split Style makes possible the phenomenon of
`running the operating system on ramdisk andstill provides
`for the preservation of uscr configuration. This thus allows
`for the possibility of separating the core part (to be stored in
`System Drive on ramdisk for fast running) from the less
`essential part (to be stored on User Drive for occasional
`access) of the operating system and the setting up of user
`applications on User Drive(s). The Split Style therefore
`caters for user flexibility by automatically preserving modi-
`fications to user configuration during using the operating
`system.
`
`In Contained Style, user configuration files and
`[0008]
`user applications, if any, are stored together with the running
`image of the operating system on ramdisk. In other words,
`the System Drive containing the running image of the
`operating system and the User Drive containing user con-
`figuration and user applications are all on ramdisk. At where
`the System Drive and the User Drive can be either separated
`into different drives or integrated into one and the same
`drive.
`
`In Split Style, user configuration files and user
`[0009]
`applications, if any, are stored on a non-volatile rewriteable
`storage medium, which can be mapped and usedas a drive
`under real DOS mode before the operating system is started
`into protected WINDOWSmode. Theyare separate from the
`running image of the operating system in System Drive on
`the ramdisk.In ather words, the System Drive containing the
`running image ofthe operating system is on ramdisk and the
`User Drive containing user configuration and user applica-
`tions is on non-volatile rewriteable storage medium.
`
`To be able to start running Microsoft Windows
`[0010]
`95/98/ME on ramdisk cither in Contained Style or in Split
`Style, firstly the operating system has to be booted up under
`real DOS mode. Secondly, a ramdisk with sufficientsize and
`compatible with Microsoft Windows 95/98/MEhasto be sct
`up. Thirdly,
`the running image of the operating system
`contained in System Drive has to be transferred to the
`ramdisk. User Drive (containing suitable configuration files
`
`

`

`US 2002/0194394 Al
`
`Dec. 19, 2002
`
`and other applications if any) is placed either on ramdisk
`again (either integrated with System Drive or separate into
`another drive on ramdisk) as in the Contained Style or on
`other non-volatile rewriteable storage medium asin the Split
`Style. Lastly, Microsoft Windows 95/98/MEisstarted off in
`protected WINDOWSmodeon the ramdisk by issuing the
`command, WIN,at the DOS command prompt.
`
`programmes through AUTOEXEC.BAT or through real
`DOS command prompt impossible when Microsoft Win-
`dows MEboots up from a hard disk. To be able to load real
`DOSmode drivers or programmes, one has to boot up from
`the Emergency Boot Disk (prepared by Microsoft Windows
`ME)placed in the booting floppy drive. This creates great
`inconvenience. This problem, however, can be solved by
`writing a software which enables access to real DOS mode
`[0011] Before this invention, no successful attempts of
`during hard disk booting by making patches to IO.SYS,
`running Microsoft Windows 95/98/ME on ramdisk in pro-
`COMMAND.COMin the root directory of the hard disk
`tected WINDOWSmode have been disclosed. The ramdisk
`
`boot-up in_thedrive and REGENV32.EXE
`
`
`
`driver bundled with the operating system supports only 32
`\WINDOWS\SYSTEM directory. One of such software,
`megabytes of maximum size which is not sufficient for
`Real DOS-Mode Patch for Windows ME v1.3, has been
`storing and running the whole running image of the pro-
`released on the Internet. According to the document accom-
`tected-mode Microsoft Windows 95/98/ME. The ramdisk
`panying the software, Real DOS-Mode Patch for Windows
`(version: rhk.rd.1.0) released on Jan. 1, 2000 and copy-
`MEv1.3 was released on Aug. 15, 2000 by a group called
`righted by Reliable (H. K.) Limited is found to be compat-
`MANIFEST DESTINY with a web-site, which appears, at
`ible with Microsoft Windows 95/98/MEand can be config-
`the time of writing, to be engaging in other business instead
`ured up to 2 gigabytes which is more than sufficient for the
`of software development.
`purpose of running the whole operating system on it.
`
`[0012] However, the transfer of the running image of the
`operating system to ramdisk is made difficult by the prob-
`lems associated with long filenames adopted by the operat-
`ing system. The commands or programmes provided by
`Microsoft for copying files cannot cope with long filenames
`under real DOS modefor this purpose. The documentation
`of Microsoft—“Unable to Copy Long File Name Files to
`Large RAMDrive”—makcesit plainly that long file name
`files cannot be copied to ramdisk of over 10 megabytes
`under Microsoft Windows 98. The document is found at
`
`http: //support.microsoft.com/support/kb/articles/Q192/9/
`27.ASP. Microsoft Windows ME,in its official version, even
`disables the access to real DOS mode. This limitation,
`however, does not apply to the copying process after the
`protected-mode Microsoft Windows 95/98/MEis started.
`However, for the purpose of transferring the running image
`of the operating system to ramdisk under real DOS mode
`before starting it in protected WINDOWSmode, there must
`be a workaround solution.
`
`In this respect, Odi’s DOStools for long file names
`[0013]
`copyrighted by Ortwin Glueck and released on Dec. 7, 1999
`at http://odi.webjump.com/ appear to provide partly the
`solution of copying long file namefiles onto large ramdisk.
`However,this tool set contains known bugsas described in
`the Readme.txt accompanying the tool set.
`
`[0014] There are two significant problems associated with
`the use ofthis tool set at present. Firstly, copyingall the files
`comprising the whole running image of Microsoft Windows
`95/98/ME using this utility file by file takes long time.
`Secondly, this tool set at present is only capable of dealing
`with Unicode characters from code pages 00h and 25h.
`Manyversions of Microsoft Windows 95/98/ME in lan-
`guages other than code pages 00h and 25h maycontain long
`file names that this tool set cannot cope with. Thus those
`versions of Microsoft Windows 95/98/ME cannot be run on
`ramdisk by using this tool set for copying or transferring the
`running image.
`
`In the case of Microsoft Windows ME, another
`[0015]
`problem of running it on ramdisk is due to the fact that this
`particular version of the operating system disables access to
`real DOS mode during the hard disk boot-up process. This
`suppression of real DOS mode makes loading real DOS
`mode drivers through CONFIG.SYS and real DOS mode
`
`[0016] Giventhat the above problemsare solved, simply
`copying or transferring the running image prepared by the
`installation programme of Microsoft Windows 95/98/MEto
`ramdisk is guaranteed to fail on running if the operating
`system has not been properly configured for the purpose of
`running on ramdisk.
`
`[0017] This invention makes possible the running of
`Microsoft Windows 95/98/ME in protected WINDOWS
`mode on ramdisk after the operating system is booted up in
`real DOS mode by bootable device. Traditionally, a com-
`puter system or device is booted up from a hard disk,floppy
`disk or boot ROM. Microsoft documents its support of
`booting from alternate devices by Microsoft Windows98,
`for instance, at http://www.microsoft.com/IIWDEV/devdes/
`edboot.htm. The EL Torito-Bootable CD-ROM Format Boot
`
`Specification, Version 1.0,is for booting a computer system
`from CDROM. Compaq,Intel, Phoenix BIOS Boot Speci-
`fication, Version 1.01 and ATAPI Removable Media Device
`BIOSSpecification, Version 1.0 are other specifications for
`booting from various formsof alternate booting devices. At
`present,
`these specifications allow booting of Microsoft
`Windows 95/98/MEinto real DOS mode, the running ofit
`in protected WINDOWSmode relies on the presence of a
`fixed non-volatile storage medium suchas a fixed hard disk
`or a fixed removable disk. These specifications do not
`specify the setting up and use of ramdisk, the configuration
`of the running image of Microsoft Windows 95/98/ME,the
`transfer of this running image from a storage medium onto
`a ramdisk and the running of the protected-mode Microsoft
`Windows 95/98/ME on the ramdisk. What is left out as
`outlined above in these specifications is specified by this
`invention.
`
`[0018] Microsoft’s web page on “Bootable CD Drives and
`Windows 98” at http:/Avww.microsoft.com/HWDEV/stor-
`age/cdboot98.htm points out that “[A]s implemented under
`Windows 98, booting from the product CD is much like
`booting from an emergency floppy disk—it is enough to
`allow uscrs to scc their devices, start an installation, and so
`on, but users cannot actually run the full operating system
`from CD”. Without this invention, this statement is appli-
`cable to Microsoft Windows 95/98/ME as a whole. Like-
`wise, the solution of creating a CD capable of booting the
`full Microsoft Windows 98 at http:/Avwww.ct.heise.de/ct/
`english/99/11/206/put forward by Tobias Remberg and Hajo
`
`

`

`US 2002/0194394 Al
`
`Dec. 19, 2002
`
`Schulz does not provide a good solution for creating a
`bootable CD for running Microsoft Windows 95/98/ME. It
`involves the use of ramdisk for storing registry files and
`other temporary files.
`In this way,
`the CD cannot be
`removed. And as the running of the operating system relies
`on this non-rewriteable CD, which cannot be taken away
`while running, the running speed is slow. The whole system
`may crash or may not function properly when the operating
`system or application programmes require(s) direct write-
`access to the drive represented by the CD. A better and
`complete solution to the problem is to completely move the
`whole operating system onto ramdisk so that it no longer
`relies on the use of CD for system operation. This is made
`possible by the Contained Style of this invention, which
`does not require any fixed non-volatile rewriteable storage
`medium either. For the purpose of preserving modifications
`to user configuration when running the operating system on
`ramdisk,
`the Split Style of this invention by definition
`requires a non-volatile rewriteable storage medium for its
`operation.
`
`DISCLOSURE OF INVENTION
`
`[0019] This invention reveals a method of preparing
`Microsoft Windows 95/98/ME to run on ramdisk in two
`styles, namely the Split Style and the Contained Style.
`
`[0020] The Split Style requires access to a non-volatile
`rewriteable storage mediumfor storing and preserving user
`configuration. This requirement of non-volatile rewriteable
`storage medium for running the operating system in ram-
`disk-based protected WINDOWS modebrings the advan-
`tage of automatically preserving modifications to user con-
`figuration during running the operating system.
`
`[0021] This advantage allows for separating the core part
`(to be put in System Drive on ramdiskfor fast running) from
`the less essential part (to be stored on User Drive(s) on
`non-volatile rewriteable storage medium for occasional
`access) of the operating system for computer system(s) or
`device(s) with limited system RAM. It also allows for
`setting up user applications on User Drive(s) and their
`continual updating and use from one session to another of
`running the operating system. For the purpose of preserva-
`tion, user configuration used by applications and the oper-
`ating system in protected WINDOWSmode is stored in a
`Uscr Drive on non-volatile rewritcable storage medium. In
`this way, it makes possible fast system operation on ramdisk
`as well as user flexibility and configurability.
`
`[0022] For the sake of clarity in description or the need of
`actual operation, the User Drive described above can be
`conceptually or materially divided into Configuration Drive,
`whereonly user configurationfiles together with WIN.COM
`are stored; Application Drive, where only user applications
`or system applications not necessary for starting up the
`operating system are stored; and Configuration & Applica-
`tion Drive, where Configuration and Application Drive are
`integrated into one drive.
`
`[0023] As distinguished from those files stored in these
`User Drives (including Configuration Drive, Application
`Drive and Configuration & Application Drive) on non-
`volatile rewritcable storage medium as described above,
`system files which form the kernel part of the operating
`system are stored in a System Drive on ramdisk for fast
`running. In order to start up the operating system into
`
`protected WINDOWSmode, both the System Drive and the
`Configuration Drive as described above are required and
`should be made accessible and usable under real DOS mode
`
`when the command WIN or WIN.COMisissued. Applica-
`tion Drive is optional and can be integrated 20 into Con-
`figuration Drive as Configuration & Application Drive or
`integrated with System Drive as System & Application
`Drive.
`
`In the Split Style, System Drive is transferred onto
`[0024]
`ramdisk for fast running and Configuration Drive is placed
`on non-volatile rewriteable storage medium/media for easy
`preservation of user configuration. Non-kernel system appli-
`cation(s) or user application(s) can be placed in a separate
`Application Drive on ramdisk or integrated into System
`Drive on ramdisk in computer(s) or device(s) with sufficient
`RAM for fast running. Or they can be placed in a separate
`Application Drive or integrated with Configuration Drive to
`be stored on non-volatile rewriteable storage medium.
`
`In the Contained Style, all the system files and user
`[0025]
`configuration files of the operating system are transferred
`onto ramdisk and the protected-mode Microsoft Windows
`95/98/MEis run wholly from ramdisk without the need for
`accessing other storage medium. In this Style, both System
`Drive and Configuration Drive are copied or transferred onto
`ramdisk. Other types of User Drive(s) are also copied or
`transferred onto ramdisk as well. Furthermore, User Drive(s)
`including Configuration Drive, Application Drive and Con-
`figuration & Application Drive, can be integrated with
`System Drive in any appropriate manner. As all the data on
`ramdisk will disappear when the poweris off, user configu-
`ration cannot be easily preserved in Contained Style. This
`style of running the operating system may however be very
`useful in cases where the user environment seldom changes
`and where only standard pre-installed applications and pro-
`cedures are used from session to session. Non-volatile
`
`rewritcable storage mcdium/media can still be used for
`storing user data that need to be preserved.
`
`[0026] For the operating system to be run on ramdisk,it
`has to be installed and configured in computer system(s) or
`device(s) as usual using the setup programmeprovided with
`it.here should also be a compatible ramdisk capable of
`holding the running image of the operating system in
`computer system(s) or devicc(s) with sufficient RAM for the
`protected-mode Microsoft Windows 95/98/MEto run. The
`ramdisk can be implemented as hardware external to the
`main RAM or as software within the main RAM. Real DOS
`
`mode software acting as virtual container drive driver for
`utilizing virtual container drive is also required so that the
`image of the customized Microsoft Windows 95/98/ME can
`be stored into virtual container drive(s) for easy copying or
`transfer from storage medium onto ramdisk. Furthermore,
`for
`the particular version of Microsoft Windows ME,
`IO.SYS and COMMAND.COMinthe root directory of the
`hard disk boot-up drive and REGENV32.EXE in the
`\WINDOWS\SYSTEM directory of the installed operating
`system haveto be patched by a software so that accessto real
`DOS mode is enabled for loading real DOS modedriver(s)
`and programme(s) during the booting process. Otherwise,
`the IO.SYS and COMMAND.COMof the Emergency Boot
`Disk (prepared by Microsoft Windows ME)placed in boot-
`up floppy drive have to be used for enabling real DOS mode
`in the booting process. (This boot-up floppy Emergency
`
`

`

`US 2002/0194394 Al
`
`Dec. 19, 2002
`
`[0032] To configure a running image of Microsoft
`Windows 95/98/MEsuitable for running off on a
`ramdisk involves the following sub-steps:
`
`(a) Customizing configurationfiles read by
`[0033]
`the operating system under real DOS mode
`
`[0034] Microsoft Windows 95/98/MEcan be made
`to boot up in two phases,the first phase is booting
`to real DOS mode. The second phaseis booting to
`protected WINDOWSmodebyissuing the WIN
`command. In the first phase, it reads in IO.SYS,
`MSDOS.SYS, COMMAND.COM, CONFIG-
`SYS, and AUTOEXEC.BAT,
`if available and
`applicable, for user-configurable system informa-
`tion, as well as commands and programmesto be
`executed. In the process, it prepares for loading
`into protected WINDOWSmode. It starts its pro-
`tected-mode operation after the WIN commandis
`issued.
`
`[0035]
`
`(1) Customizing MSDOS.SYS
`
`[0036] After issuing the WIN command,the oper-
`ating system is loaded into protected WINDOWS
`mode. Before this is successful,
`the operating
`system checks
`the system information about
`where the Microsoft Windows 95/98/ME WIN-
`DOWSsystem files are located. This information
`is stored in RAM on booting and specified in
`
`[0037] MSDOS.SYS. Modifying MSDOS.SYS
`after booting does not change the system infor-
`mation stored in RAM.So for the operating sys-
`tem to locate these system files and run the pro-
`tected-mode Microsoft Windows
`95/98/ME
`successfully, MSDOS.SYSshould contain proper
`settings before the operating system boots up
`under real DOS mode. The relevant settings for
`the location of the WINDOWSsystem files of
`Microsoft Windows 95/98/MEare specified under
`the section:
`
`[0038]
`
`[Paths]
`
`[0039] WinDir=
`
`[0040] WinBootDir=
`
`[0041] HostWinBootDrv=
`
`Boot Disk can be etched onto a bootable CD by some CD
`recording software so that the bootable CD can emulate the
`Emergency Boot Disk.)
`
`[0027] This invention reveals a method for customizing
`the configuration and preparing a running image of the
`operating system so that when this customized running
`image is booted up,
`it can be run off in protected WIN-
`DOWSmode on ramdisk in two different styles, namely the
`Contained Style and the Split Style. In the Contained Style,
`a System Drive containing the kernel part of the operating
`system and Configuration Drive containing user configura-
`tion files and WIN.COMand optionally other applicationsin
`User Drive(s) are all copied or transferred onto ramdisk for
`Starting the operating system into protected WINDOWS
`mode wholly from ramdisk. Whereas in Split Style,
`the
`System Drive containing the kernel part of the operating
`system is copied or transferred onto ramdisk for fast run-
`ning. Configuration Drive containing user configurationfiles
`and WIN.COMand optionally other applications in User
`Drive(s) are, for the purpose of preserving user configura-
`tion, stored on non-volatile rewriteable storage medium that
`can be recognized and used under real DOS modebefore the
`operating system is started into protected WINDOWSmode.
`‘This method therefore leads to the creation of a product, Le.
`a customized imageof files. This image includes customized
`configuration files, system files of the operating system and
`other device drivers and programmes. The use of this image
`makes possible the phenomenon of running off Micrasoft
`Windows 95/98/ME in protected WINDOWS mode on
`ramdisk.In Split Style, user configuration and application(s)
`are preserved from session to session on non-volatile
`rewriteable storage medium in computer system(s) or
`device(s) capable of running the operating system. In Con-
`tained Style, although user configuration and applications
`set up on ramdisk are not preserved, the operating system is
`free from the requirement of access to non-volatile rewrile-
`able storage medium for its operation.
`
`‘This method and the booting process (inherent in
`[0028]
`using the customized running image) include the steps of
`customizing the configuration of the running image of
`Microsoft Windows 95/98/ME;transferring or copying the
`properly configured running image(including system image
`and user configuration), other device drivers and pro-
`grammesonto storage medium/media; booting off the run-
`ning image in real DOS mode;
`loading the appropriate
`ramdisk; transferring or copying the system image files,
`other device drivers and programmes onto ramdisk with user
`configuration files and application(s) either also on ramdisk
`as in the Contained Style or on non-volatile rewriteable
`storage medium as in the Split Style; and finally issuing the
`command, WIN, under real DOS modeto start the operating
`system into protected WINDOWSmode.
`
`[0042] WinDir= specifies where the WINDOWS
`system files are located. If the virtual container
`drive (the System Drive), which is used for hold-
`ing the system imagefiles, is mounted as V: drive
`after being transferred onto ramdisk, and the
`WINDOWSsystem files, excluding WIN.COM
`[0029] These steps are detailed as follows:
`(WIN.COMhasto be placed underadirectory as
`specified by WinBootDir= setting, but WinBoot-
`1. Customizing the configuration of the run-
`[0030]
`Dir= setting can also be identical
`to WinDir=
`ning image of Microsoft Windows 95/98/ME
`setting as in the Contained Style in case where
`Configuration Drive is integrated with System
`Drive), i.e. the files of the Windowsdirectory, are
`put into a directory named ‘\WINDOWS’, then for
`best operation, WinDir= should be sct as WinDir=
`VAWINDOWS. Specifying WinDir= to another
`directory may work, but does not give best user
`operating environment.
`
`[0031] Before customizing the cxisting configura-
`tion files, all existing configuration files, or better,
`all files have to be backed up first so that
`the
`existing operation system and its configuration is
`preserved. A new copy of these configuration files
`for use with a new copy of the running image of
`the operating system is then to be produced.
`
`

`

`US 2002/0194394 Al
`
`Dec. 19, 2002
`
`[0043] WinBootDir= specifies where the com-
`mand, WIN.COM,is stored. In this directory,
`besides WIN.COM,user configuration files used
`by the operating system (whenit is started into and
`running in protected WINDOWS mode)
`are
`[0054] CONFIG.SYS—and(2) Customizing
`
`
`
`placed. These user configuration files include at
`AUTOEXEC.BAT
`least all Registry files and all INIfiles; Policy files
`and User Profile files may be included as well.
`Besides these files, the two file folders, Desktop
`and Start Menu, and all
`the files and sub-file
`folders within these two file folders of the installed
`Windowsdirectory should at least be included for
`providing a starting user environment. If the drive
`containingthesefiles, i.e. the Configuration Drive,
`is recognized as U: drive, and all these files and
`file folders are placed into a directory called
`\WINDOWS, the WinBootDir= should be set as
`WinBootDir=U:\WINDOWS.
`
`the operating
`to booting error. To ensure that
`system boots up properly in all cases, this setting
`should be set to 0 so as to disable scanning system
`registry on booting,
`
`It is recommended that the LastDrive set-
`[0055]
`ting in CONFIG.SYS under the root directory of
`the boot-up drive be set to Z so as to allow using
`all 26 drive letters, providing for the loading and
`mounting of ramdisk(s), virtual container drive(s)
`and/or other storage device(s)
`
`[0056] As said before, on booting up to real DOS
`mode, the operating system prepares for running
`in protected WINDOWS mode.
`It
`reads
`in
`MSDOS.SYSto find out where the system files
`are. By default, the WinDir and WinBootDir are
`assumed to be C:\WINDOWSif they are not set
`elsewhere in MSDOS.SYS. Using such informa-
`tion, the operating system loads HIMEM.SYSand
`IFSHLP.SYS in the case of Microsoft Windows
`95/98 or
`IFSHLPSYS only in the case of
`Microsoft Windows ME. Thedriver(s) should be
`loaded in memory before WIN.COMis started so
`that the operating system can be run in protected
`WINDOWSmode.
`
`In Split Style where Configuration Drive is to be
`[0044]
`placed on non-volatile rewrileable storage medium separate
`from System Drive, which is to be placed on ramdisk,
`WinBootDir= should be set to a directory in Configuration
`Drive on a non-volatile rewriteable storage mediumthat ts
`accessible under real DOS mode before the operating system
`is started into protected WINDOWSmode. On the other
`hand, WinDire, as said earlier, for best operation, should be
`set as the directory on the virtual container drive, the System
`Drive, hosted by ramdisk where all WINDOWSsystem files
`except WIN.COM are placed (however, including WIN-
`.COM in the WinDir= directory has no adverse effect in
`operation).
`
`Ifthe driver(s), HIMEM.SYSand IFSHLP-
`[0057]
`SYS in the case of Microsoft Windows 95/98 or
`IFSHLP.SYSin the case of Microsoft Windows
`ME,is/are not found in the directory specified by
`In Contained Style, in case where Configuration
`[0045]
`WinDir= in MSDOS.SYS, the driver(s) cannot be
`Drive is made identical to the System Drive, WinBootDir=
`loaded and the operating system cannot be started
`can also be made
`identical
`to WinDir= setting as
`into protected WINDOWSmode. If the driver(s)
`V:\WINDOWSas in the example above (provided that
`is/are put elsewhere,
`the loading of which can
`WIN.COMand userconfiguration files described above are
`however be madepossible by specifying its/their
`also included in this same directory). HostWinBootDrv
`location(s) in CONFIG.SYS with the use of the
`
`DEVICE= or DEVICEHIGH=_statements.
`specifies which drive that boots up the operating system. If
`the ramdisk is loaded as X:,
`the setting can be set as
`HostWinBootDrv=X. This setting is not absolutely required
`and can be set as the actual boot-up drive.
`
`[0046]
`
`‘Ihe setting:
`
`[0047]
`
`[Options]
`
`[0048] DisableLog=
`
`controls whether Bootlog.txt is created dur-
`[0049]
`ing the booting process. It assumes the value 1 or
`0. This setting should be included and set to 1 so
`as to disable the creation of Bootlog.txt on booting
`up if the booting storage medium is a read-only
`medium.
`
`[0050]
`
`Thesetting:
`
`[0051]
`
`[Options]
`
`[0052] SystemReg=
`
`controls whether the booting process scans
`[0053]
`the system registry or not. It assumes the value 1
`or 0. In certain cases, the configuration of running
`Microsoft Windows 95/98/ME off on ramdisk
`may have changed the default location of the
`system registry, cnabling this sctting to 1 will lead
`
`Another wayof loading device driver can be done
`by writing a device loading programme to be
`executed under real DOS,either to be specified in
`AUTOEXEC.BATor to be exec