Topic: Win95 OEM , Win98SE Retail , Win ME OEM AIO CD
started by: deity
Posted by deity on Nov. 11 2005,18:53
Can some one Please help me with details on how to make an all in one CD that contains:Win95 OEM , Win98SE Retail , Win ME OEM , Windows Me Upgrade
They are not self bootable. I have to use a floppy to do the booting. I have Win98SE bootdisk that allows me to boot and use fdisk and stuff when I need to Format a new disk. Then from the bootdisk I go into the CD and run setup.exe. I would like to have it simplified.
I would like to have the a All in one bootable CD which will allow me to format or Fdisk, and Partition a Drive.
How can I make the Win95 OEM , Win98SE Retail , Win ME OEM ,and Windows Me Upgrade Start the "Setup.exe" when I click on one of the options on the following Menu I want to have?
So I want to have these programs as a choice in my menu
- [1] Windows 98 SE Bootdisk [DOS]
- Run: Fdisk - Create, Delete, & Make Active Partitions
- Run: Format - afterward to Make Drive Usable
- [2 ] Paragon Partition Manager v7.00.000.1057
[Creat, resize and merge Hard-Drive disk partitions]
- [3] Windows 95 OEM
- [4] Windows 98 Second Edition
- [5] Windows Me [Millennium Edition] OEM
- [6] Windows Me [Millennium Edition] Upgrade
[Use Win95 OEM or Win98Se for Quality Check]
- [7] Boot from Hard Disk
- [8] Reboot
Here is my current folder Structure.
disk1 Folder contains the following subfolders
-----
| Code Sample |
ezboot PartMngr Win95_OEM Win98SE WinME_OEM WinME_Upgrade |
Directory of each SubFolder
ezboot
-------
| Code Sample |
default.ezb ebback.bmp eblogo.bmp loader.bin logo.bm1 logo.bmp setup98.img standard.ctb w2ksect.bin back.bm1 BACK.BMP cdmenu.ezb |
PartMngr
---------
| Code Sample |
Paragon Partition Manager v7.00.000.1057 Bootfile.bif |
- [ Contents of Paragon Partition Manager v7.00.000.1057 Bootfile.bif ]
Problem when i ran this to test it is that it wont shut down when I click on General - Exit . It just freezes VMware.
-----------
| Code Sample |
| cp850uni.tbl cp855uni.tbl cp874uni.tbl shsucdx.exe images nls autoexec.bat cfg1.cfg config.sys cp437uni.tbl cp737uni.tbl cp852uni.tbl cp857uni.tbl cp858uni.tbl cp861uni.tbl cp862uni.tbl cp863uni.tbl cp864uni.tbl cp865uni.tbl cp866uni.tbl cp869uni.tbl cwsdpmi.exe dinks.dat dinks.ini himem64.exe ibmbio.sys ibmdos.sys layout.ini luxisr.ttf mouse.com mouse.dat reboot.com restart.bat restart.pif start.exe vide-cdd.sys command.com cp775uni.tbl |
Win95_OEM
-----------
| Code Sample |
win95_26.cab win95_27.cab win95_28.cab winsetup.bin wowkit.exe xmsmmgr.exe cs3kit.exe deltemp.com dossetup.bin extract.exe FORMAT.COM layout1.inf layout.inf MINI.CAB MSINFO.INF OEMSETUP.BIN OEMSETUP.EXE PRECOPY1.CAB PRECOPY2.CAB readme.txt RMM.PDR save32.com scandisk.pif scandisk.exe scanprog.exe SERIAL#.txt SETUP25I.EXE SETUP32.EXE setup.exe setup.txt smartdrv.exe SUHELPER.BIN SWINST4.EXE wb16off.exe win95_02.cab win95_03.cab win95_04.cab win95_05.cab win95_06.cab win95_07.cab win95_08.cab win95_09.cab win95_10.cab win95_11.cab win95_12.cab win95_13.cab win95_14.cab win95_15.cab win95_16.cab win95_17.cab win95_18.cab win95_19.cab win95_20.cab win95_21.cab win95_22.cab win95_23.cab win95_24.cab win95_25.cab |
Win98SE
---------
| Code Sample |
WIN98_74.CAB WIN98_OL.CAB xmsmmgr.exe ols tour BASE4.CAB BASE5.CAB BASE6.CAB CATALOG3.CAB chl99.cab deltemp.com dossetup.bin DRIVER11.CAB DRIVER12.CAB DRIVER13.CAB DRIVER14.CAB DRIVER15.CAB DRIVER16.CAB DRIVER17.CAB DRIVER18.CAB DRIVER19.CAB DRIVER20.CAB extract.exe FORMAT.COM intl.txt mini.cab NET7.CAB NET8.CAB NET9.CAB NET10.CAB OEMSETUP.BIN OEMSETUP.EXE PRECOPY1.CAB PRECOPY2.CAB save32.com scandisk.pif scandisk.exe scanprog.exe scanreg.exe SERIAL#.txt setup0.wav setup1.wav setup2.wav setup.exe setup.txt smartdrv.exe suback.bin sucatreg.exe suhelper.bin w98setup.bin wb16off.exe WIN98_21.CAB WIN98_22.CAB WIN98_23.CAB WIN98_24.CAB WIN98_25.CAB WIN98_26.CAB WIN98_27.CAB WIN98_28.CAB WIN98_29.CAB WIN98_30.CAB WIN98_31.CAB WIN98_32.CAB WIN98_33.CAB WIN98_34.CAB WIN98_35.CAB WIN98_36.CAB WIN98_37.CAB WIN98_38.CAB WIN98_39.CAB WIN98_40.CAB WIN98_41.CAB WIN98_42.CAB WIN98_43.CAB WIN98_44.CAB WIN98_45.CAB WIN98_46.CAB WIN98_47.CAB WIN98_48.CAB WIN98_49.CAB WIN98_50.CAB WIN98_51.CAB WIN98_52.CAB WIN98_53.CAB WIN98_54.CAB WIN98_55.CAB WIN98_56.CAB WIN98_57.CAB WIN98_58.CAB WIN98_59.CAB WIN98_60.CAB WIN98_61.CAB WIN98_62.CAB WIN98_63.CAB WIN98_64.CAB WIN98_65.CAB WIN98_66.CAB WIN98_67.CAB WIN98_68.CAB WIN98_69.CAB WIN98_70.CAB WIN98_71.CAB WIN98_72.CAB WIN98_73.CAB |
WinME_OEM
-----------
| Code Sample |
xmsmmgr.exe ols BASE2.CAB CATALOG.CAB cleanhd.txt deltemp.com dossetup.bin DRIVER5.CAB DRIVER6.CAB DRIVER7.CAB extract.exe format.com intl.txt mini.cab msbatch.inf NET3.CAB NET4.CAB oemsetup.bin oemsetup.exe PRECOPY1.CAB save32.com scandisk.pif scandisk.exe scanprog.exe scanreg.exe setup0.wav setup.exe setup.txt smartdrv.exe suback16.bin suback.bin suhelper.bin w9xsetup.bin wb16off.exe win640.bin win800.bin win1024.bin WIN_8.CAB WIN_9.CAB WIN_10.CAB WIN_11.CAB WIN_12.CAB WIN_13.CAB WIN_14.CAB WIN_15.CAB WIN_16.CAB WIN_17.CAB WIN_18.CAB WIN_19.CAB WIN_20.CAB WIN_21.CAB WIN_22.CAB WIN_OL.CAB winme.wmv |
WinME_Upgrade
---------
| Code Sample |
WIN_OL.CAB winme.wmv xmsmmgr.exe ols BASE2.CAB CATALOG.CAB cleanhd.txt deltemp.com dossetup.bin DRIVER5.CAB DRIVER6.CAB DRIVER7.CAB extract.exe intl.txt mini.cab NET3.CAB NET4.CAB PRECOPY1.CAB save32.com scandisk.pif scandisk.exe scanprog.exe scanreg.exe setup0.wav setup.exe setup.txt smartdrv.exe suback16.bin suback.bin suhelper.bin w9xsetup.bin wb16off.exe win640.bin win800.bin win1024.bin WIN_8.CAB WIN_9.CAB WIN_10.CAB WIN_11.CAB WIN_12.CAB WIN_13.CAB WIN_14.CAB WIN_15.CAB WIN_16.CAB WIN_17.CAB WIN_18.CAB WIN_19.CAB WIN_20.CAB WIN_21.CAB WIN_22.CAB |
Thank you for taking the time to read this and also Thanks for any Help you can give me. The more detail the better.
Posted by eureka on Nov. 12 2005,06:44
To deityHe, he perhaps not perfect according to this: ” The more detail the better”…
Seems to me that you very well “now what you are doing”, so perhaps I don’t need to make it so detailed – hope you don’t mind?
Read this topic: < http://forum.ezbsystems.net/cgi-bin....;t=1083 >
YOU ONLY NEED TO CHANGE PATH IN AUTOEXEC.BAT AND CREATE DIFFERENT IMAGES.
Use >EasyBoot > Tools > ”Make floppy image” to create different bootable image files.
ATTENTION: Reduce length in folders and names to maximum eight letters. Not “WINME_OEM” use “WINMEOEM” and the same to every folder – reduce length on names to maximum eight letters or less. Do the same to names on images used in EasyBoot.
Example: To start setup of “WINME_OEM” name this image to “WINMEOEM.img” not “WINME_OEM.img” - to many letters. It’s possible to overcome this but then you may experience some other problems – so please, reduce length.
Examples on different Autoexec.bat down below here (copy text if you like).
Note: You do not need to make any changes in config.sys if using downloaded “bootmec”
--------------
@echo off
rem This starts win98SE setup
MSCDEX.EXE /D:tomato /L:X
PATH=a:\;a:\dos;x:\win98SE
setup.exe
------------------
@echo off
rem This starts win95OEM setup
MSCDEX.EXE /D:tomato /L:X
rem Note: I have reduced length on name from “WIN95_OEM” to “WIN95OEM”
PATH=a:\;a:\dos;x:\WIN95OEM
setup.exe
---------------
@echo off
rem This starts fdisk
fdisk
----------------
Use >EasyBoot > Tools > ”Make floppy image” to create this different bootable image files.
Note: in “Output file name” change name from “boot.img” to “win98SE.img” and/or “win95OEM.img” (no quotes) and same to the rest of different images. Note: eight letters or less on names!
Use command in EasyBoot as usual: run win98SE.img and/or run win95OEM.img and more choices in your menu, starting up different images.
About format in DOS, I suggest you use “standard image” (Windows 98 SE Bootdisk) and from A:\> manually use keyboard (“format C:”). It’s possible to set command-switch and automatically run “quick-format” from image at ones, but perhaps a little bit dangerous. I suggest that you do it “manually” using keyboard.
When creating ISO using EasyBoot. Only activate “Optimize” and nothing more!
Finally, paragon: Please show me the contents of autoexec.bat in paragon-image
This is my autoexec.bat in paragon:
------------
@echo off
echo Welcome to PTS-DOS
SHSUCDX /D:CD001
SET PATH=a:\
if exist restart.log set OPTIONS=/restart
mouse.com
start.exe %OPTIONS%
if "%OPTIONS%"=="/restart" del restart.log
shutdown /R
----------
eureka
Posted by eureka on Nov. 12 2005,07:01
To deityI forgot about Win95. If it doesn’t run using ”standard procedure”, read this: < http://forum.ezbsystems.net/cgi-bin....;t=1036 >
It depends on what version you are using.
eureka
Posted by deity on Nov. 12 2005,16:22
Thanks for the helpIt will take some time to read and make it work.
Will take your advice on making the changes to the folder names
Will read the other thread
| Quote |
| To deity I forgot about Win95. If it doesn’t run using ”standard procedure”, read this: < http://forum.ezbsystems.net/cgi-bin....;t=1036 > It depends on what version you are using. eureka |
I went to check the version where I have it installed.
It says its " Windows 95 v4.00.950 B "
any idea to which autoexec.bat to use with this version of Win95
Here is my Paragon "autoexec" info
| Code Sample |
@echo off echo Welcome to PTS-DOS SHSUCDX /D:CD001 SET PATH=a:\ if exist restart.log set OPTIONS=/restart mouse.com start.exe %OPTIONS% if "%OPTIONS%"=="/restart" del restart.log |
I added the last line in your autoexec.bat to see if that did the trick but it didnt.
Can I see Whats in you Paragon config.sys file?
Here is whats in my Paragon config.sys
| Code Sample |
files=20 buffers=10 stacks=0,0 break=on lastdrive=z switches=/F DEVICE=himem64.exe dos=low device=vide-cdd.sys /D:CD001 shell=command.com /E:256 /P break = ON |
Some Questions:
Are .*bif and *.IMA the same thing?
| Quote |
| Note: You do not need to make any changes in config.sys if using downloaded “bootmec” |
Where is this bootmec. I dont see it.
Can you explain what it is doing in this lines. Just so I can understand whats going on.
| Code Sample |
@echo off rem This starts win98SE setup <- Is this just telling you whats going to happen, A comment right MSCDEX.EXE /D:tomato /L:X <- Dont understand whats going on here PATH=a:\;a:\dos;x:\win98SE <- Dont understand whats going on here setup.exe <- I understand this Part |
| Code Sample |
MSCDEX.EXE /D:tomato /L:X rem Note: I have reduced length on name from “WIN95_OEM” to “WIN95OEM” <- understood :) PATH=a:\;a:\dos;x:\WIN95OEM <- Dont understand setup.exe <- understood |
One other question which is bugging me.
When you say use the command under Easyboot "run WINMEOEM.ima"
What is the default starting point when we use the "run WINMEOEM.ima" command in Easyboot.
Is it Disk1.
Does this mean when I type "run WINMEOEM.ima".
Is it saying go into Disk1\WINMEOEM\WINMEOEM.ima <- Can I put the WINMEOEM.ima in the same folder as WINMEOEM\
If so how do I tell EasyBoot Where "WINMEOEM.ima" is
I installed EasyBoot in C:\EasyBoot
I copied both folders "disk1\ezboot"
to my "D:\MultibootableOS's Win95-98SE-ME\disk1\ezboot"
Im using the default.ezb as template
So these is goig to be the new Dir Structure
D:\MultibootableOS's Win95-98SE-ME\disk1\
What Run command do I use in Easyboot?
DOS7_1_0
- DOS7_1_0.ima
ezboot
- all the Files that where there originally in there
Win95OEM
- WINMEOEM.ima
- all the Windows Install Files mentioned on first post
Win98SE
- WIN98SE.ima
- all the Windows Install Files mentioned on first post
WINMEOEM
- WINMEOEM.ima
- all the Windows Install Files mentioned on first post
WINMEUPG
- WINMEUPG.ima
- all the Windows Install Files mentioned on first post
PartMngr
- PartMngr.ima <- Thats why I asked if the .*bif and *.IMA the same thing?
- PartMngr.bif <- because these two files are the same size [ 1,440 KB]
D:\MultibootableOS's Win95-98SE-ME\disk1\ezboot <- Dose anything go in here other then what was in there originaly
If I have a couple of IMA DOS utility images where can I Put them so they run properly?
I wanted them to be in their own subfolder under the Disk1 Directory.
This is one of the Subfolder under Disk1
So its like this
D:\MultibootableOS's Win95-98SE-ME\disk1\DOS7_1_1\DOS7_1_0.ima
What command do i write when I try to create the "run DOS7_1_0.ima"
I dont think that will work because there is a subdirectory of DOS7_1_0 in Disk1 before the DOS7_1_1.ima
This DOS7_1_0.ima bootfloppy has USB, CDROM recognition and Mouse Support
Is theres a way to boot this DOS7_1_0.ima file with the options.
1 Go to DOS Prompt
2. Run Checkdisk
3. Run Fdisk
Thank you!
deity
Posted by eureka on Nov. 12 2005,17:47
To deitySorry, but I think you have mixed things up here and there.
Please read help in EasyBoot to get the basic stuff!
I don’t think it’s the right time to go any further at this point. Only some answers:
@echo off
rem This starts win98SE setup <- Is this just telling you whats going to happen, A comment right>> YES, it’s okay to delete this line!
MSCDEX.EXE /D:tomato /L:X <- Dont understand whats going on here >> Read this topic one more time: < http://forum.ezbsystems.net/cgi-bin/ikonboard.cgi?act=ST;f=1;t=1083 > and please in the same time use second link in topic to get more information.
PATH=a:\;a:\dos;x:\win98SE <- Dont understand whats going on here >> This is a very simple dos-command. It forces path in dos to point to folder win98SE (It’s really very basic stuff…)
setup.exe <- I understand this Part
-----------------
“What is the default starting point when we use the "run WINMEOEM.ima" command in Easyboot.
Is it Disk1”. NO!!! IT’S EASYBOOT\DISk1\EZBOOT Please read help in EasyBoot!
“Can I put the WINMEOEM.ima in the same folder as WINMEOEM” NO!!!!! Please read help in EasyBoot!
“If I have a couple of IMA DOS utility images where can I Put them so they run properly?” Yes probably, but we need to straight some things out before we go any further. Please, start with reading help in EasyBoot!
Anyway, about paragon:
In paragon autoexec.bat – please test with inserting this text in the very end: “reboot” (no quotes!)
Autoexec.bat in paragon should now look like this:
-------------
@echo off
echo Welcome to PTS-DOS
SHSUCDX /D:CD001
SET PATH=a:\
if exist restart.log set OPTIONS=/restart
mouse.com
start.exe %OPTIONS%
if "%OPTIONS%"=="/restart" del restart.log
reboot
--------------
Just curios…
This is importing for me: Did you start paragon from EasyBoot or did you use floppy itself?
See you tomorrow (it’s bedtime, my eyes are falling down…)
eureka
Posted by deity on Nov. 12 2005,21:45
| Quote |
| Please read help in EasyBoot to get the basic stuff! |
I did read the Manual first to get an idea, but its a little confusing. Thats one reason im asking questions. To fill in those holes.
| Quote |
| copy all boot image file needed to "C:\EasyBoot\disk1\ezboot", such as setup98.img, wxpsect.bin, to reduce additional file form CD root directory. |
So do boot files have to be with *.img extension and not IMA or PIF.
So they also have to be in the ezboot directory so thats why when you write run setup98.img its default starting to run is in the folder Ezboot and from when it runs the image file, it runs the autoexec.bat file which proceeds to go to the root disk1 folder to go into for example the Win98 folder to run setup.exe to begin the installation .
| Quote |
| MSCDEX.EXE /D:tomato /L:X <- Dont understand whats going on here >> Read this topic one more time: |
Your refering to this
| Code Sample |
| Quote: ” what does mscdex.exe /D:tomato /L:X mean and is it really supposed to be tomato” “tomato” is just a “name substitute”. You may call it “potatoes” or “Pluto” or whatever. Note: Same name must be in “name substitute” in config.sys file. No need to change this. |
| Code Sample |
“What is the default starting point when we use the "run WINMEOEM.ima" command in Easyboot. Is it Disk1”. NO!!! IT’S EASYBOOT\DISk1\EZBOOT Please read help in EasyBoot! |
Understood. After reading the Help it was not made very clear. Thats why I asked.
| Quote |
| PATH=a:\;a:\dos;x:\win98SE <- Dont understand whats going on here >> This is a very simple dos-command. It forces path in dos to point to folder win98SE (It’s really very basic stuff…) |
PATH= <-What does PATH do, Whats its purpose
a:\ <- Im thinking it goes into A drive
; <- From reading another Thread I think is this a separator
between multiple commands
a:\dos <- Whats it doing here
x:\win98SE <- Where did we get the x:
| Quote |
| “Can I put the WINMEOEM.ima in the same folder as WINMEOEM” NO!!!!! Please read help in EasyBoot! |
So it has to go into the EZBOOT folder.
After finishing the layout. I was thinking of moving all files back to C drive EASYBOOT\DISk1\EZBOOT
but is that mandatory.
Or can i just create the D:\MultibootableOS's Win95-98SE-ME\EASYBOOT\DISk1\EZBOOT
I have the original ezboot files in the Ezboot folder. For example the default.ezb and the rest of the files Im working on to make the interface. Would that not work. Since Im still using the same directory structure.
| Quote |
| “If I have a couple of IMA DOS utility images where can I Put them so they run properly?” Yes probably, but we need to straight some things out before we go any further. Please, start with reading help in EasyBoot! |
I read the manual! Thats what confused me. I think im still confused.
| Quote |
| Just curios… This is importing for me: Did you start paragon from EasyBoot or did you use floppy itself? |
No im testing it using the Floppy itself. I havent tried making an ISO yet. Im working on the Layout and the Background Image and the text aswell.
The reboot at the end of the Paragon autoexec.bat at the end of the text file did the job. Very cool!
Forgot that you can use the tools to transform an IMA image to a *.img file.
All it creates is an empty Image when I use the IMA source to seed Image.
I created an empty 1440 and a 2280 img file but I cant Put any files into it. Im usig Winimage to open the img file. And its empty. Even though the Seed is full of files.
Thanks for your help!
Posted by eureka on Nov. 13 2005,07:13
To deityI do agree with you that help in EasyBoot is far from any ”masterpiece”, it has its limits.
Quote: “I think im still confused”. You are not alone…. When I started using EasyBoot I was more than confused. I ended up “pulling out my hair” – Well I’m not bold yet, but I’m working on it….
Anyway… *.bif is what extension that’s being used in programs like UltraIso. *.bif-file with size 1,44 Mb (floppy-size) is basically the same as *ima or *.img.
This means that images with “floppy-size” (created from “normal” floppy-size) could have extension: *.bif, *.ima and *.img they are al used in the same way.
Quote: “All it creates is an empty Image when I use the IMA source to seed Image.
I created an empty 1440 and a 2280 img file but I cant Put any files into it. I’m using Winimage to open the img file. And its empty. Even though the Seed is full of files.”
You only use “seed image” to get bootsector. Then use winimage or UltraIso to inject files. Read this topic: < http://forum.ezbsystems.net/cgi-bin....1;t=473 >
Quote: “So they also have to be in the ezboot directory so thats why when you write run setup98.img its default starting to run is in the folder Ezboot and from when it runs the image file, it runs the autoexec.bat file which proceeds to go to the root disk1 folder to go into for example the Win98 folder to run setup.exe to begin the installation .” Correct!
Quote: “x:\win98SE <- Where did we get the x:” >> From the line above: MSCDEX.EXE /D:tomato /L:X
Note: “tomato” is just a funny nickname. In config.sys this line is set to same: “DEVICE=cd1.SYS /D:tomato”
You can name it “pluto”, “potatoes”, “lassie” or “europe” or whatever. But same “nickname” must be set in Autoexec.bat.
Syntax for path:
PATH;
PATH [d:]path[;][d:]path[...]
Purpose: Sets or displays directories that will be searched for programs not in the current directory. PATH tells DOS which directories should be searched for external commands after DOS searches your working directory. DOS searches the paths in the order specified in the PATH command. Example in autoexec.bat: PATH=a:\;a:\dos;x:\WIN95OEM
Dos “jumps” to directory WIN95OEM in unit X:\
Unit X (first CD/VDV-reader-unit) is forced to have letter X bye this dos-command: “MSCDEX.EXE /D:tomato /L:X” It’s possible to fix this using other dos-commands or using a small dos-program like “findCD”.
Note: I like to make things straight on combined with a way that I now is 100% waterproof.
However, I think you need to learn more about DOS. This isn’t the right forum to discuss this.
You will run in to a lot of different dos-commands later on. Take a look in autoexec.bat in paragon and notice that path isn’t changed because paragon is not calling on any different harddisk/CD/DVD-unit, it uses only path to floppy (SET PATH=a:\). EasyBoot runs floppy-images in “dos emulated mode”. This means that it is easy to use images in EasyBoot.
Nice that you solved your problems with paragon floppy with that command I suggested.
Start “EasyBoot >>Tools >>Make Floppy Image” and make a new image using paragon-floppy.
Note that deafault location is EasyBoot\disk1\ezboot for this new image.
Then try to make a menu-start in EasyBoot for this new image (and finally create ISO) and see if you can make it run? Note: default name when creating image in “EasyBoot >>Tools >>Make Floppy Image” is “boot.img” change it to paragon.img and set command in menu to: run paragon.img
Quote: “I have the original ezboot files in the Ezboot folder. For example the default.ezb and the rest of the files Im working on to make the interface. Would that not work. Since Im still using the same directory structure.”
What’s the point with moving stuff around? You need to change path on a lot of stuff inside EasyBoot. I suggest you use original installation path ([C:]).
I have noticed that you made some progress, and I think it’s only a matter of time to you get things right, and finally create your first ISO using EasyBoot.
eureka
Posted by deity on Nov. 13 2005,17:25
I have finished the a beta of my layout for the CD im creating.I used fireworks to create the layout and save it into a 256 color BMP 8 File. I was getting error meassage when trying to use it. So, I went to search for more info at this forum and found a suggestion where you can go into the Easyboot Options - Configuration - ScreenMode - 256 Color [8bit] and then tryied using the one I made and it worked. The background worked.
It seems Easyboot uses only the things that are contained within the disk1 folder when creating an ISO. I opened the ISO it created and it contained the 4 folders I had in the disk1 Folder for testing.
These are all floppies
Dell <- Having Problems with this one working
It has a Ghost image for backing up my drive
It launches the DOS options Menu, but when
I click one the options it says restore ....
It launches but it can reports
"CDR103: CDROM not High Sierra or ISO-9660 format reading drive T Abort, Retry, Fail?
But When I use test the ISO again, And i select one of the options it boots up with ghost just fine.
DOS7_1_0 <- Seems to lauch using the Menu created
ezboot
PartMngr <- Seems to lauch using the Menu created
I have also messed with layou using the Eazyboot. Its not so easy to get the blending to match. I have to experiment some more to try to get the right effect.
| Quote |
| Anyway… *.bif is what extension that’s being used in programs like UltraIso. *.bif-file with size 1,44 Mb (floppy-size) is basically the same as *ima or *.img. You only use “seed image” to get bootsector. Then use winimage or UltraIso to inject files. Read this topic: < http://forum.ezbsystems.net/cgi-bin....1;t=473 > |
So does that mean that when I have the bootsector seeded into the new img, then I can extract the IMA contents and inject them back to the new img that has the IMA bootsector. RIght!
Tested my theory and it works.
| Quote |
| Syntax for path: |
Thanks for the explanation. It helps in better understanding whats going on. That way, I can thinker with it if I need to.
| Quote |
| However, I think you need to learn more about DOS. This isn’t the right forum to discuss this. |
| Quote |
| Start “EasyBoot >>Tools >>Make Floppy Image” and make a new image using paragon-floppy. Note that deafault location is EasyBoot\disk1\ezboot for this new image. Then try to make a menu-start in EasyBoot for this new image (and finally create ISO) and see if you can make it run? Note: default name when creating image in “EasyBoot >>Tools >>Make Floppy Image” is “boot.img” change it to paragon.img and set command in menu to: run paragon.img |
These two are working if I keep them in the ezyboot folder using the run command
DOS7_1_0.img 1,440 KB
PartMngr.img 2,880 KB
Im having problems with this one
DELL_NRU.img 2,880 KB
The only thing visible when you use UltraISO to open the ISO is the ghost.exe file which is 1,366 KB in size
- So what i did was Open the ISO with UltraISO.
- Saved the *.bif boot file. I contains the autoexec.bat file and other files. In total it saves into a 1,440 KB bif file.
- I opened the bif file in UltraISO and saved it into a IMA file.
- I used Easyboot to create a 2,880 KB boodisk img using the seed from the IMA file.
- I tried two things after that
- 1. I opened the 2,880 KB IMG file in Winimage and inserted the ghost.exe into it. Since it has the boot info from when I seeded into it. I should have booted ok. But it didnt. I get the message:
Invalid sytem disk
Replace the disk and then press any key
If I press any key, It reboots the system. Then im back in the easy boot menu i created.
- 2. I also opened the IMA file that was the bif bootfile before and extracted its contents out and then injected them to the 2,880 KB IMG file with the Ghost.exe file. This time it recognize the cdroms and booted into the selection options menu. But once I select a menu option it seems to launch just fine but then get the error message I mentioned above:
"CDR103: CDROM not High Sierra or ISO-9660 format reading drive T Abort, Retry, Fail?
But When I use test the ISO again, And i select one of the options it boots up with ghost just fine.
| Quote |
| I have noticed that you made some progress, and I think it’s only a matter of time to you get things right, and finally create your first ISO using EasyBoot. |
Have to work on the blending of the selectable options. they look blury.
Ill be back later I have to go try to fix a friends computer. He has some viruses and trojans. From the symptons his reporting.
Thanks for all you help!
Posted by eureka on Nov. 14 2005,04:17
To deityQuote: ”So does that mean that when I have the bootsector seeded into the new img, then I can extract the IMA contents and inject them back to the new img that has the IMA bootsector. RIght!” Correct!
Quote: ” Im having problems with this one
DELL_NRU.img 2,880 KB
The only thing visible when you use UltraISO to open the ISO is the ghost.exe file which is 1,366 KB in size”
“use UltraISO to open the ISO” What I can figure out here is that this is a ISO-file containing ghost in the root of ISO-file and that you then saved bootrecord as *.bif Correct? If this is the case, you have to copy ghost.exe to the root (EasyBoot\disk1) and then use saved *.bif as usual in EasyBoot: “run *.bif”. Because path to ghost.exe in Autoexec.bat in *.bif is probably pointing to the root of CD/DVD-unit. About Ghost:
If still having problem to start Ghost, please use this guide:
Download bootfile: “Windows Me Custom, No Ramdrive” from here: < http://www.bootdisk.com/bootdisk.htm >
Use right mouse button on “bootmec.exe” and choose to “Extract to bootmec\” (you need zip-program of some kind installed. I prefer WinRAR). You now have a new folder named “bootmec”. Open folder and locate “bootmec-img”. We are going to edit autoexec.bat in this one. Use WinImage (or UltraIso) and extract Autoexec.bat to some temporary folder (use folder bootmec to make it easy). Open autoexec and put in this text (delete other text):
@echo off
MSCDEX.EXE /D:tomato /L:X
PATH=a:\;a:\dos;x:\
ctmouse.exe
ghost
reboot
------------------
Save autoexec.bat back to bootmec.img
Note: To easy up next step, I suggest you create several temporary folders, because we need to extract and inject stuff from images and compressed files from here and there.
Start EasyBoot>>Tools>>Create new Image >> set Image size to: 2880 >> and use bootmec.img as “Seed Image” >>when saving this new image, rename file from “2880.img” to “ghost.img” (no quotes). Make sure you save image to EasyBoot\disk1\ezboot
Now open this “oversized” ghost.img and inject ghost.exe followed bye injecting every file from bootmec.img as well. End it up with injecting “reboot.com” from EasyBoot\ resource.
Finally, we need mouse support. Download zip-file from here: < http://cutemouse.sourceforge.net/program/ctm20a4.zip >
Extract “ctmouse.exe” from zip-file and inject it to “ghost.img”.
As I pointed out in the beginning – use temporary folders to make it easier to separate files and images.
You should now have a new Image in EasyBoot\disk1\ezboot named ghost.img with size 2880.
Use command in EasyBoot as usual: “run ghost.img” (no quotes).
-----------------------------------------------------------------------------------
Some notes…
Quote: “So what i did was Open the ISO with UltraISO.
- Saved the .bif boot file. I contains the autoexec.bat file and other files. In total it saves into a 1,440 KB bif file.
- I opened the bif file in UltraISO and saved it into a IMA file.”
No need to rework *.bif.
You can use this one (*.bif) as it is in EasyBoot (run *.bif). Note: use extension “bif” as it is!
Quote: ” >>…go into the Easyboot Options - Configuration - ScreenMode - 256 Color [8bit] and then tryied using the one I made and it worked. The background worked”
Yes you have to set screen mode (colours and size) to the same as your choice of background picture, I always use 256 colours. Have never experied any troubles using those colours – but you never now…
---------------------------
Links on your request:
< http://www.computerhope.com/msdos.htm >
< http://www.freedos.org/ >
< http://www.opus.co.tt/dave/ >
< http://www.pc-tools.net/dos/dosutils/ >
A1.zip (A1 Dos Utilities Shareware).
Regards eureka
Posted by euraka on Nov. 14 2005,08:28
To deitySorry, forgot to insert link according to A1-dosutilities, here it is:
< http://www.ers.kestar.com.au/a1.zip >
eureka
Posted by deity on Nov. 14 2005,22:37
Easyboot has a run reboot command. Is there one that will shutdown?| Quote |
| “use UltraISO to open the ISO” What I can figure out here is that this is a ISO-file containing ghost in the root of ISO-file and that you then saved bootrecord as *.bif Correct? If this is the case, you have to copy ghost.exe to the root (EasyBoot\disk1) and then use saved *.bif as usual in EasyBoot: “run *.bif”. |
I didnt know you could run .bif files. I got the bif file and then resaved it in to a IMG. Just to keep things tidy in the Easyboot folder.
| Quote |
| Because path to ghost.exe in Autoexec.bat in *.bif is probably pointing to the root of CD/DVD-unit. |
Your right. I moved the ghost.exe to the disk1 folder and reran the Test.
It works! The menu comes up and the ghost program runs. Ah! yeah!
You know what command I should put in autoexec.bat to run ghost.exe from the folder disk1\Dell\GHOST.EXE
I would like to keep the directory structure a little tiddy.
| Quote |
| About Ghost: If still having problem to start Ghost, please use this guide: Download bootfile: “Windows Me Custom, No Ramdrive” from here: < ]http://www.bootdisk.com/bootdisk.htm |
No problems so far with the suggestion you gave above.
I have a question about the recomendation. Whats the "Windows Me Custom, No Ramdrive". Mainly the No Ramdrive thing. When would it be good to use.
I will also try to follow the rest of the instrcutions to get mouse support because at this time it has no support to it.
I preferr to use Winrar also. Small and usefull app.
I have to use the original because it has other options I need.
How can I add mouse support to my original bif or IMA that I have now working?
I will go to the sites you recommended to learn more about DOS commands.
One thing ive noticed is that if you click outside the hot area of the selectable items with the newly created easyboot iso image that when you run it and then move the mouse outside the hot areas it will launch one of the IMG files you have as an option. Is this a an expected bug from easyboot.
Thanks for the help. Without it. I would probably had given up on this product.
Now I will try to make the Win95 - Me IMG files to work. I ll right back to see how that goes.
Thanks!
Posted by eureka on Nov. 15 2005,03:39
To deityQuote: “Easyboot has a run reboot command. Is there one that will shutdown?”
Haven’t been testing switches according to resources in EasyBoot. I use a small dos utility (Shutdown.com).
Download Shutdown.com from here: < http://www.opus.co.tt/dave/shut12.zip >
Quote from author: “The reboot option works on any modern personal computer”.
[Comments from eureka: I have never expired any problems so far. I’ll say it works from computer manufactured 1997 and later!]
Syntax: [shutdown.com /R] (reboots computer) - [shutdown.com /S] (shutdown computer) - [shutdown.com / C] (to cancel and return to DOS – a kind of substitute for ESC-button. You probably won’t use this one).
Inject Shutdown.com (0,45 kb) to any image and, if wanted, in the end of autoexec.bat insert Shutdown.com.
Example autoexec.bat running Ghost:
-------------
@echo off
Ghost
shutdown /R
-------------
When you quit Ghost computer reboots.
-------------
If used in EasyBoot: Put shutdown.com in EasyBoot\disk1\ezboot folder. Use command “run shutdown” in EasyBoot-menu. This shutdown computer very quick.
Quote: “Mainly the No Ramdrive thing”. Ramdrive is a utility that creates a kind of hard disk. It’s not any physical hard disk (mechanical stuff). Instead program uses a part of the ram memory to set up this “hard disk” (it disappears when you reboot). In most cases we don’t need ramdrive. I use this boot floppy because it is so applicable in many ways.
------------------------------
Quote: “to get mouse support…” You can use ctmouse.exe (cutemouse). Download here: < http://cutemouse.sourceforge.net/program/ctm20a4.zip > or use mouse from your own paragon-image. Extract mouse.com from paragon-image and use this in any image. Set command “mouse.com” in autoexec.bat. Example showing ghost:
@echo off
mouse.com
Ghost
shutdown /R
----------------------------
example showing autoexec.bat in paragon image:
@echo off
echo Welcome to PTS-DOS
SHSUCDX /D:CD001
SET PATH=a:\
if exist restart.log set OPTIONS=/restart
mouse.com
start.exe %OPTIONS%
if "%OPTIONS%"=="/restart" del restart.log
shutdown /R
-----------------------------------
Note: You need to start mouse before application is being initiated.
Attention: This only generates mouse support to PS/2 you don’t get mouse support according to USB.
Download USB-mouse support from here: < http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/UHCI.EXE >
Rename file “Uhci.exe” to mouseusb.exe (more convenient, wouldn’t you say?). Use it in the same way as mouse.com. It doesn’t matter if you put mouseusb.exe before or after mouse.com in Autoexec.bat
Example showing Ghost:
-------------------
@echo off
mouse.com
mouseusb.exe
Ghost
shutdown /R
------------------
This generates mouse support to mouse connected to PS/2 and USB as well.
---------------------------------------------------------
Quote: “……and then move the mouse outside the hot areas it will launch one of the IMG files you have as an option”. Well it’s the same to me, so I presume it’s the normal case. Nobody is perfect, even not “Mr EasyBoot”.
Regards eureka
Posted by eureka on Nov. 15 2005,04:06
"If used in EasyBoot: Put shutdown.com in EasyBoot\disk1\ezboot folder. Use command “run shutdown” in EasyBoot-menu. This shutdown computer very quick". Attention: Must bee: "run shutdown.com".
eureka
Posted by deity on Nov. 15 2005,18:14
Thanks for the info. Will try it out . I will try to ge the Win98 and ME to Work, then I will focus on Win 95, since it seems it will give more resistence. lol!Adding PS/2 adn USB mouse support to DOS is very cool.
You know if there is a way to change image when hovering over selection. Similar to the text effect.
Do you know the required Files int
\ezboot
folder. I have alot of things I might not need to include into CD. What does it need in there to work.
| Quote |
| You know what command I should put in autoexec.bat to run ghost.exe from the folder disk1\Dell\GHOST.EXE I would like to keep the directory structure a little tiddy. |
| Quote |
| Quote: “……and then move the mouse outside the hot areas it will launch one of the IMG files you have as an option”. Well it’s the same to me, so I presume it’s the normal case. Nobody is perfect, even not “Mr EasyBoot”. |
Hope they fix that in a new release.
| Quote |
| Attention: Must bee: "run shutdown.com". |
Tried it and it works. Very fast shutdown.
Thanks!
Posted by deity on Nov. 15 2005,23:10
I tried getting the Win98Se to start installation. I was able to go into autoexec and type the path mentioned. The installation start and begins installation. Bad thing is that for some reason it does not complete all the way. It gives error messages. So what i did was boot into a boodisk that can read long file names and I have noticed that for some reason the Programs folder is named "PROGRA~1". Im thinking Easyboot messed up the iso it created. Also noticed all other files or folders that are longer then eight characters has been truncated similar to "PROGRA~1". 
When I create the ISO.
1. In option I have the Optimize, DOS(8.3), and Joliet deselected.
2. I tried with the Joliet selected and same thing happens.
Can you post the way to input the format command.
For example format c: or if I need to adjust it to two drives or partitions.
I just read that you can put a pasword to Menu - Menu Text. So that should be OK, because a password needs to be typed in to make sure they are ready to actually format and not accidentally format by mistake. What do you think? I tested it and it works.
Posted by eureka on Nov. 16 2005,04:07
To deityQuote: “You know if there is a way to change image when hovering over selection. Similar to the text effect”. Sorry, no such option accessible yet (to my knowledge). Note: You should direct this kind of questions to the moderator “XOBEN” in here: < http://forum.ezbsystems.net/cgi-bin....=SF;f=6 >
Quote: “In option I have the Optimize, DOS(8.3), and Joliet deselected.” This is the correct choice in this case. Be sure to not have this options activated. Note: “Optimize” could work but not DOS(8.3) and/or Joliet.
Can’t figure out what you did to get truncated names on files? I have never seen any windows_9x with filenames longer than eight letters? They look like this: Win98_58.cab , W98setup.bin, Dossetup.bin, Oemsetup.exe or Channels (Channels is a folder). What kind of win98Se is this you are using???
Please check that folder holding win98SE-files in EasyBoot\disk1 don’t have a name like windows98SE. That’s to many letters (eight letters or less please).
---------------------------------------------------------
Quote: “For example format c: …………”
Quick format using “format.com” (related to “standard” boot floppy generated bye win9x/Me) can only be used if you initial have made a full format (takes a while to do). From this point its possible to “quick-format” using format.com.
Syntax: format C: /Q
Note: To get all syntax, start win9x rescue-floppy and at prompt write this command: format /?
And then hit enter. This gives you switches accordingly to format.com.
Example in Autoexec.bat:
Format c: /Q
This runs quick format on [C:]
Create image and name it to something like format.img (or whatever) and in EasyBoot as usual: run format.img (or if it is *.ima run format.ima)
Note: Win95B/Win98/Win98SE/WinMe rescue-floppy uses FAT32 (fdisk.com creates FAT32).
Attention: Win95a rescue-floppy (“golden” version) uses FAT16! Don’t mix original Win95a-floppy with later versions (Win95b and later versions).
-----------------------
Finally, quote: “………..or if I need to adjust it to two drives or partitions”.
This has nothing to do with format. This is done with fdisk.com. To my knowledge - there is no switches to automatic this. You have to run it manually.
You do have paragon – this is a nice and powerful tool. Why not use paragon?
Attention: Be careful about this format and fdisk issues. It’s very easy to screw things up.
Quote: “……because a password needs to be typed in to make sure they are ready to actually format and not accidentally format by mistake”. As I pointed out, be careful with this option: “automatic quick format”.
eureka
Posted by deity on Nov. 16 2005,19:42
| Quote |
| Quote: “You know if there is a way to change image when hovering over selection. Similar to the text effect”. Sorry, no such option accessible yet (to my knowledge). Note: You should direct this kind of questions to the moderator “XOBEN” in here: [URL=http://forum.ezbsystems.net/cgi-bin....=SF;f=6] |
ok!
| Quote |
| You do have paragon – this is a nice and powerful tool. Why not use paragon? |
I wanted to have both options.
| Quote |
| Quote: “In option I have the Optimize, DOS(8.3), and Joliet deselected.” This is the correct choice in this case. Be sure to not have this options activated. Note: “Optimize” could work but not DOS(8.3) and/or Joliet. Can’t figure out what you did to get truncated names on files? I have never seen any windows_9x with filenames longer than eight letters? They look like this: Win98_58.cab , W98setup.bin, Dossetup.bin, Oemsetup.exe or Channels (Channels is a folder). What kind of win98Se is this you are using??? Please check that folder holding win98SE-files in EasyBoot\disk1 don’t have a name like windows98SE. That’s to many letters (eight letters or less please). |
Ill leave the format thing off then. It might be too dangerous. .???
Pic of the dir after installing Win98SE
The floppy im using to see the C: has LFN support.
Disk Directory
Posted by eureka on Nov. 17 2005,03:53
To deityPlease test with WinMe and Win95 to see what results this gives.
How and with what tools did you made partition and format on [C:] (using Wmvare?).
Repartition completely and format. Please test with using paragon (I think you can use “Quick format” in paragon). Then reinstall Win98SE and feedback result to me.
I now that in very rare cases you get this truncated stuff. Can’t remember when and where I have seen this happened. But I do have seen it before!
Anyway, test repartition and also with test of win95 and winme as well.
Regards eureka
Posted by deity on Nov. 17 2005,20:25
Moved Win98 to another folder and tried disk1\ezboot\WinMeOEM.IMG and disk1\WinMeOEMI get this error.
AUTOEXEC.BAT
| Code Sample |
| @echo off MSCDEX.EXE /D:tomato /L:R PATH=a:\;a:\dos;x:\WinMeOEM setup.exe |
I used both Fdisk and Partition Manager.
I used Partition Manager the first time then installed windows98. I partition the drive in Fat32.
When I installed Win98 it was truncated, so
I then tried Fdisk and format commands and the same thing happened.
AUTOEXEC.BAT for Win98SE
| Code Sample |
| @ECHO OFF set EXPAND=YES SET DIRCMD=/O:N set LglDrv=27 * 26 Z 25 Y 24 X 23 W 22 V 21 U 20 T 19 S 18 R 17 Q 16 P 15 set LglDrv=%LglDrv% O 14 N 13 M 12 L 11 K 10 J 9 I 8 H 7 G 6 F 5 E 4 D 3 C cls call setramd.bat %LglDrv% set temp=c:\ set tmp=c:\ path=%RAMD%:\;a:\;%CDROM%:\ copy command.com %RAMD%:\ > NUL set comspec=%RAMD%:\command.com copy extract.exe %RAMD%:\ > NUL copy readme.txt %RAMD%:\ > NUL :ERROR IF EXIST ebd.cab GOTO EXT echo Please insert Windows 98 Startup Disk 2 echo. pause GOTO ERROR :EXT %RAMD%:\extract /y /e /l %RAMD%: ebd.cab > NUL echo The diagnostic tools were successfully loaded to drive %RAMD%. echo. LH %ramd%:\MSCDEX.EXE /D:mscd001 /L:%CDROM% echo. cls echo Now installing Windows 98 SE echo. echo Loading... path=%RAMD%:\;a:\;%CDROM%:\Win98SE setup.exe echo. GOTO QUIT :QUIT echo To get help, type HELP and press ENTER. echo. rem clean up environment variables set CDROM= set LglDrv= |
Posted by eureka on Nov. 18 2005,04:47
To deityThis is what you have in Autoexec.bat:
MSCDEX.EXE /D:tomato /L:R
PATH=a:\;a:\dos;x:\WinMeOEM
setup.exe
I have earlier instructed you to have this line: MSCDEX.EXE /D:tomato /L:X
But you use this: MSCDEX.EXE /D:tomato /L:R This is wrong path (/L:R) to CD/DVD-unit.
Because in Path you have: “PATH=a:\;a:\dos;x:\WinMeOEM” . As you can notice your self letter: X
This is the right Autoexec.bat:
@echo off
MSCDEX.EXE /D:tomato /L:X
PATH=a:\;a:\dos;x:\WinMeOEM
setup.exe
- End of script -
Please test this WinMeOEM and feedback
Note: Use similar image to win98SE (same simple autoexec.bat as for winmeoem). Only change path in autoexec.bat to:
PATH=a:\;a:\dos;x:\win98SE
Regards eureka
Posted by deity on Nov. 20 2005,13:07
This is what i did to try to get Windows Me OEM to start the setup.1. Created a new Virtual Machine.
2. Chose the Windows ME option that i was going to install WinMeOEM.
3. Used Partition Manager to create the drive and format it into FAT32.
4. Using the extracted "bootmec.IMA" from the bootmec.exe [Windows Me Custom, No Ramdrive]as the base for the boot image and opening it in UltraISO to save it into WinMeOEM.img and then changing the AUTOEXEC.BAT to
| Code Sample |
| @echo off MSCDEX.EXE /D:tomato /L:X PATH=a:\;a:\dos;x:\WinMeOEM setup.exe |
Windows ME OEM Started the Installation OK! Lets see if it does the corrupt files thing.
The first reboot when installing came up.
Now its setting up hardware.
Restarted the second time. It seemed to start ok but then I get the same message i was getting with the Win98se installtion. "Disk Write Error" and then "Windows Protection Error. You need to restart your computer. System halted".
For some reason the files greater then 8 characters are being truncated. As you can see in the last picture. I dont think other people have tested there creations all the way thru.
You think it suppose to have Long file name support or something in order for the setup.exe to go ok.
I dont know what else to do.
For Win98Se Installation I also tried
1. Created a new Virtual Machine.
2. Chose the Windows 98 option that i was going to install Win98SE.
3. Used Partition Manager to create the drive and format it into FAT32.
4. Using the extracted "bootmec.IMA" from the bootmec.exe [Windows Me Custom, No Ramdrive]as the base for the boot image and opening it in UltraISO to save it into Win98SE.img and then changing the AUTOEXEC.BAT to
| Code Sample |
| @echo off MSCDEX.EXE /D:tomato /L:X PATH=a:\;a:\dos;x:\win98SE setup.exe |
I ran the Windows98 Installtion from the Easyboot Menu and I get the following message.
So the installation never starts. It sends me back to dos prompt.
Posted by eureka on Nov. 20 2005,13:49
To deityQuote: “I don’t know what else to do”. Neither do I?
I really don’t understand what’s goes wrong here? This has nothing to do with how you start setup. It’s something else. I’ll say it’s out of my “control”.
I refer to this: < http://forum.ezbsystems.net/cgi-bin....;t=1083 >
Note: blaze85 used the same instruction (and so do I) and no problems occurs what so ever.
Quote: “I don’t think other people have tested there creations all the way thru”.
Well I do use this without any problems what so ever. I use it sometimes when I’m creating boot-folder to different NT-system. To manage this, I install win98 or WinMe.
As I pointed out. This has nothing to do with tutorial it self. Sorry to say – I can’t put my finger on what kind of mismatch this is.
Where have you found these strange win9x-systems? At least they seem to behave a little bit strange in some manners. And I can’t find out how or why?
eureka
Posted by deity on Nov. 20 2005,14:26
| Quote |
| Where have you found these strange win9x-systems? At least they seem to behave a little bit strange in some manners. And I can’t find out how or why? |
I got them from there original CD. I just Created an ISO and then Extrated the Win98 folder to use with Easyboot. I have no trouble when I used the CDs normally when I install window98 SE or Windows ME. I try to test the same install on a MS Virtual Machine and see if I get the same error message.
Posted by eureka on Nov. 20 2005,14:29
To deityThat message: Setup found a compressed volume….
You can press ESC on keyboard or download ”Windows 98 Custom, No Ramdrive” from < http://www.bootdisk.com/bootdisk.htm >
Use this instead of WinMe –version of image. In this way you don’t need to press ESC on keyboard. It’s depends on what DOS-version you have in Win98-folder. Why not use the exact compatible images according to your different win9x-system? Download from < http://www.bootdisk.com/bootdisk.htm >
However I don’t think it solves problems with truncated names. But sure worth a try….
Regards eureka
Posted by eureka on Nov. 20 2005,14:43
To deityPlease test following on Win98SE.
Change Autoexec.bat to this and use image ”Windows 98 Custom, No Ramdrive”:
MSCDEX /D:MSCD001 /L:X
PATH=a:\;a:\dos;x:\
c:
mkdir option
x:
cd win98SE
xcopy *.* c:\option
c:
cd option
setup.exe
- end of script -
Test as usual. Make a quick format and install Win98SE in this way.
Note: This is only to see if we can stop truncated files.
Regards eureka
Posted by deity on Nov. 20 2005,15:07
Ok! will try that out. Will write results.
Posted by deity on Nov. 20 2005,15:26
This is what i get using the autoexec | Code Sample |
@echo off MSCDEX /D:MSCD001 /L:X PATH=a:\;a:\dos;x:\ c: mkdir option x: cd win98SE xcopy *.* c:\option c: cd option setup.exe |
I used the Windows 98 SE Custom, No Ramdrive as bootimage.
Posted by eureka on Nov. 20 2005,15:42
To deitySorry wrong path (BANANA is the right one if using ”Windows 98 Custom, No Ramdrive”).
Change Autoexec.bat to this and use image ”Windows 98 Custom, No Ramdrive”:
MSCDEX /D:BANANA /L:X
PATH=a:\;a:\dos;x:\
c:
mkdir option
x:
cd win98SE
xcopy *.* c:\option
c:
cd option
setup.exe
- end of script -
Regards eureka
Posted by deity on Nov. 20 2005,15:58
That worked. It copied ok and installation is running. Ill see if the same thing happens on this one.
Posted by deity on Nov. 20 2005,16:29
Darn the same error. " DIsk Write error".It seems to install fine but when Windows try to run for the first time you get this error.
Ill have to find My Virtual PC CD and install it to run this test on it and see if I will get the same error.
Posted by eureka on Nov. 20 2005,16:35
To deityQuote: ”Ill have to find My Virtual PC CD and install it to run this test”.
Please do so and feedback result.
Regards eureka
Posted by deity on Nov. 20 2005,19:23
Success on both installations. Windows98Se Retail and Windows Me OEM. Using Virtual PC. I wonder what is happening to VMware that its not working on it. I probably have to go back to Vmware and test it some more.Now I just need to get Windows ME Upgrade to work and WIndows 95. I'll also test in Virtual PC.
Here is some screenshots of the results. It takes to long under Virtual PC to install the OS's.
Windows ME OEM Autoexec
| Code Sample |
| @echo off MSCDEX.EXE /D:tomato /L:X PATH=a:\;a:\dos;x:\WinMeOEM setup.exe |
Autoexec of WIndows 98 SE
| Code Sample |
| @echo off MSCDEX.EXE /D:banana /L:X PATH=a:\;a:\dos;x:\win98SE setup.exe |
Posted by eureka on Nov. 21 2005,02:30
To deityExcellent! As I earlier pointed out: “This has nothing to do with how you start setup. It’s something else.”
There is some lack according to win95 setup. If you after the first reboot (to continue setup process), receive a message typical that Windows don’t recognize CDROM drive (setup requests CDROM drive "D:\WIN95"). Well if that’s the case, you need to use a different way to setup.
Test using: ”Windows 98 Custom, No Ramdrive” to setup win95 as well, just to see how it works.
Change Autoexec.bat to have this:
@echo off
MSCDEX /D:BANANA /L:X
PATH=a:\;a:\dos;x:\
c:
mkdir option
x:
cd win95OEM
xcopy *.* c:\option
c:
cd option
setup.exe
- end of script –
As you can notice in Autoexec.bat, I create a folder on [C:] with the name “option” (“mkdir option”). I then start installation (“setup.exe”) from there. What’s the point with this? There are two reasons for this.
1. If you later install some hardware (or software) and support is needed from Win95-CD, well CD is not necessary any more, because install path is now [C:\option] so files and support is easily collected from this install directory (option) instead of CD.
2. No problems when computer reboots and continue installation.
Note: You don’t need this arrangement in Win98 or WinMe, because these two systems create a folder named “option” inside Windows folder.
Quote: “Edited by deity on Nov. 21 2005,00:28”. He, he don’t you ever sleep?
Regards eureka
Posted by deity on Nov. 21 2005,20:45
| Quote (Guest @ Nov. 21 2005,07:30) |
| To deity Excellent! As I earlier pointed out: “This has nothing to do with how you start setup. It’s something else.” There is some lack according to win95 setup. If you after the first reboot (to continue setup process), receive a message typical that Windows don’t recognize CDROM drive (setup requests CDROM drive "D:\WIN95"). Well if that’s the case, you need to use a different way to setup. Test using: ”Windows 98 Custom, No Ramdrive” to setup win95 as well, just to see how it works. Change Autoexec.bat to have this: @echo off MSCDEX /D:BANANA /L:X PATH=a:\;a:\dos;x:\ c: mkdir option x: cd win95OEM xcopy *.* c:\option c: cd option setup.exe - end of script – As you can notice in Autoexec.bat, I create a folder on [C:] with the name “option” (“mkdir option”). I then start installation (“setup.exe”) from there. What’s the point with this? There are two reasons for this. 1. If you later install some hardware (or software) and support is needed from Win95-CD, well CD is not necessary any more, because install path is now [C:\option] so files and support is easily collected from this install directory (option) instead of CD. 2. No problems when computer reboots and continue installation. Note: Regards eureka |
Success Installing Windows 95 OEM on the MS Virtual PC using the ”Windows 98 Custom, No Ramdrive” and changing the Autoexec to
| Code Sample |
| @echo off MSCDEX /D:BANANA /L:X PATH=a:\;a:\dos;x:\ c: mkdir option x: cd win95OEM xcopy *.* c:\option c: cd option setup.exe |
| Quote |
| You don’t need this arrangement in Win98 or WinMe, because these two systems create a folder named “option” inside Windows folder. |
I can only see the Options folder for the Windows Me OEM installation and not the Windows 98Se Retail.
| Quote |
| Quote: “Edited by deity on Nov. 21 2005,00:28”. He, he don’t you ever sleep? |
Yes! I sleep.
Only robots, dont sleep.
you know what are the minimum files required in the ezboot folder.
Thanks!
Posted by eureka on Nov. 22 2005,04:11
To deityGood news from you. Excellent!
Quote: “I can only see the Options folder for the Windows Me OEM installation and not the Windows 98Se Retail.” Well, how about apply same method on Win98 as for Win95?
Quote: “you know what are the minimum files required in the ezboot folder.”
You don’t need “old xxx.bmp” (not used any more) or not used xxx.bm1-files (with same name as not used xxx.bmp-files) and of course not used xxx.ezb-files. Delete Win98.ima (you use your own stuff).
Note: xxx.bm1 is created (or recreated) when you save (or resave) xxx.ezb-file. In fact, you can delete every xxx.bmp-file (but not xxx.bm1-file) when your project is finished (before you actually create the finished ISO). Because EasyBoot don’t need xxx.bmp background any more, but it still needs xxx.bm1-files.
Attention: you need to have xxx.bmp picture in ezboot to make it possible to rework xxx.ezb-file. Otherwise you receive a message typical; “No background…..”. Only use this option when you for sure have finished your project and finally create ISO!
To avoid having xxx.img, xxx.ima, xxx.bif in same folder as ezboot (it could some times get a little bit messy). Do as following:
Step 1. Create a subfolder in ezboot. Name it images. Like this: EasyBoot\disk1\ezboot\images.
Step 2. Move xxx.img, xxx.ima, xxx.bif files to folder images.
Step 3. You need to change “run-command” in EasyBoot to make it work. Typical case is: “run xxx.img”. If using a subfolder (named images), run command looks like this: “cd /;cd images;run xxx.img” (no quotes).
It’s been described bye Incroyable HULK in earlier topic (can’t find it now).
Regards eureka
Posted by deity on Nov. 22 2005,23:03
| Quote (Guest @ Nov. 22 2005,09:11) |
| To deity Good news from you. Excellent! Quote: “I can only see the Options folder for the Windows Me OEM installation and not the Windows 98Se Retail.” Well, how about apply same method on Win98 as for Win95? Quote: “you know what are the minimum files required in the ezboot folder.” You don’t need “old xxx.bmp” (not used any more) or not used xxx.bm1-files (with same name as not used xxx.bmp-files) and of course not used xxx.ezb-files. Delete Win98.ima (you use your own stuff). Note: xxx.bm1 is created (or recreated) when you save (or resave) xxx.ezb-file. In fact, you can delete every xxx.bmp-file (but not xxx.bm1-file) when your project is finished (before you actually create the finished ISO). Because EasyBoot don’t need xxx.bmp background any more, but it still needs xxx.bm1-files. Attention: you need to have xxx.bmp picture in ezboot to make it possible to rework xxx.ezb-file. Otherwise you receive a message typical; “No background…..”. Only use this option when you for sure have finished your project and finally create ISO! To avoid having xxx.img, xxx.ima, xxx.bif in same folder as ezboot (it could some times get a little bit messy). Do as following: Step 1. Create a subfolder in ezboot. Name it images. Like this: EasyBoot\disk1\ezboot\images. Step 2. Move xxx.img, xxx.ima, xxx.bif files to folder images. Step 3. You need to change “run-command” in EasyBoot to make it work. Typical case is: “run xxx.img”. If using a subfolder (named images), run command looks like this: “cd /;cd images;run xxx.img” (no quotes). It’s been described bye Incroyable HULK in earlier topic (can’t find it now). Regards eureka |
| Quote |
| Quote: “I can only see the Options folder for the Windows Me OEM installation and not the Windows 98Se Retail.” Well, how about apply same method on Win98 as for Win95? |
I dont need the options folder created for Win98 I was just saying it wasnt there.
| Quote |
| Attention: you need to have xxx.bmp picture in ezboot to make it possible to rework xxx.ezb-file. Otherwise you receive a message typical; “No background…..”. Only use this option when you for sure have finished your project and finally create ISO! |
| Quote |
| To avoid having xxx.img, xxx.ima, xxx.bif in same folder as ezboot (it could some times get a little bit messy). Do as following: Step 1. Create a subfolder in ezboot. Name it images. Like this: EasyBoot\disk1\ezboot\images. Step 2. Move xxx.img, xxx.ima, xxx.bif files to folder images. Step 3. You need to change “run-command” in EasyBoot to make it work. Typical case is: “run xxx.img”. If using a subfolder (named images), run command looks like this: “cd /;cd images;run xxx.img” (no quotes). |
I tried all the step mentioned.
I stoped at step 3. The command “cd /;cd images;run xxx.img” mentioned doesnt work.
I took of the cd/ and just left the
"cd images;run xxx.img" to each image and they run ok.
This is what files I have in the easyboot folder after deleting all the other files that where there. The images folder contains all the img, ima, or bif files that i had in the easyboot folder before.
| Code Sample |
| ebBACK.BM1 ebBACK.BMP ebLOGO.BM1 eblogo.bmp loader.bin standard.ctb images CDmenu.ezb |
Thanks for the help. I will try to polish it and then try it on a real PC hardrive. Hopefully i can find one that I can test it on.
I was trying to follow the following info on how to get Erd 2005 to run but he doesnt explain how to get erd to work with easyboot. I tried extracting the contents of the ISO created to erd_2005 in disk1 and then extracting the bif bootfile from my orgininal ERD iso and I put it in the images folder but easyboot will not boot it when I create an ISO with all my compilation. It complains about
| Code Sample |
CDBOOT: Couldnt find NTLDR Invalid system disk Replace the disk, and then press any key |
< http://forum.ezbsystems.net/cgi-bin/ikonboard.cgi?act=ST;f=1;t=301 >
Posted by eureka on Nov. 23 2005,09:54
To deityQuote: ”I took of the cd/ and just left the "cd images;run xxx.img" to each image and they run ok.”
Yes you have 100% right there. I copied the whole command from a different ISO (sometimes fingers on keyboard moves faster than brain does – at least in “my world”).
I’m imprested how clean you hold ezboot-folder (I don’t dare to show my own).
Quote: “I was trying to follow the following info on how to get Erd 2005 to run….”
Use my tutorial here:
1. Copy folder I386 from ERD-CD to EasyBoot\disk1
2. Rename I386 to “ERD5” (no quotes).
3. Copy ident files (WIN51 and WIN51IS) from root on ERD-CD to EasyBoot\disk1
4. Copy w2ksect.bin to ezboot-folder(w2ksect.bin comes with EasyBoot when you install and is placed in ezboot-
folder).
5. Rename w2ksect.bin to erd2005.bin
Now to hex edit:
Step 1. Start EasyBoot >> Tools >> Replace Text… >> Find file >> erd2005.bin in ezboot-folder
In “Text to find” you put in “I386” (no quotes) and in “Replace with” you put in “ERD5” (no quotes) push “Replace”. Only one text string should be replaced if you have done right!
Attention: use uppercase (CAPS). Like this ERD5 not erd5
Step 2. This is a little bit tricky.
Again use EasyBoot >> Tools >> Replace Text… >> Find file >> setupldr.bin in folder ERD5
In “Text to find” you put in “i386” (no quotes and note: i386 not I386) and in “Replace with” you put in “ERD5” (no quotes) push “Replace”. Three text strings should be replaced if you have done right!
Attention: use uppercase (CAPS). Like this ERD5 not erd5
Step 3. Again use EasyBoot >> Tools >> Replace Text… >> Find file >> setupldr.bin in folder ERD5
In “Text to find” you put in “I386” (no quotes and note this time you use: I386 not i386) and in “Replace with” you put in “ERD5” (no quotes) push “Replace”. One text string should be replaced if you have done right!
Attention: use uppercase (CAPS). Like this ERD5 not erd5
Use run command in EasyBoot as usual: run erd2005.bin (or different command if using separate image-folder)
Regards eureka
Posted by deity on Nov. 23 2005,22:07
| Quote |
| I’m imprested how clean you hold ezboot-folder (I don’t dare to show my own). |
Well it wasnt that clean the way I had it before. I had to go and delete all the backup BMP and PNGs I had in there. I had to delete other stuff that was in there. It helped that I could move the img and other files to their own folder.
| Quote |
| Use my tutorial here: 1. Copy folder I386 from ERD-CD to EasyBoot\disk1 2. Rename I386 to “ERD5” (no quotes). 3. Copy ident files (WIN51 and WIN51IS) from root on ERD-CD to EasyBoot\disk1 4. Copy w2ksect.bin to ezboot-folder(w2ksect.bin comes with EasyBoot when you install and is placed in ezboot- folder). 5. Rename w2ksect.bin to erd2005.bin Now to hex edit: Step 1. Start EasyBoot >> Tools >> Replace Text… >> Find file >> erd2005.bin in ezboot-folder In “Text to find” you put in “I386” (no quotes) and in “Replace with” you put in “ERD5” (no quotes) push “Replace”. Only one text string should be replaced if you have done right! Attention: use uppercase (CAPS). Like this ERD5 not erd5 |
I was successful in doing the steps above.
I got an error message on the 2nd step on the following step
| Quote |
| Step 2. This is a little bit tricky. Again use EasyBoot >> Tools >> Replace Text… >> Find file >> setupldr.bin in folder ERD5 In “Text to find” you put in “i386” (no quotes and note: i386 not I386) and in “Replace with” you put in “ERD5” (no quotes) push “Replace”. Three text strings should be replaced if you have done right! Attention: use uppercase (CAPS). Like this ERD5 not erd5 |
Do you have a "setupldr.bin" that I can use to replace the i386 string with the ERD5. I was so close to trying to run it.
So what happes to the left over folder and file
DOCUMENTS AND SETTINGS
BOOTSECT.BIN
LICENSE.TXT
WINBOM.INI
Does it matter if the files in the ERD5 folder are capitalized or can they remain with non caps.
Can I keep them like this
ERD5\
system32
WinSxS
biosinfo.inf
ntdetect.com
setupldr.bin
spcmdcon.sys
txtsetup.sif
winbom.ini
Fonts
help
inf
msagent
Never mind about the "bootsect.bin". I have mounted my ERD 2005 ISO with Daemon Tools and then went to the CD drive it mounted and just copied all the I386 contents from the CD to the disk1 folder and then I was able to use the replace tool successfuly with the last two steps. The above error I was getting when I had used Ultra ISO to open my ERD 2005 iso and then Drag and droped the I386 contents to the disk1 folder. Why would UltraISO mess it up. I tought that was its purpose to create and be able to extract files without corruption. Weird!
I tried booting it and it booted up fine. I could see the other attached drive and it seems to work ok!
Thanks for the help and Happy Thanksgiving Day to you and all those other people reading this thread!
Posted by deity on Nov. 24 2005,01:05
One other thing of note. Easyboot seems to capitalize all the contents of the new created ISO's it makes. So as stated by "Soma" at this thread < http://forum.ezbsystems.net/cgi-bin/ikonboard.cgi?act=ST;f=1;t=301 >You have to have "FireFox" and "FireFoxProfile" folder in lower case in the iso in order to be able to work online. Otherwise if it is capitalized you will not be able to browse.
So what I did was load my Erd 2005 ISO using Daemon Tools and then went to the Virtual CD that it loaded the image to and then I just copied the "FireFox" and "FireFoxProfile" folders from the CD to my desktop.
Then I did a bit of what he suggested in order to keep the "FireFox" and "FireFoxProfile" folders in lowercase.
What i did was create My Easyboot image with all my stuff capitalized. It forces everything into CAPS and we cant do anything about it at the moment. That blows. We should have more options. So, anyway. As I was saying. I then Opened the ISO image that Easyboot Created and then I just draged and droped the
"FireFox" and "FireFoxProfile" folder into my ERD5 folder under the SYSTEM32 Folder. Then I went to
File -> properties
The options I chose there per suggestion were:
tick the "allow lowercases"
tick the IS09660
tick the Max(221) caracters
tick the Omit ISO 9660 version number
Then I saved the new ISO and The Browsing works with Firefox on ERD 2005.
If you do any changes to your layout in easyboot and create a new ISO. You will have to redo the above steps in order for Firfox to work again in ERD 2005.
Posted by eureka on Nov. 24 2005,02:58
To deityWell-done deity!
Quote: “…..to extract files without corruption. Weird!”. Well, that’s life!
You didn’t need to do that “hex thing” with “erd2005.bin” in ERD5-folder (the same with “w2ksect.bin” in ezboot-folder). In fact, it’s possible to use original i386 (keep name) on folder and then use w2ksect.bin as it is, to start ERD2005.
What’s the point to hex edit files then, you may ask? Well, you now have room for original i386-folder holding WinXP or similar. No mismatch with folder i386 holding ERD2005 because it’s now renamed to ERD5!
About files:
DOCUMENTS AND SETTINGS
BOOTSECT.BIN
LICENSE.TXT
WINBOM.INI
These files are not necessary. I suppose you like to keep folders as clean as possible, so why put in stuff that you really don’t need?
Quote: “……capitalized or can they remain with non caps” Rule one: Don’t change anything that works!
About: "FireFox". Yes, you do need to rework this part to make "FireFox" run able.
Thanks giving to you………
Regards eureka
Posted by deity on Nov. 27 2005,21:30
I tought I was having success.Do you know of a way to add long File Support to my DOS Bootfiles. I was thinking if I add that support I can then have either Lowecase or uppercase letters. So that when I try to run the installer it will read it.
For example if I create an ISO with the WindowsME Upgrade, the Bootfile will run the autoexec file, but In DOS it is not able to read those folders. So when I go to the X: drive, I am unable to open the WinMeUPG folder.
So why is it that for example in My Original Windows ME Upgrade CD there is combination of Uppercase and lower case names and I have no problems running the Windows Me Upgrade Setup.exe files. But when I create and ISO like that I have problems opening the folder or files. I think that is why I could not open and edit the text strings before. mmm!
If I have my Wndows Me OEM version. Cant I use that to fresh install and do Upgrades. You think!
Thanks.
Posted by eureka on Nov. 28 2005,14:23
To deityQuote: If I have my Wndows Me OEM version. Cant I use that to fresh install and do Upgrades. You think!
Good thinking… I use WinMe –OEM this way (“clean install” and also to upgrade Win9x).
You don’t need WinMe-upgrade. In this way you avoid every problem you have mentioned, witch seems to be a “golden way” out of your problems with truncated files and that stuff…
I still haven’t figured out why you getting truncated names (and only when installing WinMe-upgrade). That’s what I call weird! Anyway, you are on the right track using WinMe-OEM to both “clean install” as to upgrade from Win9x. And as bonus, you create more space to something else!
I don’t think lfndos is to any help in this case.
Regards eureka
Posted by deity on Nov. 30 2005,00:00
I had to optimize the files in order to fit a 80min CD. Original File size was 1Gig plus. When I optimized it. It came down to 709MB. But It might be the problem. So im trying to trim it down to use the DOS programs I have and Win95, WinSe, and WinME, and ERD 2005. I dont want to use Optimized. I have a question reguarding DOS. Hope you know how to do what im hoping can be done. I tried going to the pages you mentioned before on dos commands but I cannot find an example to do what i need.
I want to copy files from the D drive to the c: drive subdirectory
Most of it works. I think im having problems at the end
where I need to copy the files from the DeskProp Folder from the CD rom to the c:win98\DeskProp
I cant figure out how to do it. Here is my attempt.
| Code Sample |
| @echo off MSCDEX /D:BANANA /L:X PATH=a:\;a:\dos;x:\ c: mkdir Min98 cd Min98 mkdir DeskProp x: cd Win98SE xcopy *.* c:\Min98 x: cd Mindows xcopy *.* c:\Min98 x: cd Mindows cd DeskProp xcopy *.* c:\Win98\DeskProp <--- I tried this one and it didnt work. or xcopy *.* path=c:\Min98\DeskProp <--- I tried this one and it didnt work either. c: cd Min98 Install.bat |
Posted by eureka on Nov. 30 2005,08:50
To deity Quote from your autoexec.bat-file:
@echo off
MSCDEX /D:MSCD001 /L:X
PATH=a:\;a:\dos;x:\
c:
mkdir Min98 < This is correct (creating folder Min98 on [C:])
cd Min98
mkdir DeskProp < This is correct (creating subfolder DeskProp in Min98)
a:
(copy command of some kind. Examples down here)
(your final command “install.bat” when all copy commands been executed as wanted)
--------------
I give you some examples. I use “ezboot” folder with subfolder “image”.
Attention: I didn’t manage to get switch [/H] (hided files and folders) to work with xcopy. I assume that xcopy cannot copy hided files and folders (at least not with that version I tested). Files and folders must be visible! So I didn’t set option: “Hide boot folder” or “Hide all files in bootfolder” when creating ISO in EasyBoot!!!
Note: DOS doesn’t care about uppercase (CAPS) or not!
--------------
Example 1.
a:\xcopy x:\ezboot\image\*.* c:\min98\deskprop\ /E < This copy every file (and subfolder) from folder “image” to folder deskprop on [C:].
Note: It doesn’t copy anything from folder “ezboot”.
Attention to switch [/E]
Result is this: c:\min98\deskprop\*.* (files and subfolders copied)
Example 2.
a:\xcopy x:\ezboot\image c:\min98\deskprop <This only copies files from folder “image” to c:\min98\deskprop
Result is this: c:\min98\deskprop\*.* (only files no subfolders copied)
Example 3.
a:\xcopy x:\ezboot\image c:\min98 <This copy files from folder “image” to C:\min98
Result is this: c:\min98\*.* (only files and no subfolder copied)
Example 4.
a:\xcopy x:\ezboot c:\min98 <This copy files from folder “ezboot” to c:\min98 (no subfolders copied).Result is this: C:\min98\*.* (only files and no subfolders copied).
Example 5.
a:\xcopy x:\ezboot\*.* c:\min98 /E <This copy files and subfolders from “ezboot” to c:\min98 Note: switch [/E]
Result is this: c:\min98\*.* (files and subfolders copied).
----------------------------------------------------------------------
Read here: < http://www.computerhope.com/xcopyhlp.htm#03 >
< http://www.microsoft.com/resourc....py.mspx >
< http://www.ss64.com/nt/xcopy.html >
Regards eureka
Posted by deity on Dec. 01 2005,00:17
Thanks! I will try out some of your examples. I had gone to that site you mention but their not good at showing good examples. They are lacking in that. They describe things ok. But sometimes its confusing.
Your examples clear things out. I have a better understanding.
Posted by deity on Dec. 03 2005,12:55
This seems to work.| Quote |
| @echo on MSCDEX /D:BANANA /L:X PATH=a:\;a:\dos;x:\ Echo now changing to C drive c: Echo < creating folder Min98 on [C:] mkdir Min98 Echo Changing to Min98 Directory contents cd Min98 Echo < creating subfolder DeskProp in Min98 mkdir DeskProp Echo Now Copying all files and folders from the CD's Win98SE Directory to the c:\Min98 directory a:\xcopy x:\Win98SE\*.* c:\Min98\ /E Echo <This only copies files from the CD's Mindows\DeskProp folder to c:\min98\deskprop a:\xcopy x:\Min98\DeskProp c:\min98\DeskProp Echo now changing to C drive c: Echo Changing to Min98 Directory contents cd Min98 Echo Now running the Install.bat file to install Windows 98 Install.bat |
This line you mentioned did not work
| Code Sample |
| MSCDEX /D:MSCD001 /L:X |
Still have to test some more.
Posted by deity on Dec. 05 2005,18:36
Update: I created the ISO. It came out to be around 675 MB.
I had to use Easy boot to create the Small ISO with the Easyboot Folder and the DOS Images.
I had to use Magic ISO to drag the contents of the ERD Commander 2005, Win95 - 98Se - ME.
Otherwise, If I used Ultra ISO, Whenever I ran the ERD 2005 It would give me an error when looking for the Network stuff. Plus Magic ISO explains what options should be selected when Creating an ISO to be used in DOS, Win, and others.
I just got a laptop that I could test the installations on. An old one. But just right for the testing.
I was successful in installing Windows 95.
Then I tried Installing Windows 98Se.
I just need to test installing Windows ME.
Something is wrong with my VMware virtual machine.
It seemed to work Well in MS Virtual PC.