MobileOS
#101
Posted 16 May 2007 - 01:48 AM
I d/l WB 071b. I d/l all Recommended. Now, how do I form project? I see MobileOS under Downloads but not on Scripts.
So how do I make a MobileOS project? I see how to Create a script in Tools and I then overwrote that with the script you provided. But how do I RUN the script? Do I need to create a PROJECT? How do you create a new project. I could not find anywhere how to do this?
Gerry
#103
Posted 16 May 2007 - 12:51 PM
you should be re-selecting http://mobileos.boot-land.net
Ok, did that. Now I try to run project MobileOS after setting Paths. It keeps saying error, CD is bad! It's not bad, I have used it many times. It is DELL WinXP CD. It has all files. I have separate download for SP2 EXE and for Win2003 Server Enterprise CD.
How can I get past this error?
#104
Posted 16 May 2007 - 11:49 PM
fix "Rpc server"
fix "redirector"
some small tweaks
#105
Posted 17 May 2007 - 12:10 AM
save log.html , 7ziping him and give me
#107
Posted 17 May 2007 - 12:59 AM
use real CD
Do not use long path and blanks
#108
Posted 17 May 2007 - 01:12 AM
And these files really exist?
use real CD
Do not use long path and blanks
Result:
Error source CD "D:", this CD is bad!
log_REALCD.html 64.87K
126 downloads
#109
Posted 17 May 2007 - 01:22 AM
#110
Posted 17 May 2007 - 01:30 AM
use v006
How do I select V006? I redownloaded MobileOS. Shouldn't that bring down V006?
#111
Posted 17 May 2007 - 01:34 AM
#112
Posted 17 May 2007 - 01:38 AM
I redownloaded it again and this time it brought down V006. So I will try this.
Errors:
Target directory (Bin.img ) not exist.
Target directory (ram.img ) not exist.
Source disk not exist.
log_V006_1.html 9.68K
131 downloads
#113
Posted 17 May 2007 - 01:49 AM
Files which at you are not present - this critical files
Your CD really spoiled
attempt other CD/DVD
#114
Posted 17 May 2007 - 02:08 AM
go to "proect"
Files which at you are not present - this critical files
Your CD really spoiled
attempt other CD/DVD
Do not agree.
My "Projects" tree looks like:
├───v005 │ ├───BinImg │ ├───RamImg │ └───Tools └───v006 ├───BinImg ├───RamImg └───Tools
So BinImg and RamImg directories are there. They are not named Bin.img and ram.img.
The script is looking for the wrong names.
BinImg <> Bin.img RamImg <> ram.imgAnd again in script it is looking for X: rather than D: so it thinks that the Source disk is missing.
X: <> D:
#115
Posted 17 May 2007 - 02:31 AM
├───Project (script not folder) !!!
├───BinImg
├───RamImg
└───Tools
#116
Posted 17 May 2007 - 02:40 AM
projectgo to "proect"
#117
Posted 17 May 2007 - 02:40 AM
└───v006
├───Project (script not folder) !!!
├───BinImg
├───RamImg
└───Tools
This is from DOS tree command. Here is the expanded listing:
└───v006 │ Project.script │ ├───BinImg │ 1_Preparation.script │ 3_Copy_and_Expand.script │ 5_XP_Setup.script │ 7_Applying_settings.script │ 9_Finish.script │ key.script │ ├───RamImg │ 1_Preparation.script │ 2_Copy_and_Expand.script │ 3_Fixreg.script │ 9_Finish.script │ └───Tools Cleaning_project.script IMG_and_ISO.script Quick_test.script
#118
Posted 17 May 2007 - 08:34 AM
In Project.script (title Project) you choose "Source Disk" , "Target directory " and "Target directory for Ram.img"
#119
Posted 17 May 2007 - 10:02 AM
MobileOS(http://mobileos.boot-land.net/) | .-. |+|-v006 `-' | ├--- Project (choice of Paths) .-. |+|-- BinImg `-' | | ├-- Preparation | | | ├-- Copy and Expand | | | ├-- XP Setup | | | ├-- Applying settings | | | ├-- Finish | | | └-- __key .-. |+|-- RamImg `-' | | ├-- Preparation | | | ├-- Copy and Expand | | | ├-- Fixreg | | | └-- Finish .-. |+|-- Tools `-' | ├-- Cleaning project | ├-- IMG and ISO | └-- Quick test
#120
Posted 17 May 2007 - 01:25 PM
I am sorry to tell you this but I am still seeing nearly the exact same errors:
Target directory (Bin.img ) not exist. Target directory for ram.img not exist. Source disk not exist.
log_V006_2.html 9.66K
119 downloadsAnd once we are beyond these errors, if you are expecting a user to make a choice of some type then there must either be an input box to fill-in like those on the Paths tab, or radio buttons, or you must popup a selection window for the user.
I see no "Target directory for ram.img" input box anywhere.
How I am testing:
Run WinBuilder GUI
Select Download Tab
Check mobileos.boot-land.net checkbox
Click Download button
Wait for any download
Select Paths Tab
Select Work directories Tab
Select MobileOS (euhenio)
Fill-in Source dir: D:
Fill-in Target dir: C:\Documents and Settings\greno\Builds\MobileOS\Target
Fill-in ISO file: C:\Documents and Settings\greno\Builds\MobileOS\ISO\Boot.iso
Select Scripts Tab
Check MobileOS (euhenio) checkbox
Check V006 checkbox
Press Play icon
Ok, I found the obscure input boxes by click on MobileOS | V006 | Projects.
And how do these choices relate to those on the Paths Tab? Looks like duplication.
This is not intuitive at all!
The user should either have just one place to enter these choices on one of the main tabs or be prompted for the choices as the script runs.
So I clicked the "Check project and set new paths now" button and I get this error again:
Error Source CD "D:", this CD is bad!
Arrrrrg. It's not bad I just checked the log and the very first file that it is failing on is right there on the CD!
>dir d:\win*
Volume in drive D is XP2_PRO_ENG
Volume Serial Number is 0E2F-A37E
Directory of d:\
08/18/2001 08:00 AM 10 WIN51
08/18/2001 08:00 AM 10 WIN51IP
2 File(s) 20 bytes
0 Dir(s) 0 bytes free
log_V006_3.html 65.59K
144 downloads
#121
Posted 17 May 2007 - 05:26 PM
dir d:\i386
#122
Posted 17 May 2007 - 05:32 PM
Ok , send me
dir d:\i386
cdi386.txt 66.95K
1108 downloads
cdi386_full.txt 273.5K
261 downloadseuthenio,
Could there be a problem about language or character encoding that is causing the script to think that the CD is bad? I ask this because I have seen a couple times Error box about "Other language".
#123
Posted 17 May 2007 - 06:55 PM
integrate Service Pack 2 and try again
#124
Posted 17 May 2007 - 07:00 PM
Anyway around this? This is going to be the case for about 99.9% of everyone out there.
Why does MobileOS even care about the Service Pack level? Just build the RAM image from whatever the user provides. If they want higher level then let them load image into VM and apply newer Service Pack and shutdown.
#125
Posted 17 May 2007 - 11:51 PM
D:\WIN51IP.SP2
D:\I386\NTOSKRNL.EX_
D:\I386\SCHEDSVC.DL_
D:\I386\SHELL32.DL_
D:\I386\SYSSETUP.DL_
D:\I386\USBEHCI.SY_
D:\I386\WIN32K.SY_
D:\I386\fltmgr.sy_
D:\I386\http.sy_
D:\I386\sp2.cab
D:\I386\xpsp2res.dl_
and other sp2-files
I never made it, therefore I can not help
This option is present in nLite , maybe it will help you
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users






