| Topic: Win95 OEM , Win98SE Retail , Win ME OEM AIO CD, How can you create an ALL in ONE CD | < Next Oldest | Next Newest > |
|
| Post Number: 31
|
eureka
Unregistered
|
 |
Posted on: Nov. 20 2005,16:35 |
|
   |
To deity
Quote: ”Ill have to find My Virtual PC CD and install it to run this test”.
Please do so and feedback result.
Regards eureka
|
|
|
|
| Post Number: 32
|
deity 
Group: Members
Posts: 58
Joined: Nov. 2005
|
|
Posted 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
|
Edited by deity on Nov. 20 2005,19:28
|
 |
|
|
| Post Number: 33
|
eureka
Unregistered
|
 |
Posted on: Nov. 21 2005,02: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: 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
|
|
|
|
| Post Number: 34
|
deity
Group: Members
Posts: 58
Joined: Nov. 2005
|
|
Posted 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!
Edited by deity on Nov. 21 2005,23:57
|
|
|
|
| Post Number: 35
|
eureka
Unregistered
|
 |
Posted on: Nov. 22 2005,04: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
|
|
|
|
| Post Number: 36
|
deity
Group: Members
Posts: 58
Joined: Nov. 2005
|
|
Posted 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! |
Ok! i will leave it in there untill I finish. Then I will delete all BMP files.
| 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
Edited by deity on Nov. 22 2005,23:50
|
|
|
|
| Post Number: 37
|
eureka
Unregistered
|
|
Posted on: Nov. 23 2005,09:54 |
|
|
To deity
Quote: ”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
|
|
|
|
| Post Number: 38
|
deity
Group: Members
Posts: 58
Joined: Nov. 2005
|
|
Posted 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
|
I did find the setupldr.bin in folder ERD5. I tried to do the find “i386” and replce with ERD5. But I get this error!
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!
Edited by deity on Nov. 23 2005,22:44
|
|
|
|
| Post Number: 39
|
deity
Group: Members
Posts: 58
Joined: Nov. 2005
|
|
Posted 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.
Edited by deity on Nov. 24 2005,01:34
|
|
|
|
| Post Number: 40
|
eureka
Unregistered
|
|
Posted on: Nov. 24 2005,02:58 |
|
|
To deity
Well-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
|
|
|
|
|
|
|
© 2002-2024 EZB Systems, Inc.
|
|
|
