Windows 98 Live Cd Project (Update)

**BeatZero** · December 14, 2009

This project creates a bootable image of Windows 98 SE, based on Mindows, with only 23MB.

A WinBuilder extracts the files from the WIN98 CDROM, uses registry files and system files configuration pre-defined, and creates a bootable ISO image. With PREPTOOL_98 in the first stage of the boot, detects and installs devices such as network, mouse, keyboard, configure the plugins, settings, etc ...

With RunOnce.exe patched and SYSDM.CPL of WIN95, the computer does not restart, it restarts in MS-DOS, and then starts Windows with the drivers and services installed and enabled!

The current version is 1.11B, and can be downloaded here:

Download here

Size: 26MB (Update 11/02/2010)

File name: Win98LiveCD.zip

Some Features:

-Detect and install drivers on boot without reboot computer.

-Default VGA driver is vbemp (bye bye 640X480X16 colors).

-USB Suport

-Customizable plugins.

-Multi language suport (Russian, Spanish, Polish, english, Portuguese-BR, Portuguese-PT, Italian, Czech).

-Installation small, based on Mindows, approximately 23mb

Requirements:

-Windows 98 Second Edition CDROM

-Computer with Windows XP, 2K3, vista or Win7

-Virtual PC or VMWare for test your ISO (optional)

Plugins Included in this Build

-Eset NOD32 Antivirus 2.7 Trial *NEW

-Lavalys Everes ultimate 5.30 Trial *NEW

-Opera 9.50 (Internet browser)

-MSN Messenger 5

-7-Zip 4.65 - (Compres / decompress archives)

-IrfanView 4.25 - (view various types of images, bmp, jpg, etc.)

-Xplorer² Lite 1.7.2.7 - (replace the old win95 Explorer File Manager)

-Customizations - (wallpaper, desktop colors, etc..)

Drivers

-Lan - (all lan drivers from DriversPack98, VMWare, Virtual PC and others)

-Storage - (all storage drivers from DriversPack98 and others)

-USB - (Suport Mouse and Keyboard USB, pendrive, USB HDD)

PS: The new plugins does not contain any files or parts attached to the package Win98LiveCdBuider, you need internet connection to download packages from the author site and Winbuilder add them to the project.

Desktop

Disks

Network and sharing

NOD32

"I'm sorry for my bad English"

Edited February 15, 2010 by BeatZero

**jaclaz** · December 14, 2009

It seems to me like a really nice project.

I haven't tested it by running, only peeked a bit inside the .cmd's to get the general idea.

Are you ready for questions/suggestions/critics?

I can see IMDISK called in five occasions, two to "mount" and three to "dismount":

BUILD_WIN98LIVE.cmd
imdisk -D -m x:
MAKEISO.CMD
imdisk -D -m x:
rar.cmd
imdisk -a -f TEMP\WIN98\win98.img -m x:
....
imdisk -D -m x:
REBUILD_IMAGE.cmd
imdisk -a -f TEMP\WIN98\win98.img -m x:

Of course the only part that actually runs (if one follows the instructions) is the one in rar.cmd, and the "just to make sure" dismount command in BUILD_WIN98LIVE.cmd.

And here is where I am lost.

What is the use of the WIN98.IMG?

I see great potentialities in your approach, but I would like to better understand it, so that I can (should you allow it, of course ) to give you a few suggestions I have in mind.

Why there is an uumerge.exe and an uumerge2.exe? They seem identical to me.

About MSN messenger, I would remove it (besides from your project from the whole world ).

jaclaz

**BeatZero** · December 14, 2009

Jaclaz, thank you for your interest in the project.

Let me explain your questions ....

The files WIN98.IMG would be a bootable image, type a superfloppy, which is part of the system, the files of the drivers, and the principal, which is the WINDOWS.RAR that extracted for the RAMDISK X: \ boot time.

The IMDISK and utilized to MOUNT / UNMOUNT image (WIN98.IMG)

During the creation of your win98 livecd, the IMDISK will be used only once:

The image is Mounted "BUILD_WIN98LIVE.cmd"

and insert the boot files, folder DOS, Win98 folder, etc ...

The IMDSK unmount after the creation of the ISO image (RAR.CMD)

The file REBUILD_IMAGE.CMD (rebuild all images, win98.img, windows.rar, win98live.iso) can be used to test their MODIFICATIONS, without having to re-extract all files from the CDROM windous 98.

MAKE_ISO.CMD (rebuild a new ISO)

Plugins ....

to enable or disable plugins, see folder PLUGIN ... "CFG_PLUGIN-NAME.CMD"

MSN Messenger disable = run CFG_MSN_MESSENGER_PLUGIN.cmd, choice "2" and click "ENTER"

MSN Messenger enable = run CFG_MSN_MESSENGER_PLUGIN.cmd, choice "1" and click "ENTER"

Edited December 14, 2009 by BeatZero

**jaclaz** · December 14, 2009

I see , so the only use is to create the WIN98.IMG that is later used by grub4dos mapping:

title Mini Windows 98
find --set-root /WIN98/WIN98.IMG
map --mem /WIN98/WIN98.IMG (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

In other words, the "result" is not "really-really" a bootable .iso, but rather a bootable .iso containing a bootable superfloppy image, this was the part that wasn't clear to me at first sight.

I.e. the .iso is just a "container", you can copy the WIN98.IMG to (say) a USB stick booting grldr or grub.exe and add an entry for it in menu.lst and it will work just the same.

About "removing" I meant "removing", I mean are the msn files redistributable?

As well the use of rar.exe should be replaced by the use of freeware 7-zip or of any similar freeware command line archiver, IMNSHO.

As an addition, I would suggest the use of Qemu for the test(s).

There is a pre-packed solution:

MobaliveCD:

http://mobalivecd.mobatek.net/en/

that seems to me like ideal, and much easier than VMware and VirtualPC for people not already familiar with Qemu (or Qemu Manager).

jaclaz

Edited December 14, 2009 by jaclaz

**BeatZero** · December 14, 2009

Ok Jaclaz .. all suggestions are welcome, changes in scripts, new alternatives is what I want, with the help of all, perhaps in the future so we have a WINBUILDER for win98.

regarding grub4dos you're right, allows the use of heath stick ...

Since the rar.exe, I have found another alternative (yet), I tried pkunzip, uharcd and had crashes on some computers

MobaLiveCD is interesting, however never used it ... I will try this :-)

**luluthefirst** · December 14, 2009

⁭

Edited February 9, 2018 by luluthefirst

**jaclaz** · December 14, 2009

Why not 7-zip?

http://www.7-zip.org/

7-Zip works in Windows 7 / Vista / XP / 2008 / 2003 / 2000 / NT / ME / 98.

32-bit 7-Zip Command Line Version

http://downloads.sourceforge.net/sevenzip/7za465.zip

Why using EXTRAC32.EXE instead of EXTRACT.EXE?

Both EXTRAC32.EXE and EXTRACT.EXE are normally in %Windir%\System32 on XP systems, i.e. in path.

C:\WINDOWS\system32>extrac32 /? | more
Microsoft ® Cabinet Extraction Tool - Version 5.1.2600.2180
Copyright © Microsoft Corporation. All rights reserved..

EXTRACT [/Y] [/A] [/D | /E] [/L dir] cabinet [filename ...]
EXTRACT [/Y] source [newname]
EXTRACT [/Y] /C source destination

  cabinet  - Cabinet file (contains two or more files).
  filename - Name of the file to extract from the cabinet.
             Wild cards and multiple filenames (separated by
             blanks) may be used.

  source   - Compressed file (a cabinet with only one file).
  newname  - New filename to give the extracted file.
             If not supplied, the original name is used.

  /A         Process ALL cabinets.  Follows cabinet chain
             starting in first cabinet mentioned.
  /C         Copy source file to destination (to copy from DMF disks).
  /D         Display cabinet directory (use with filename to avoid extract).
  /E         Extract (use instead of *.* to extract all files).
  /L dir     Location to place extracted files (default is current directory).
  /Y         Do not prompt before overwriting an existing file.

C:\WINDOWS\system32>extract /?
Microsoft ® Cabinet Extraction Tool - Version 5.1.2600.2180
Copyright © Microsoft Corporation. All rights reserved..

EXTRACT [/Y] [/A] [/D | /E] [/L dir] cabinet [filename ...]
EXTRACT [/Y] source [newname]
EXTRACT [/Y] /C source destination

  cabinet  - Cabinet file (contains two or more files).
  filename - Name of the file to extract from the cabinet.
             Wild cards and multiple filenames (separated by
             blanks) may be used.

  source   - Compressed file (a cabinet with only one file).
  newname  - New filename to give the extracted file.
             If not supplied, the original name is used.

  /A         Process ALL cabinets.  Follows cabinet chain
             starting in first cabinet mentioned.
  /C         Copy source file to destination (to copy from DMF disks).
  /D         Display cabinet directory (use with filename to avoid extract).
  /E         Extract (use instead of *.* to extract all files).
  /L dir     Location to place extracted files (default is current directory).
  /Y         Do not prompt before overwriting an existing file.

But 7-zip can extract from .cab files allright.

Also, I would suggest using a more "structured" approach.

In BUILD_WIN98LIVE.cmd there are 371 lines with more or less the same content including a few COPY /L (most probably due to copy and paste ).

Instead of (example):

115 PROJECT\TOOLS\EXTRAC32.EXE /Y /a PROJECT\SYSTEM\SYSPREP.CAB GETCLINF.DLL /L TARGET\WINDOWS\SYSTEM\
242 PROJECT\TOOLS\EXTRAC32.EXE /Y /a PROJECT\SYSTEM\SYSPREP.CAB PSYDMSOS.DLL /L TARGET\WINDOWS\SYSTEM\
243 PROJECT\TOOLS\EXTRAC32.EXE /Y /a PROJECT\SYSTEM\SYSPREP.CAB PSYDO957.DLL /L TARGET\WINDOWS\SYSTEM\
244 PROJECT\TOOLS\EXTRAC32.EXE /Y /a PROJECT\SYSTEM\SYSPREP.CAB PSYSDUP2.EXE /L TARGET\WINDOWS\SYSTEM\
264 PROJECT\TOOLS\EXTRAC32.EXE /Y /a PROJECT\SYSTEM\SYSPREP.CAB RUNONCE.EXE /L TARGET\WINDOWS\SYSTEM\

One could have a plain .txt file SYSPREP.LST:

GETCLINF.DLL SYSTEM
PSYDMSOS.DLL SYSTEM
PSYDO957.DLL SYSTEM
PSYSDUP2.EXE SYSTEM
RUNONCE.EXE SYSTEM

and in BUILD_WIN98LIVE.cmd something like:

@ECHO OFF
SET SOURCE_PATH=PROJECT\SYSTEM\
SET TARGET_PATH=TARGET\WINDOWS\
CALL :DO_EXTRACT SYSPREP
::...
GOTO :EOF

:DO_EXTRACT
FOR /F "tokens=1,2" %%A IN ( %1.LST) DO ECHO EXTRACT.EXE /Y /a %SOURCE_PATH%%1.CAB %%A %TARGET_PATH%%%B
GOTO :EOF

I guess it would be easier to add/remove things in a further stage.

@luluthefirst

Because it would be a plain WAREZ release.

jaclaz

Edited December 14, 2009 by jaclaz

**BeatZero** · December 14, 2009

Jaclaz, thanks for the tips, I will deploy in the next build ..

actually I'm thinking of converting the scripts, and use them with WINBUILDER, what you tell me that idea?

**BeatZero** · December 14, 2009

luluthefirst.. try run "MAKEISO.CMD"

**jaclaz** · December 14, 2009

Jaclaz, thanks for the tips, I will deploy in the next build ..
actually I'm thinking of converting the scripts, and use them with WINBUILDER, what you tell me that idea?

Well, I am at the same time a fierce substainer and somewhat a detractor of Winbuilder.

I personally think that the means are not at all important.

I prefer batches, as I know a bit about them (vs. next to nothing about Winbuilder .scripts) I simply cannot read .scripts, too many commas, quotes and #$ for my mental parsing engine, but it works very well if you "get the hang of it".

It is entirely up to you.

jaclaz

**luluthefirst** · December 14, 2009

⁭

Edited February 9, 2018 by luluthefirst

**LoneCrusader** · December 15, 2009

Hello BeatZero, always glad to see new members in the Windows 98 community.

I've not had an opportunity to look at your project yet, but I find it very interesting, and I hope you get it perfected. I actually did some reading up on Windows 98 Live CD's a few weeks ago, but I haven't had the time to even attempt it yet and I have no experience with such things. Here's a link to a couple of the pages I looked at, you may have already seen them or they may not help you, but they're relevant to the topic at hand so they may help someone else.

Win98LiveCD1

[link removed]

I was thinking about trying my hand at making my own Win98 Live DVD. I know someone's going to ask "why DVD" so I'll go ahead and explain. The size of the image/install doesn't matter to me, in fact, I'd rather have the entire system, with as many drivers, updates, tools & applications as possible. I'd prefer to have a full featured system ready to do anything I want whenever I load it up (like KNOPPIX, etc). (I know this would not be a good setup for older systems, but most of my hardware is Pentium 4 Northwood or Prescott ready)

But anyhow, best of luck, and welcome!

Edited December 15, 2009 by dencorso
No links about warez (or to warez, but this wasn't the case) allowed...

**kamahl** · December 16, 2009

About MSN messenger, I would remove it (besides from your project from the whole world ).

Swapping MSN Messenger for Pidgin would be a much nicer idea. Pidgin can use all the popular IM networks, and has more features than MSNv5 anyway.

**BeatZero** · December 23, 2009

New release = http://www.sendspace.com/file/51fd58

The project has been updated, all scripts were modified and integrated with WinBuilder.

The use of IMDISK is no longer necessary.

Fixed some bugs...

"A happy Christmas to all!"

BeatZero

**win98user** · December 27, 2009

Hi Everybody. It is my 1st post on this forum I tested your project on 3 different computers and it works, but I have problems with USB. My mouse wasn't detected. I have USB mouse. I haven't tryed pendrives and other usb devices. Besides, everything is ok. Big thanks for working NTFS

Image I made on Windows XP SP2 with Winbuilder included for your project. My installtaion disc was Windows 98 SE English Version Sorry for my english It isn't good

Sign In

Windows 98 Live Cd Project (Update)

Recommended Posts

BeatZero

jaclaz

BeatZero

jaclaz

BeatZero

luluthefirst

jaclaz

BeatZero

BeatZero

jaclaz

luluthefirst

LoneCrusader

kamahl

BeatZero

win98user

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members

Activity

Browse