Printable Version of Topic

Click here to view this topic in its original format

Boot Land _ Projects _ MobileOS

Posted by: euhenio Feb 13 2007, 01:29 PM

Based on WinXP SP2 (EN - recommended)


QEMU on Windows Version 0.9.0 Fabrice Bellard http://www.h7.dion.ne.jp/~qemu-win/
Section "Accelerators"
- qemu.exe
- fmod.dll
- SDL.dll
- qemu-img.exe
- bios.bin
- vgabios.bin
7-Zip © Igor Pavlov http://www.7-zip.org
- 7zG.exe
- 7z.dll
dd for windows John Newbigin http://www.chrysocome.net/dd
- dd.exe

- mkisofs.exe?
- cfadisk.sys http://www.911cd.net/forums//index.php?showtopic=14292
- RegDACL.exe http://www.heysoft.de/Frames/f_sw_rt_en.htm
- flashnul.exe http://shounen.ru/soft/flashnul/
- http://ovh.dl.sourceforge.net/sourceforge/ultradefrag/ultradefrag-1.2.1.bin.i386.exe http://ultradefrag.sourceforge.net
- http://www.ltr-data.se/files/imdiskinst.exe

WinBuilder 072

Antivirus, explorer(user) etc. should not interfere in work virtual machine (Qemu)

Web server - http://mobileos.boot-land.net

--------------------------------------------------------------------------------------





Hi all
Somebody already tasted this OS?
http://www.911cd.net/forums//index.php?showtopic=19056
http://euhenio.mam.by/ (Russian)

Scripts which are at this forum almost approach MobileOS
I think, that it can replace Preinstallation Environment.

Posted by: Nuno Brito Feb 20 2007, 11:40 PM

It would be an excellent replacement if the whole method could be automated, otherwise people will still be afraid to try it out by themselves..

I'll try it next weekend, looks really good! thumbsup.gif

Posted by: euhenio Feb 22 2007, 12:43 AM

Yes, people really are afraid to try it.
I am confident, that i will manage to create sometime automated method based by scripts Winbuilder. I hope for reciprocal efforts

Posted by: Nuno Brito Feb 22 2007, 12:01 PM

Since you're using nlite, have you already tried the method used by microwinx?

http://microwinx.com/

They create a XP based build (not PE) also sized around 50Mb, it's not using explorer shell or anything else added, but the result is very similar to our liveXP project and it will surely be easier to tweak with all the experience gathered from PE environments.

Don't be afraid to place any doubts you have regarding the script syntax or anything else in wich you need help - This is a really promissing project.. smile.gif

Posted by: euhenio Feb 27 2007, 01:00 PM

Whether you plan to support ms-inf format.
In projects a plenty of the information (in registry) included in installation CD contains.
Maybe to an release version 1.0 it will be possible .


Posted by: Nuno Brito Feb 27 2007, 01:44 PM

It's good hearing news about a version 1.0 - I haven't had the time I hoped to get for testing mobileOS but will do it as soon as possible.

Do you need support for reading INF file from MS format?

Never thought about it, but I can give it a try - but it will take a while since I already have a few other code sections needed to be recoded and modified. Then I'll definitively help you better on this task! smile.gif

Posted by: euhenio Feb 28 2007, 12:37 AM

Nuno Brito

QUOTE
Do you need support for reading INF file from MS format?

Of course.
Windows XP registry contains ~10Mb keys which basically are read from inf files.
Bart has directed us not at that way.


Posted by: Nuno Brito Feb 28 2007, 10:07 AM

Wouldn't it be simpler to load the XP hive from the running project onto the local registry and then modify the paths on the INF files to match the loaded hive?

This way it would be 100% ms compatible since we'd be using their INF engine - I would surely take a lot of time to get a good working result and this way seems faster to test this theory on real builds.

smile.gif

Posted by: euhenio Feb 28 2007, 11:08 PM

QUOTE
Wouldn't it be simpler to load the XP hive from the running project onto the local registry and then modify the paths on the INF files to match the loaded hive?

For the beginning it most suitable variant.

Posted by: euhenio Mar 9 2007, 12:33 AM

see first post

Posted by: thunn Mar 9 2007, 03:27 AM

Thanks for project script! Looks very interesting.
This is something I've been playing with for two years...
Regular XP as a runtime image!
Do you have it EWF enabled yet?
smile.gif
I'll be curious to see your project continue. wink.gif

Both PE and regular Windows developers have reduced their platforms to 15MB each, they're very similar.

Posted by: Nuno Brito Mar 9 2007, 11:04 AM

Thanks for this release!

One thing: why is nlite required to slim the source?

We can copy only the needed files and remove unneeded entries from txtsetup.sif ourselves with wb, and the installation process can be simulated with qemu - I can help you with this process if you need.

Imagine it this way: We create the modded windows source as an ISO and proceed to use it as boot image on qemu - it's possible to generate an answer file that will provide all needed steps in an unatended fashion install on the emulated disk.

The serial number needed to install windows *must* be provided by the user itself - this can either be added from a script box inserted into the unnatended answer file, or user will input when windows is installing.

After the installation is complete, the registry patch is added and files.7z is created fresh - at this point I'm not sure on the best approach to copy files.7z from the guest OS - perhaps using network support, but on systems with firewall activated or even vista would make it hard to work as expected. Can't we use the disk image itself as source and mount it on our host OS since we can always create a fresh image disk on each build? This would also make it easier to manipulate files.

In either case, a small app - (using autoIt for example) can do these tasks unnatended, and order the system to shutdown, wich will cause qemu to close itself and allow the script processing to continue.

A message box asks the user if the created image is working correctly and proceed with the rest of build process.

End result is a completely unnatended XP hardware independent OS done with efficiency... thumbup.gif

In my opinion, this would be a mobile solution I would use all day long... punk.gif


Posted by: thunn Mar 9 2007, 12:06 PM

You bring up some good points...why nlite? Good question to which there are many answers but you may be right. Is the XP Setup process so difficult to reproduce? I think we already know it's more flexible than we're led to believe. I'm thoroughly familiar will all pre-Vista UA practices and find all of this sparking some ideas. I have pre-scripted installs and a good bit of undocumented information on winnt.sif, but I don't even think you need all that, just a simple answer file combined with Nuno's detailed knowledge of the NT OS core should suffice. Just to make it interesting, you could use something like Longhorn 4047? smile.gif

Posted by: euhenio Mar 12 2007, 12:21 AM

thuun
I not use Longhorn.
Nuno Brito
Thank you for idea. Еventually we find way to simplify this process .

However if will appear the script , simplifying making MobileOS I will glad .

Posted by: thunn Mar 12 2007, 02:44 AM

I was only joking.
I've been looking at how the registry must be modified so that we can make a hdd install straight from the source cd. DigitalProductIDs must be added and other things too, but it's very possible.
Obviously we can benifit from Nuhi's knowledge by studying a small nlited XP. I want to do something similar to what euhenio is doing using nlited xp but using just the source cd. The end result to be a generic hardware vhd image you could restore to bare metal or boot into RAM from cd/dvd/hdd.
Communication may by a little tricky but I 'd like to help with this project if I can. smile.gif

Posted by: Oleg_II Mar 12 2007, 03:41 AM

Needed files for the system can be taken directly from source CD - make one small and stable build with nLite and you'll know the files and their locations in the build. It's no problem at all (I have this about 300MB with working printing, scanning, duil-up adsl and WiFi and think it could be reduced some more, most of my programs work and it's about 200MB on compressed NTFS image).

I found that for universal system some files should be extracted from DRIVER.CAB and placed in system32 and system32\drivers folders - it is possible to find out which files from WinBuilder stable build.
Some SATA/RAID drivers can be added to MobileOS for this purpose too.

Some pre-made regestry tweaks like USB support can be added for universal system too.


The only problem is in creating working Registry. The only way I see is to take regestry files from user's working system and edit them in WinBuilder - delete and add some keys with pre-made scripts.
Where to take these scripts? Compare full installation XP regestry with nLited or xplited regestry (maybe with both) and finding which keys should be added and which deleted to achive the goal.

nLited system seems to be smaller. xplited system seems to be more stable. IMHO.
Some regestry settings maybe taken from BartPE hives aslo.

If generic Regestry creating is possible any programs and language support can be added by a user through regular scripts during building.


NIKZZZZ from Ru-Board created new utility for saving image of running in RAM system. That could be very usefull because as we know any changes in MobileOS can't be saved after reboot. And this can be usefull for capturing the system itself (I have not tested it yet).


PS Just thought of it: maybe some functions in XP can be replaced by free alternatives like native netwoking replaced with PENetwork GUI? That way some more files and regestry settings can be deleted.

Posted by: thunn Mar 12 2007, 06:44 AM

Oleg_II,
There's a guy, Bold Fortune, he made batch files which reduce an installed XP system, however, I'm leaning toward a nlite based project because of the small size that users have achived. I've been running nlite throughout the day to work out a few bugs and make sure the new version is working ok. Actually, I've reverted to v1.2.1 which has produced a stable build I'm running on a VM now. Taget size is about 135MB for the setup i386 with most fuctions still in tact, any smaller and the loss of funtionality is too great. When done, hopefully tomarrow, I'll start building my list to generate scripts.
Thanks for reporting your success!
Wouldn't it be nice to run the image out of RAM if you want to? wink.gif
The end project might use a DOS based install, or even a mini Linux, to load OR restore the XPSP2 system image made from the install CD.

Posted by: Oleg_II Mar 12 2007, 06:54 AM

You can try my LASTSESSON.INI (nLite v1.3) and take out Chinese Simplified and Russian languages support. For now I only have one very serious bug - I can't run some MSI installers in the system confused1.gif Everything else seems to be functioning well. New source is less then 120MB (without languages it will be about 100MB).

If you need CHM files openning I can give you work around (works fine) or you can use a free program xCHM (works fine with English).

I open video files with Mplayer that doesn't need video playback support (self containing).

DirectX with sound support, printing, scanning, new devices drivers installation and, all kind of internet connections - all works fine.
No IE, OE, Task scheduler, MS Help (CHM files can be opened fine though with a small addition wink.gif


PS No need for install at all - when you prepare the build just place it on virtual drive created with BootSDI.script wink.gif I don't even think we should concentrate on installing - it's just for achiving the fewest files set for working system with the most functionality. When using WB we only need extact and place into Target sub-folders needed files from the source CD and find out how to create the Regestry in WB.

I run this image right now and writing this from RAM what.gif

PPS And I forgot to mention that you can delete a lot of files from installed system too: .LOG, .TMP, .PNF, .EVT, .OLD, etc. - it was about 10MB in my system! Some fonts should be revised if they are really used wink.gif After extracting some files from DRIVER.CAB and SP2.CAB they also can be deleted. No need for DLL Cache. And so on.

 Last_Session.zip ( 6.22k ) : 29
 

Posted by: thunn Mar 12 2007, 07:39 AM

That's right, no install, just restore or load!
I already know where to export most all of the DigitalProductIDs, WPA, WGA.. (etc.) entries from in the registry.
It will be easy for me to start building a script and concentrate on the registry patching once the nlite build is imaged and ready for building lists. thx!

---
...and now I'm posting from the nlited system that just finished installing, It's about 20-30MB. bigger than yours, but still very fast even in a VM!
No IE front end, but the engine was left so I'm using explorer to surf the net before going to sleep. smile.gif I'll try your presets tomarrow.

here I am wink.gif..


 PrintFolders.7z ( 34.81k ) : 26
 

Posted by: Oleg_II Mar 12 2007, 08:13 AM

More 30MB - it's a half of WinBuilder stable build with network support and some appz! wink.gif

I think that this also will be difficult - some people needs IE, some want to have Task scheduller, some will need OOB or even Old CDPlayer...

Would it be better not to stick with ALL functionality but with some features that are difficult to reproduce in PE systems like WiFi with security, printing and scanning? Most of other features including HTML rendering can be added with regular scripts during the build.

Posted by: jaclaz Mar 12 2007, 08:56 AM

Thunn, Oleg, have a look at this post here:
http://www.boot-land.net/forums/I-found-a-GOLD-mine-t1697.html

The "universal" ATA and SVGA by "alter" could be useful to reduce size while making it "portable".

jaclaz

Posted by: Oleg_II Mar 12 2007, 09:04 AM

Yep, it's Russian isn't it? wink.gif Yurkesha from Ru-Board thinks that it's good but it only supports SATA. And if you need RAID you should add some drivers too (they are often the same for SATA and RAID).

Interesting and promissing but not right now cheers.gif

Posted by: jaclaz Mar 12 2007, 12:20 PM

Well, NO, it supports MOST IDE/ATA/ATAPI devices and a few SATA:
http://alter.org.ua/en/soft/win/uni_ata/
hence the name of "universal"

Same applies for the VGA/SVGA:
http://www.navozhdeniye.narod.ru/vbemp.htm
http://www.geocities.com/bearwindows/vbemp.htm

jaclaz

Posted by: Oleg_II Mar 12 2007, 12:41 PM

Yurkesha made the script for universal VGA/SVGA and posted it on 911cd.net wink.gif
It works for most drivers and I think it can be usefull in MobileOS project.

The WB plugin for this is very easy - just copy two files and extract one from the source CD. I'm attaching mine and if somebody wants he/she may adjust it for better look and functionality wink.gif

As for universal mass storage driver... I'm not an IT specialist, I'm just transfering Yurkesha's opinion about it cheers.gif

 vga.zip ( 22.24k ) : 30
 

Posted by: thunn Mar 12 2007, 03:36 PM

Oleg_II,
Later today I will. reproduce your build...100MB. is a good target size!!! thumbsup.gif

We'll obviously need to load generic drivers for most hardware, jaclaz is excellent to have around isn't he? thanks for the info!!

Posted by: psc Mar 12 2007, 03:47 PM

QUOTE(Oleg_II @ Mar 12 2007, 01:41 PM) *
Yurkesha made the script for universal VGA/SVGA and posted it on 911cd.net wink.gif
It works for most drivers and I think it can be usefull in MobileOS project.

The WB plugin for this is very easy - just copy two files and extract one from the source CD. I'm attaching mine and if somebody wants he/she may adjust it for better look and functionality wink.gif

As for universal mass storage driver... I'm not an IT specialist, I'm just transfering Yurkesha's opinion about it cheers.gif

Including your script into (running) nativeEx_barebone project:

Under VirtualBox ISO starts well, but the CD with burned ISO fails with a 'setupdd.sys issue'.
Microsoft knowledge base tells something about hardware issue, starting from RAM module (I did not change) to a new unknown piece of HW (I did not change). So I suspect the new driver misunderstands something or something is missing.

My HW is onChip intel 82845GL

Peter

Posted by: Oleg_II Mar 12 2007, 06:04 PM

psc
Interesting... It works fine here on a couple of notebooks with Intel 82852/82855 GM/GME and Via integrated video cards. And your error seems to have relation not with video confused1.gif

Anyway it's a beta version driver. It was reported working with some video adapters but some Intel card was advised to be commented in INF file according to Ru-Board information.

Just checked it (you may look at the screen shots http://forum.ru-board.com/topic.cgi?forum=62&topic=8981&start=608&limit=1&m=1#1. For i845 it's recomended to comment this line:

QUOTE
%AnaPa.DeviceDesc0% (VBEMP VIDEO DRIVER FOR PCI\VEN_8086&DEV_2562) = Vbemp, PCI\VEN_8086&DEV_2562
and maybe to comment all devices with PCI\VEN_8086 - they are supported by native XP driver.
And GeForce 6100 is probably should be commented too (you need to find out vendor ID and comment the line with it)...
Information from Yurkesha (just reading his postings).

Posted by: euhenio Mar 13 2007, 06:33 PM

Hi All
MobileOS does not know restrictions!

My MobileOS is arranged so:
RAM.IMG - kernel, 64 Mb, mounted as X:
BIN.IMG - other system files , mounted as Y:
PROG.IMG - my programs, mounted as W:

She can be loaded on compi with 128Mb RAM (required pagefile.sys)

I already use such monsters, as Promt Expert and Kaspersky Internet Security 6.0 (full version) .

Farewell HDD-OS, time MobileOS has come .

Posted by: thunn Mar 27 2007, 11:36 AM

Yes it has! And flash prices are dropping fast!!
In less than 10 years flash will be cheaper per MB than metal platter hdds.

Posted by: MedEvil Mar 27 2007, 02:10 PM

I will start getting inpressed when flash memory can take as many write cycles as a hdd.
Until then, it's nothing more than any RW-Disk. thumbdown.gif

Posted by: Nuno Brito Mar 27 2007, 03:27 PM

The mobileOS proposed by euhenio runs straight from RAM, so the overall write cycle of the pendisk is very limited - no more would it stress the hardware like copying a gigabyte worth of mp3's .. wink.gif

Seems a handy OS to carry around, to wich adding programs isn't a pain as we see on PE environments, I should really try it when I get some extra time.

smile.gif

Posted by: thunn Mar 27 2007, 10:47 PM

Testing now.
A question for euhenio
,
You have used Programs instead of "Program Files" in the reg patch. It's not for PE., Any reason?
I'll have to look closer!
I'm adding additional 7-Zip entries for associations, so, no problem.
wink.gif
I install 2 programs:
Firefox and 7-Zip

My nlite presets are 110 MB, seems to work ok, very fast.
I'll post presets/adds later, as a thought,
you should provide last session presets with the script.project,
Perhaps some other methods to reduce XP can be tested also.

Posted by: thunn Mar 28 2007, 12:28 AM

Wow..OK now I understand.

You're only using some files from the nlite build!
Most of them come from the source disk!!

This is so f------g cool and exactly what I had in mind. I should have looked at this before. I hope it works, it certainly makes perfect sense that it does from what I see in the provided scripts. 'Her' time has come, I love it.
Great job!! :twothumbsup:

forget the question.

I'll post some test results shortly.

Posted by: euhenio Mar 28 2007, 01:41 AM

Old last session I have lost.

However now I work about new script for similar last session. The size ~ 400Mb.
Ram.img (~55Mb) completed - complete script .

Probably my scripts work without nLite.

Requirements are similar:

Program Files> Programs
Documents and Settings> Settings
WINDOWS> WINNT

To install it is necessary on disk Y:

Last Session.ini I can give tomorrow.

Now I use XPSP2 English version.


Posted by: thunn Mar 28 2007, 03:48 AM

Well, I guess I need more details smile.gif

My nlited XPSP2 is 105MB.
I do not need last session. No.

Please, more on what files go where, and when.

If you have posted more details in English please point me to it.. I need to know about how to use minlogon, fbwf, and vdk with your project. Minlogon and FBWF require registry changes.
I have the files, but most users do not, please keep that in mind.

Finally, what is done with the finished folder?

QUOTE
My MobileOS is arranged so:
RAM.IMG - kernel, 64 Mb, mounted as X:
BIN.IMG - other system files , mounted as Y:
PROG.IMG - my programs, mounted as W:


I can imagine, but i have to ask..
How are the individual images for Kernal, Extras, and Programs, made and used?
Once 'MobileOS' is working here, I'd be happy to assist with making the script(s) user friendly. My command of English is not so bad. wink.gif

If you lokk at the picture below,
What I missed is where you told us to add these files to the nlite build,
FBWF and minlogon I understand.
I need information on the use of VDK with regard to..
How do we make the finished image and mount it at boot?
thank you![attachment=1701:mosquest.png]

 

Posted by: euhenio Mar 29 2007, 12:53 AM

thuun

FBWF is optional.
I use minlogon always and he is extremely desirable.
My script make contents Ram.img.
Bin.img contains the installed system and other programs - he gathers manually.
Prog.img It is possible to unite with Ram.img.

Use VDK is in detail described jaclaz http://www.911cd.net/forums//index.php?showtopic=19056&st=40#

Re-read the connected topics.

QUOTE
I'd be happy to assist with making the script (s) user friendly


Thanks! It will be simply magnificent!



Posted by: thunn Mar 29 2007, 03:34 AM

euhenio,
I'll do my best to put the pieces together.
Once I understand exactly what you want to do, I can help automated the rest so nothing must be done manually.
I am also working on other work/projects so hopefully tomarrow I can study your mobileos model more. I can't wait until it's all scripted so more people here can try it!
Currently running my full SDI PE in RAM.. about 250MB with DX9c, audio, many drivers, but very fast with 1 GB RAM. smile.gif

I have translated your web page for other English users and so that I'll be able to study it a little more easily.

http://thuun.boot-land.net/MobileOS.htm

So far I only interpreted and edited the title, all else is roughly translated.
Hasta luego, amigo.

Posted by: euhenio Mar 30 2007, 12:59 AM

Thank you ever so much !
I check your work.

Today I have finished fixreg. He is very alike by base MobileOS. Also it is possible to load mine Last session.



Go to " Download Center " , press button " Add a new web server " - paste mobileos.boot-land.net.

Posted by: euhenio Mar 30 2007, 01:52 AM

thuun

I think there is no sense in metaphrase .
Remaking him to the your taste.

It is better to use GRUB and SYSLINUX separately, so far as probably delay of work memory .

After completion of scripts I shall change http://euhenio.mam.by/

Posted by: Nuno Brito Mar 30 2007, 03:45 AM

QUOTE(euhenio @ Mar 30 2007, 12:59 AM) *
....
Go to " Download Center " , press button " Add a new web server " - paste mobileos.boot-land.net.


Congratulations on your webserver - do makes it a lot easier to get all files..

Trying your web server I noticed two projects listed maybe it would be simpler to use a single project inside mobileos.boot-land.net.

Also one small typo under the last session script - shouldn't the button say "Get file"?

Nice work so far!! thumbup.gif

Posted by: euhenio Mar 31 2007, 01:16 AM

Nuno Brito


These are different projects. When I shall complete MobileOS_new I shall rename him in MobileOS.

Posted by: Nuno Brito Mar 31 2007, 09:04 AM

Ok, thanks for explaining the difference! laugh.gif

Posted by: euhenio Apr 7 2007, 01:24 AM

Version 002
Public version (beta testing)
You needed in following collection files :

Microsoft® Windows® XP Professional SP2 EN
minlogon.exe Microsoft® Windows® XP Embedded
ramdisk.sys Microsoft® Windows® Server 2003 SP1
nLite 1.3 Windows customizer Dino Nuhagic
QEMU on Windows Version 0.9.0 Fabrice Bellard
Virtual Disk Driver Ken Kato
WinBuilder © Nuno Brito rolleyes.gif

7-Zip © Igor Pavlov also should be installed

You also should provide that other processes e.g. antivirus, explorer etc. have not blocked temporary virtual drive as it can spoil result

All still remain more quantity small bugs which I shall correct in the future.

Posted by: thunn Apr 9 2007, 03:03 PM

OK...wiz kids.

Right now I'm trying to boot a regular xpsp2 image from ISO using suggestions spread throughout threads you know of including mobileos registry settings and updating IDE drivers to generic. I Added a grub chainloader renamed as setupldr.bin in i386 next to ntdetect.
ISO boots and loads grub which loads boot.ini in root which then loads xpcore.ima.. loading ramdisk image... then,
'ntoskrnl.exe not found/corupt' message

Filedisk was used to make the image, perhaps the problem is the drive is not 'mapped' right. I'm looking at vmware-mount.exe now. I was going to image a udf disk and load it with bcdw2 if no success. I did that before but it loads a bit slow if I remember right. Of course, thoughts on this are most welcome!

my image root is currently like this..
----------------------------------
\I386 DIR
\ntldr 295536 b <--from s2k3 R2 not setupldr.bin renamed
\XPcore.ima 260046848 b
\boot.ini 167 b

\I386\setupldr.bin 167328 b <---Grldr
\I386\NTDETECT.COM 47772 b
-----------------------------------
(w/xp bootsector)

one more note,
I have not changed the main PC driver to 'Standard', just the 3 IDE drivers. Minlogon is used and the system boots well normally.
:rollseyes:

Posted by: euhenio Apr 9 2007, 04:41 PM

Problem in wrong XPcore.ima

I recommend to test my version 002
Me seems you there will find answers

Posted by: thunn Apr 9 2007, 09:02 PM

yes..
I tried but received an error that your script cannot find a folder in gub dir.
I downloaded regular grub for dos 042 which does not have the missing folder.
I need the link to your grub!!
Please always provide download links to components used, it will help your project to be more friendly. laugh.gif

So I'll do it manually,
this is a help here:

CODE
ShellExecute,Hide,"%qemu%\qemu-img","create %targetdir%\ram.img %pFileBox1%M"
ShellExecute,Hide,"compact","/u %targetdir%\ram.img"
ShellExecute,Hide,"%vdk%\vdk.exe","open * %targetdir%\ram.img /rw /p:0 /l:%tmpltr%"
ShellExecute,Hide,"format","%tmpltr%: /FS:NTFS /V:MobileOS /Q /C /x /FORCE"




Too bad nLite has no cmdline. Maybe we can use batch files soon. smile.gif

 xp_cmpnt_removal.7z ( 51.91k ) : 23
 

Posted by: euhenio Apr 9 2007, 11:58 PM

QUOTE
I tried but received error that your script cannot find a folder in gub dir.

I in confusion! Such should not be. More in detail please.
In version 002 grub is not mentioned!
QUOTE
Too bad nLite has no cmdline.

Too it is not pleasant for me.
QUOTE
Please always provide download links to components used, it will help your project to be more friendly.

These links seem to me are obvious

nLite - http://www.nliteos.com/

VDK - http://chitchat.at.infoseek.co.jp/vmware/vdk.html

QEMU - http://www.h7.dion.ne.jp/~qemu-win/

Posted by: thunn Apr 10 2007, 12:21 AM

sorry..
it was an was error with qemu, a subdirectory was missing.
Just add some web links. smile.gif

Posted by: euhenio Apr 10 2007, 01:02 AM

QUOTE
xp_cmpnt_removal.7z

It is very interesting, whence it?

Posted by: thunn Apr 10 2007, 08:30 PM

Those batch files were made by msfn member jdeboeck, they for XPsp1.
His website is now gone.
I made one or two changes/additions..
Using just components, no drivers, they still work perfectly on xpsp2.
--
I know it may seem obvious, but to eliminate confusion,
Why not add 'weblinks' to your script UI? smile.gif

I always do this so people do not even have to open another application, just click, bang, zoom, done. laugh.gif

I'm attaching the error message. qemu does not contain a pc-bios directory, please download the English dist. and see.

btw..
I have a cd booting with boot.ini and no grub, instead server 2k3sp1 ntldr is renamed as setupldr.bin. This is what I overlooked, a most excellent 'trick'. However, at start of boot files begin to load and it freezes loading acpitbl.dat. I wish I had more time for this! let me know if the lproblem sounds familiar. smile.gif

--
the 'trick'
ROOT:
I386 (DIR)
boot.ini
xpcore.img

I386:
NTDETECT.COM
SETUPLDR.BIN <--NTLDR renamed, from Svr2K3 sp1

--

 

Posted by: MedEvil Apr 10 2007, 10:05 PM

QUOTE(thunn @ Apr 10 2007, 10:30 PM) *
btw..
I have a cd booting with boot.ini and no grub, instead server 2k3sp1 ntldr is renamed as setupldr.bin. This is what I overlooked, a most excellent 'trick'.
--

confused1.gif 2k3sp1 ntldr can read cdfs?

cheers.gif medieval.gif

Posted by: euhenio Apr 11 2007, 12:55 AM

thunn

QUOTE
Using just components, no drivers, they still work perfectly on xpsp2.


I shall try to convert it in scripts

QUOTE
I'm attaching the error message. qemu does not contain a pc-bios directory


Sorry , it demands attentive studying this page http://www.h7.dion.ne.jp/~qemu-win/

QUOTE
QEMU 0.9.0 binary.
http://www.h6.dion.ne.jp/~kazuw/qemu-win/Qemu-0.9.0-install.exe
BIOS is in a pc-bios directory. Use -L like this.
-L "C:\Program Files\Qemu\pc-bios"

only 4.1 Mb

QUOTE
This is what I overlooked, a most excellent 'trick'.


This unusual case

Posted by: thunn Apr 11 2007, 04:10 AM

I had almost called it a night when low and behold, after days of tinkering, there it was..
the StandardXP nRAM aka MobileOS boot screen!
laugh.gif
euhenio, thank's for your contributions. Between your scripts and the info at CD Forum, I've now got it figured out. I'm posting from a 100MB XP in RAM now, it work's very well, I go to bed happy tonight...
Some tools I've been using can be found http://thuun.boot-land.net/WinBldr/XP-2K3/Projects/Tools/.
I'll post details on some pitfalls to avoid in the process after I organize the build in the morning. Maybe we should petition nuhi to add cmdline functionality to nlite for such projects. I have no complaints about the build I'm using (my nlite xpcore.ini presets are in dir. linked to above) Note that I also deleted a handfull of useless files with a batch file I made.

G'night all.
thumbsup.gif

--edit--
I'll post a few more details tonight, but for those interested, MS Virtual PC can NOT be used to install the system to be imaged, I wound up using VMWare after wasting some time.
--------
................
\success..
ntldr renamed as setupldr.bin loads the boot.ini which loads the
filedisk based .ima file, booting here from ISO (no grub loader)..


 

Posted by: Nuno Brito Apr 11 2007, 08:36 AM

Congratulation, looks fabulous! thumbup.gif

Now it's only missing to completely automate the process, nlite tweaks can also be duplicated - let me know what it is needed and I will help getting it done..

These are good news! thumbsup.gif

Posted by: euhenio Apr 11 2007, 07:02 PM

QUOTE
ntldr renamed as setupldr.bin loads the boot.ini which loads the
filedisk based .ima file, booting here from ISO (no grub loader)..


Probably the mistake was in it

bios > setuptldrbootsector > \i386\setupldr.bin(renamed grldr) > \ntldr > \boot.ini > \i386\ntdetect.com > \ram.img

This incorrectly, correctly will be so:

1. bios > grldr(boot sector,no emulation) > \ntldr > \boot.ini > \i386\ntdetect.com > \ram.img

95% success , multiboot ok

2. bios > setuptldrbootsector(in installation cd) > \i386\setupldr.bin(renamed ntldr) > \boot.ini > \i386\ntdetect.com > \ram.img

100% success (if it is possible) , no multiboot


Also VDK will convenient for IMG more, but filedisk necessary for ISO

Nuno Brito
QUOTE
Now it's only missing to completely automate the process

I do already it
In some days you can test it

Posted by: Nuno Brito Apr 11 2007, 07:33 PM

I'm really looking forward to try it out! yahoo.gif

Good luck!! victory.gif

Posted by: thunn Apr 13 2007, 03:29 PM

ok..
With the 'installer' of qemu, the project now moves into motion...
(prior to this I had been trying to use the downloaded .zip of qemu which has a different structure when unpacked to disk).

I placed all needed files in "c:\mos"
Qemu starts and begins to install the nlited iso...however, on reboot after copying files in txtmode, the script errors out with message like.. "install failed". So, I wonder now if anyone has successfully run these scripts to completion. Oh well, my manully assembled XPnRAM is flying right along, so it doesn't ruin my day.
I will do my best over the next few days to review things and put them into a working script(s), or at the very least, post a tutorial for interested users that don't speak Russian.

I was under the impression that MobileOS took files directly from the nlited source media to create the runtime image and no setup was required. Is the qemu phase simply a test? I'll have to review the scripts more completely.

Posted by: euhenio Apr 13 2007, 11:54 PM

For me v002 on 100 % the worker.
In version 003 nLite will not be - probably it will increase chances.
Also it is necessary to remember:

QUOTE
You also should provide that other processes e.g. antivirus, explorer etc. have not blocked temporary virtual drive as it can spoil result

Posted by: thunn Apr 14 2007, 03:31 AM

thx for that thought euhenio, I usually do disable my avast, who knows, maybe I forgot. wink.gif
At any rate,
I've now done several test builds and have found VMware to be my tool of choice for creating standardized XP builds for use in RAM. The fact that I used the MS product before spoiled many early test builds.
The vmware MSI installer can be reduced to produce a 15 MB setup which was worth a moments work in an MSI editor earlier.

Posted by: euhenio Apr 23 2007, 11:23 PM

Disk image ( qemu.script ) should be one fragment

Run dfrg.msc for check it

Posted by: euhenio Apr 26 2007, 12:18 AM

Version 003

-nLite
+Usb support

see first page for detail

Posted by: Nuno Brito May 4 2007, 10:43 PM

Any more updates?

I'm ready for testings!! thumbup.gif

Posted by: euhenio May 5 2007, 11:03 PM

You tested version 003 ?

Posted by: fdhd May 6 2007, 08:38 PM

QUOTE(euhenio @ May 5 2007, 11:03 PM) *
You tested version 003 ?

PLEASE
HOW TO DOWNLOAD SCRIPTS ? confused1.gif

Posted by: Nuno Brito May 6 2007, 09:16 PM

fdhd, you can download all files from the Download Center inside Winbuilder.

--> Open Winbuilder
--> Download Center
--> Press the + button to add a new webserver (wb068) or Press Options and then press the above mentioned + button (wb069 and above)
--> Type the name of the new webserver: mobileos.boot-land.net
--> Press Download to get all files (wb068) or Select Complete (wb069 and above) and press Download


Euhenio, haven't yet tried them but I wanted to test your project intensively and see how I can help you.

There is also one detail: The download center has changed a bit since 068 - can you reupload your webserver again using the download profile - otherwise people will have to select the "Complete" profile all the time just to download your project, it should be changed to the "Recommended" profile.

Small details:

There is a Proect.script file which should be "Project.script" and the files on the RamImg folder should also be named as "1-1_Preparation.script" instead of "1-1preparation.script" to ease the reading.. wink.gif

Your webserver will be added on the next wb release so I'll surely help you correct these cosmetic corrections..

cheers.gif

Posted by: thunn May 6 2007, 11:31 PM

That would be great. I've only been able to use the information in the scripts until now, when attempting to run the project to completion, various errors have prevented me from seeing what euhenio wants to share. As I've examined the different scripts in the project, clearly there's an amazing idea at work here, but it could use some fine tuning, who better than Nuno. thumbsup.gif

As the project matures,
please consider the following..

(1)
The project assumes you are currently using nlited XP, not ideal. It collects hives from the users system for use in 'MobileOS' and adds some updates including the essential ramdisk driver entries. Some registry items are removed including the 'mounted devices' key.
There are a few possible sollutions, Nuno's been working in the registry a bit lately, so hopefully he can point to a good way to generate the needed hives without taking them from the current system in use.

(2)
Testing mechanism.
The project can easily be tested without use of a physical system. Right now I'm using a script to image my build called "http://thuun.boot-land.net/WinBldr/XP-2K3/Projects/NativePE/Finish/CreateBcdwPE.script". The multiboot image produced will allow you to test full versions of XP InRAM using a virtual machine. To use it, add grub (MobileOS loader) to the 3rd or 4th boot option and re-image the build after copying the folders from MobileOS to the root dir..
I'm not saying it souldn't be tested on a real system, it should.

(3)
All the tools used in the project are freeware. thumbsup.gif
I suggest uploading the files to a "Tools" folder for users so they don't have to play guessing games and search the net before beginning. The easier it is to use, the more people will use it.

(4)
Less branding shows more class.
e.g.
Name the volume(s) something like %Version%_Disk instead of MobileOS, or better yet, provide a textbox. wink.gif

And I'll be happy to update this post to reflect development. smile.gif

Posted by: Nuno Brito May 6 2007, 11:51 PM

I very much agree with your opinion!

MobileOS was also added as a webserver on the present wb beta.

Thank you very much for the road map - a guide was indeed needed.. thumbup.gif

Posted by: euhenio May 7 2007, 12:09 AM

Nuno Brito

Thanks for corrections.

QUOTE
people will have to select the "Complete"profile all the time just to download your project


maybe this profile should be default profile

after release new stable version Winbuilder I shall make necessary changes

Posted by: thunn May 7 2007, 12:15 AM

I'd be greatfull to see my suggestions put to use and I'm glad they seem reasonable.

Posted by: euhenio May 7 2007, 12:41 AM

thunn

QUOTE
The project assumes you are currently using nlited XP, not ideal

version 005 using full xp installation(she is almost ready)

QUOTE
Testing mechanism.

For this , is test.script . what you receive inconveniences?

Posted by: bilou_gateux May 9 2007, 08:30 PM

QUOTE(thunn @ Mar 12 2007, 08:39 AM) *
That's right, no install, just restore or load!
I already know where to export most all of the DigitalProductIDs, WPA, WGA.. (etc.) entries from in the registry.
It will be easy for me to start building a script and concentrate on the registry patching once the nlite build is imaged and ready for building lists. thx!

---
...and now I'm posting from the nlited system that just finished installing, It's about 20-30MB. bigger than yours, but still very fast even in a VM!
No IE front end, but the engine was left so I'm using explorer to surf the net before going to sleep. smile.gif I'll try your presets tomarrow.

here I am wink.gif..


Hi thunn, would you like to send me a private message with the infos you have collected about entries from in the registry.
My purpose is not to hack/crack my Windows OS. I have a COA sticker from my OEM manufacturer on the case.
I just want to inject to a prebuilt Windows Embedded runtime image xxxxx-215-xxxxxxx-xxxxx <> Product Key xxxxx-OEM-xxxxxxx-xxxxx from licenced Windows XP Professional OEM SLP installation i have.

QUOTE(thunn @ Apr 14 2007, 04:31 AM) *
The vmware MSI installer can be reduced to produce a 15 MB setup which was worth a moments work in an MSI editor earlier.

VMware Server 1.0x or Workstation 5.5x/6.x?

I'm looking for a tutorial to edit VMware Server standalone MSI to remove ISO images from it.

Posted by: euhenio May 9 2007, 11:52 PM

version 005 is available thumbup.gif

Posted by: Alexei May 10 2007, 01:27 PM

QUOTE(euhenio @ May 9 2007, 04:52 PM) *
version 005 is available thumbup.gif

Congratulations thumbup.gif
I'll test it soon smile.gif

BTW
I have an idea I hope you may consider useful. I propose to use "last access" stamp to determine which files were actually used.
I mean like that:
- Boot the OS
- Go over everything you may need in the future.
- Check which files were actually "touched".
Theoretically, that would allow to delete all files you don't need.
Of course, it's more complicated with Mobile OS...
cheers.gif
Alexei

Posted by: euhenio May 11 2007, 12:02 AM

Thank for idea.
However here is necessary more thoroughly analysis

Posted by: thunn May 11 2007, 05:52 AM

I have not seen it, does it use a VM?

Posted by: TheHive May 11 2007, 06:27 AM

Any pics of the project working in bootup.
Will the new scripts posted in the new MobileOS server work out of the box or are there certain steps to get certain results.

Posted by: hooovahh May 11 2007, 01:34 PM

QUOTE(thunn @ May 11 2007, 01:52 AM) *
I have not seen it, does it use a VM?

Yes it actually uses Qemu. You run the script and it will prepare the files, and create the windows xp iso, then mount the iso in qemu and install it. After that it uses the hard disk image in createding the MobileOS that gets loaded into ram.

I haven't finished it personally but I got most the way through the install and realized I wouldn't have enough ram to load a full xp install, so I quit until I have a minimal xp ready to try it out on.

Posted by: euhenio May 12 2007, 12:08 AM

For realization my project to you should suffice 256 Mb system ram
However it can occupy some hours

Posted by: greno May 12 2007, 10:17 PM

Hi euhenio,
I am in the middle of building the XP RAMdisk from this post:
http://www.911cd.net/forums//index.php?showtopic=19056&hl=Ramdisk&st=20

and in there is a link to your registry patch, http://euhenio.mam.by/mobileos/MobileOSregPatch.reg .
But this link no longer works. confused1.gif Did you move this file? Or is there another replacement file that can be used?

Thanks,
Gerry

Posted by: greno May 12 2007, 11:19 PM

I found you new website for file downloads and I think this file may be the same reg patch:
http://mobileos.boot-land.net/old/regpatch.reg

Let me know if that is right. smile.gif

Thanks,
Gerry

Posted by: greno May 12 2007, 11:56 PM

Some problem.
I opened the registry and clicked on HKEY_USERS and loaded the hive from Q:\WINDOWS\System32\config\system as keycode 'sys'.
Then I try to import this patch but it always gives me the error: "Cannot import C:\Documents and
Settings\Administrator\Desktop\regpatch.reg: Error accessing the registry."
I have checked permissions and everything looks right. confused1.gif

Thanks,
Gerry



Posted by: euhenio May 13 2007, 12:02 AM

HKEY_LOCAL_MACHINE

Posted by: greno May 13 2007, 12:05 AM

Found the problem. Needed to click on HKEY_LOCAL_MACHINE instead.

biggrin.gif

Posted by: greno May 13 2007, 02:08 AM

euthenio,
I finished all the steps and burned a CD. Then I put the CD into one of my machines and rebooted but the CD did not boot. It just went like normal boot. How to make the CD bootable?

CD looks like:

i386\ntdetect.com
boot.ini
grldr
i386
ntldr
winxp.img

boot.ini:

[boot loader]
timeout=10
default=ramdisk(0)\WINDOWS
[operating systems]
ramdisk(0)\WINDOWS="RAM Boot XP" /rdpath=\winxp.img /fastdetect /SOS /BOOTLOG

grldr is patched


Files from W2K3:
ntldr
ntdetect.com
ramdisk.sys (inside winxp.img)



Thanks,
Gerry

Posted by: euhenio May 13 2007, 11:27 PM

Re-read this post
http://www.boot-land.net/forums/index.php?showtopic=1218&view=findpost&p=12142

Posted by: greno May 14 2007, 02:06 AM

QUOTE(euhenio @ May 13 2007, 11:27 PM) *
Re-read this post
http://www.boot-land.net/forums/index.php?showtopic=1218&view=findpost&p=12142


Ok, I read the post.

Here are things that I am changing:

Changed all filenames to uppercase. Including references in boot.ini.

I am somewhat confused by the recipe in this post:
http://www.911cd.net/forums//index.php?showtopic=19056&view=findpost&p=127706

It shows 'GRLDR.BS' Does '.BS' mean 'BootSector'? Is this the same as the GRLDR from Grub4DOS? That's what I have used.

Here is my 'GRLDR':
>dir grldr
05/12/2007 08:40 PM 167,328 GRLDR

Can a file this big be a bootsector?

Does this become the '-b' argument to mkisofs?

=============================================
And a probably really bad Russian Google translation of above text:

Ок, я прочитал этот пост. Вот, что скажу : Изменен все имена файлов в верхний регистр. Включая ссылки в файле boot.ini. Меня несколько смущает рецепт в этой должности : http://www.911cd.net/forums//index.php?showtopic=19056&view=findpost&p=127706 Он показывает "GRLDR.BS" ли ". ББ "означает" BootSector "? Это же как с GRLDR Grub4DOS? Вот все, что я хотел использовать. Вот мои 'GRLDR' :> каталог grldr 05/12/2007 8.40 ПМ 167,328 GRLDR Может это большой файл будет загрузочным? Означает ли это, стать "б" аргумент для руководства?


Posted by: greno May 14 2007, 03:12 PM

I almost have it working! I needed -no-emul-boot.

So now I get the NT Boot List, but when I select "RAM XP Boot" it just says cannot open the RAMDISK file. But it is there! confused1.gif

\WINXP.IMG

My boot.ini has:

[boot loader]
timeout=10
default=ramdisk(0)\WINDOWS
[operating systems]
ramdisk(0)\WINDOWS="RAM Boot XP" /rdpath=\WINXP.IMG /fastdetect /SOS /BOOTLOG


What is wrong with this?

Posted by: greno May 14 2007, 06:31 PM

Still stuck. frusty.gif

Here's my md5 checksums (taken in Cygwin):

3d898d10b949a0cc6574d930d84f5630 *GRLDR
971757832f7dd9516977985999f527ca *NTLDR
cdce1413695a6ace7304e77f35aa3a37 *i386/NTDETECT.COM


These are all W2K3 versions taken from W2K3 Enterprise.

Anything look wrong here?


And only 1 try out of very many I get this error message:

Windows could not start because the following file is missing
or corrupt:
<Windows root>\system32\ntoskernel.exe
Please re-install a copy of the above file.


Also, my RAM image file is 512M. Would that cause this specific symptom that I'm seeing?
$ls -lh *.img
-rwx------+ 1 greno None 512M May 12 20:10 winxp.img

>dir *.img
05/12/2007 08:10 PM 536,870,912 winxp.img

I already tried substituting a smaller image file (picture) and it produced the exact same error:

Windows could not start due to an error while booting from a RAMDISK.
Windows could not open the RAMDISK image.


Posted by: greno May 14 2007, 11:12 PM

Finally found something at MSDN:

QUOTE
If a Preboot eXecution Environment (PXE) client attempts to download an image that is too large to run in memory, the following error message is displayed: "Windows could not start due to an error while booting from a RAMDISK. Windows failed to open the RAMDISK image." This error means that the client computer does not have enough RAM for the current RamDisk image to run.


But that is just wrong! blink.gif My machine has 2G of memory.

Is there some memory setting that needs adjusted? confused1.gif


Posted by: euhenio May 14 2007, 11:23 PM

Limitation in 512M is possible to overcome easily
For this the Disk Y ( http://www.boot-land.net/forums/index.php?showtopic=1218&view=findpost&p=9250 ) should be second ramdisk (Qsoft)

Posted by: greno May 14 2007, 11:54 PM

euhenio,
What I do not understand is why I cannot load even small photo image of 100k. It should try to load that into memory. But it produces the same error. This does not make sense.

Ok, did crazy thing. Used 'dd' to cut RAM image in half = 256M. Then retried boot. This time I got error "NTDETECT failed".

So what does this mean? Is this good or bad?


Posted by: euhenio May 15 2007, 12:29 AM

there is script http://www.mobileos.boot-land.net/euhenio/v005/Tools/IMG_and_ISO.script
It creates bootable CD from Ram.img
Using him as the sample you will find the mistake

Posted by: thunn May 15 2007, 03:27 AM

greno, I started a small guide to remind myself about the build details after having some good results booting a 100 MB nlited xp inram..
http://thuun.boot-land.net/XPnRAM/
Contained in the page are tools I used.

Posted by: greno May 15 2007, 03:46 AM

euhenio, thunn,
Thank you for these suggestions. I am still working on getting the RAMDISK to be recognized. First, I think I will try to make a smaller image and see if that helps. Being right at 512M might be part of the problem.

Gerry

Posted by: TheHive May 15 2007, 05:59 AM

QUOTE(thunn @ May 14 2007, 10:27 PM) *
greno, I started a small guide to remind myself about the build details after having some good results booting a 100 MB nlited xp inram..
http://thuun.boot-land.net/XPnRAM/
Contained in the page are tools I used.

You should add that link to the Tutorial section.

Posted by: hooovahh May 15 2007, 01:35 PM

QUOTE(thunn @ May 14 2007, 11:27 PM) *
greno, I started a small guide to remind myself about the build details after having some good results booting a 100 MB nlited xp inram..
http://thuun.boot-land.net/XPnRAM/
Contained in the page are tools I used.

Very nice I always appreciate a well written how-to.

I will attempt your procedure soon but I do have a question, how do you guys add drivers to this compilation? Like say for a PCI TV Tuner. (just an example), how could I install these drivers in the VMWare machine so that when I booted this XP into ram on a real machine, which contained the PCI TV Tuner it wouldn't need a restart to use the hardware, since a restart would clear the ram drive and start the process all over again.

Some times I explain things in too much detail so here's the executive summary: How can I add drivers to my XP in Ram image, so that it won't require a reboot to use that new hardware?

Posted by: greno May 15 2007, 08:57 PM

Ok, I reduced the size of the image to 499M but I'm still not having any luck getting this working:

Here is my ISO create commands:
>mkisofs.exe -iso-level 4 -force-uppercase -volid RAMXPBOOT -no-emul-boot -o \Temp\RAMXP.iso -b GRLDR . REM note the '.' for current directory

The above command results in a "unable to open RAMDISK" error.

I get the same error in both VMware and on a real machine.

All my files are listed in previous posts if someone wants to look at them.


What I don't understand is that others have claimed to have succeeded with this technique and I followed in their footsteps and yet cannot repeat their success.

Everything was built in Windows XP SP2
The created nLited image is Windows XP SP2
The ramdisk.sys and NTLDR are from W2K3 Server Enterprise.

I have redone this exercise about 10 times with the same result everytime.

I don't want to start over with a different technique. I want to understand what is wrong in the technique that I am using.

Any help greatly appreciated.

Posted by: euhenio May 15 2007, 11:31 PM

You can download my project and to test him is. It an automatic method
Probably so you will find your mistake more quickly

Posted by: greno May 15 2007, 11:43 PM

euhenio,
For running your script, what does your build tree look like and what environment variables do I need to set?

Gerry


Posted by: euhenio May 16 2007, 12:38 AM

source directory - is installation CD
target directory - better empty fat32 partition ~5Gb , even better diffirent phisical disk (non system)

result:

Ram.img - image ramdisk (kernel - 64Mb)
Bin.img - mbr+partition1 (1Gb) image for r/w disk, not less 1Gb

Posted by: greno May 16 2007, 01:48 AM

euhenio,
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

Posted by: euhenio May 16 2007, 09:05 AM

you should be re-selecting http://mobileos.boot-land.net

Posted by: greno May 16 2007, 12:51 PM

QUOTE(euhenio @ May 16 2007, 09:05 AM) *
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?

Posted by: euhenio May 16 2007, 11:49 PM

version 006

fix "Rpc server"
fix "redirector"
some small tweaks

Posted by: euhenio May 17 2007, 12:10 AM

qreno

save log.html , 7ziping him and give me

Posted by: greno May 17 2007, 12:35 AM

QUOTE(euhenio @ May 17 2007, 12:10 AM) *
qreno

save log.html , 7ziping him and give me


Performed new d/l. Reran MobileOS. Still same error. Log attached.

 log.html ( 106.92k ) : 10




Posted by: euhenio May 17 2007, 12:59 AM

And these files really exist?
use real CD
Do not use long path and blanks

Posted by: greno May 17 2007, 01:12 AM

QUOTE(euhenio @ May 17 2007, 12:59 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 ) : 9

Posted by: euhenio May 17 2007, 01:22 AM

use v006

Posted by: greno May 17 2007, 01:30 AM

QUOTE(euhenio @ May 17 2007, 01:22 AM) *
use v006


How do I select V006? I redownloaded MobileOS. Shouldn't that bring down V006?


Posted by: greno May 17 2007, 01:34 AM


I redownloaded it again and this time it brought down V006. So I will try this.

Posted by: greno May 17 2007, 01:38 AM

QUOTE(greno @ May 17 2007, 01:34 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 ) : 10

Posted by: euhenio May 17 2007, 01:49 AM

go to "proect"

Files which at you are not present - this critical files
Your CD really spoiled
attempt other CD/DVD

Posted by: greno May 17 2007, 02:08 AM

QUOTE(euhenio @ May 17 2007, 01:49 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:

CODE
├───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.
CODE
BinImg <> Bin.img
RamImg <> ram.img

And again in script it is looking for X: rather than D: so it thinks that the Source disk is missing.
CODE
X: <> D:


Posted by: euhenio May 17 2007, 02:31 AM

└───v006
├───Project (script not folder) !!!
├───BinImg
├───RamImg
└───Tools

Posted by: euhenio May 17 2007, 02:40 AM

QUOTE
go to "proect"

project

Posted by: greno May 17 2007, 02:40 AM

QUOTE(euhenio @ May 17 2007, 02:31 AM) *
└───v006
├───Project (script not folder) !!!
├───BinImg
├───RamImg
└───Tools


This is from DOS tree command. Here is the expanded listing:

CODE
└───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

Posted by: euhenio May 17 2007, 08:34 AM

All is true
In Project.script (title Project) you choose "Source Disk" , "Target directory " and "Target directory for Ram.img"

Posted by: euhenio May 17 2007, 10:02 AM

CODE
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

Posted by: greno May 17 2007, 01:25 PM

euhenio,
I am sorry to tell you this but I am still seeing nearly the exact same errors:

CODE
Target directory (Bin.img ) not exist.
Target directory for ram.img not exist.
Source disk not exist.


 log_V006_2.html ( 9.66k ) : 5


And 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:

QUOTE
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.

QUOTE
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!

QUOTE
>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 ) : 8



frusty.gif

Posted by: euhenio May 17 2007, 05:26 PM

Ok , send me

CODE
dir d:\i386

Posted by: greno May 17 2007, 05:32 PM

QUOTE(euhenio @ May 17 2007, 05:26 PM) *
Ok , send me
CODE
dir d:\i386



 cdi386.txt ( 66.95k ) : 14


 cdi386_full.txt ( 273.5k ) : 7



euthenio,
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".

Posted by: euhenio May 17 2007, 06:55 PM

probably your CD - Service Pack 1
integrate Service Pack 2 and try again

Posted by: greno May 17 2007, 07:00 PM

Didn't work. Got error message about CD already has integrated updates.

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.


Posted by: euhenio May 17 2007, 11:51 PM

After integration should there will be following files

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

Posted by: greno May 18 2007, 12:03 AM

euhenio,
My point was why even bother with requiring SP2? Just use whatever the user has for XP. XP wo/SP, XP w/SP1, XP w/SP2. Don't even check which version. Just make the RAM image from whatever they give you.


Posted by: greno May 18 2007, 12:10 AM

euthenio,
Can you answer this?
Can I create an nLited WinXP image and use it in MobileOS without needing XP w/SP2?



Posted by: euhenio May 18 2007, 12:52 AM

QUOTE
Just make the RAM image from whatever they give you.

this assumes many variants - I cannot assume

QUOTE
Can I create an nLited WinXP image and use it in MobileOS without needing XP w/SP2?


No , you need in normal winxpsp2 install-cd


Posted by: euhenio May 18 2007, 07:12 PM

qreno

QUOTE
My point was why even bother with requiring SP2? Just use whatever the user has for XP. XP wo/SP, XP w/SP1, XP w/SP2. Don't even check which version. Just make the RAM image from whatever they give you.


Hm... This good idea !
I shall try to change project cheers.gif
But it will occupy some time.

Posted by: euhenio May 22 2007, 11:11 PM

I found mistake in version 006

file [7zip directory]\codecs\Branch.dll
should be copied in
[winbuilder directory]\codecs

Posted by: greno May 23 2007, 12:50 AM

Hi euhenio,
Just let me know when I can use MobileOS with my existing OEM XP CD.

thanks,
Gerry

Posted by: euhenio May 24 2007, 01:27 AM

Version 007

only WinBuilder 071 beta 2

Posted by: euhenio May 24 2007, 12:53 PM

Version 007 Updated

Posted by: euhenio May 24 2007, 11:54 PM

greno

you tested version 007 with the your OEM XP

Posted by: greno May 25 2007, 12:54 AM

QUOTE(euhenio @ May 24 2007, 11:54 PM) *
greno

you tested version 007 with the your OEM XP


OK, I d/l 071b2 and d/l 007.
checked only RamImg, clicked Version and filled in paths.
clicked button.

It is prompting me for 7z.dll I located and found, but also:
cab.dll
lzma.dll
Branch.dll
dd.exe
ntldr
vdk.exe
vdk.sys
qemu.exe
qemu-img.e
fmod.dll
SDL.dll
bios.bin
vgabios.bin

Even though all these failed, it says "Ok, Check is executed"
"Now select WinBuilder.exe" which I do, and then it says:
"Unknown error"

so I am stuck here.

confused1.gif

Posted by: bicarbon May 25 2007, 02:30 PM

Hi,

First to say this must be the Holy Grail of OS!
Very well done euhenio, thun & nuno

Maybe someone could point out my noob error on check paths?



then hit ok



thanks in advance
bic

Posted by: greno May 25 2007, 02:41 PM

bicarbon,
You've run into the same issue that I'm trying to work through with v007. I'm sure euhenio will either change something or respond shortly and let us know what to do to get by this problem.

Gerry

Posted by: euhenio May 25 2007, 09:27 PM

Strange ... I updated :

Version
BinImg
Tools\Cleaning project

Redownload this > Version > click "check project and set new paths now" > Log > save log.html > and will send here

Posted by: greno May 25 2007, 09:50 PM

QUOTE(euhenio @ May 25 2007, 09:27 PM) *
Strange ... I updated :

Version
BinImg
Tools\Cleaning project

Redownload this > Version > click "check project and set new paths now" > Log > save log.html > and will send here



Here is my last log:

 log_V007_1.html ( 115.4k ) : 10

Posted by: euhenio May 26 2007, 01:24 AM

use WBbeta2

you should find this file using navigation on folders

Posted by: greno May 26 2007, 02:07 AM

QUOTE(euhenio @ May 26 2007, 01:24 AM) *
use WBbeta2

you should find this file using navigation on folders


I am. It identifies itself as WBb1 but it is from the WBb2 zip file.

The 7z.dll is no problem but there are many other missing files that are not found with a search.

Gerry

Posted by: euhenio May 26 2007, 02:31 AM

Ok. 7z updated - "Version" also is updated !

Posted by: greno May 26 2007, 02:42 AM

QUOTE(euhenio @ May 26 2007, 02:31 AM) *
Ok. 7z updated - "Version" also is updated !


Ok, it no longer prompts for 7z.dll BUT it is still prompting for many many other files which are not found.

And then it still ERRORS at end.

Maybe there should be box to enter path to TOOLS DIR?

Gerry

Posted by: bicarbon May 26 2007, 05:12 AM

Hi,

Folder navigation file type defaults to "euhenio" (root dir name)

with no choice to change to 7z.dll type

so file cannot be selected

maybe bug?

Best,
bic

Posted by: euhenio May 26 2007, 06:48 PM

binary files are not included in project !

links for downloads you find on first page and other pages in this topic


Posted by: greno May 26 2007, 07:25 PM

Ok, I d/l all the binaries; set the paths and ran the Version script; that seems ok.
Next I ran the BinImg and RamImg scripts and they fail with an error in creation of bin.img

Here is log:

 log_V007_2.html ( 52.33k ) : 10



Gerry

Posted by: euhenio May 26 2007, 11:54 PM


DO NOT USE LONG PATH !!!

--------------------------------------------

MobileOS International ?


BinImg \ Copy and Expand - updated

RamImg \ Localisation - New !


------------------------------------------

files for version 007


 

Posted by: greno May 27 2007, 12:41 AM

QUOTE(euhenio @ May 26 2007, 11:54 PM) *
DO NOT USE LONG PATH !!!


I do not understand this. Where? On Version page? When prompted for binary locations?
I just put where I have things. So are you meaning ABSOLUTE path? If it's RELATIVE, relative from where?

Gerry

Posted by: euhenio May 27 2007, 01:21 AM

Example :

C:\Programs\7z\7z.exe
C:\WB\Winbuilder.exe
C:\WB\Projects\updates.ini
C:\WB\Tools\cfadisk.sys
E:\Target\bin.img
F:\Target\ram.img

Posted by: greno May 27 2007, 01:52 AM

QUOTE(euhenio @ May 27 2007, 01:21 AM) *
Example :

C:\Programs\7z\7z.exe
C:\WB\Winbuilder.exe
C:\WB\Projects\updates.ini
C:\WB\Tools\cfadisk.sys
E:\Target\bin.img
F:\Target\ram.img


A suggestion. MobileOS should take whatever files, directories, binaries, etc. that we give it and then just copy all that stuff to some temporary work area with a SHORT PATH if the program requi a short path.
I have all my build tools under my home directory C:\Documents and Settings\greno\Builds. But even this seems too long for MobileOS. Each user account has their own work area under their own home directory. This is quite normal.


Posted by: euhenio May 27 2007, 11:07 AM

C:\Documents and Settings\greno\Builds thumbdown.gif

C:\Users\greno\Builds smile.gif

(C:) Qreno - very good !!! thumbup.gif

Posted by: greno May 27 2007, 02:54 PM

It looks like MobileOS has a problem with SPACES in paths and it is not a problem with SHORT or LONG paths. SPACE is a legal character for paths under Windows so why is this a problem? I can rearrange my work area but longterm MobileOS should allow SPACES in paths.

Posted by: bicarbon May 27 2007, 03:34 PM

Hi,

after rename 7-zip.dll to 7z.dll scripts ran great

bin.img completed aok

now a hang on localisation?

 log.html ( 401.32k ) : 6


Thanks,
bic


Posted by: euhenio May 27 2007, 05:06 PM

QUOTE
after rename 7-zip.dll to 7z.dll scripts ran great

This rough infringement



- fully delete old 7zip version from all tools-folders
- download 7zip 4.46 and install
- reboot compi
- update v007
- place 7z.dll and 7z.exe in WB dir
- compare my WB dir and you WB dir (date , size)
- "check project and set new paths now"
- compare my WB dir and you WB dir (date , size) again
- run "BinImg" again

Posted by: bicarbon May 27 2007, 05:16 PM


euhenio, thanks again

will get on that tomorrow

starting to look good!

Best

Posted by: jaclaz May 27 2007, 06:52 PM

QUOTE(greno)
It looks like MobileOS has a problem with SPACES in paths and it is not a problem with SHORT or LONG paths. SPACE is a legal character for paths under Windows so why is this a problem? I can rearrange my work area but longterm MobileOS should allow SPACES in paths.


Yes, but you see, when used in command line like in batches, the space assumes the functions of separator, thus, what is after the space is assumed by the parser as a parameter.
Therefore path with spaces need to be enclosed in double quotes but since very often in batch files paths are composed from a "fixed" part and a "variable" part, to produce a "path-with-spaces-compatible" script there is the need to quote separately both first and second parts (to correctly manage them internally) then unquote them to join them, then again quote them to give the final result.
The above usually makes things a lot more complex that really needed, and usually one adds support for paths with names in a "polishing-up" phase when all functionalities of script are well tested and debugged.

jaclaz

Posted by: greno May 27 2007, 10:43 PM

jaclaz,
Ok, got it. Part of the cleanup. It just made testing MobileOS a little harder is all.

euhenio,
Finally, some success. It created both the ram.img and bin.img. It went through the installation in QEMU and then finally shutdown. So now what? How do I create a DVD that will boot MobileOS?

Gerry

PS. In Linux I tried to loopmount bin.img as iso image but didn't work. Also, under Tools, what is Cleaning Project? Should I check this? It is unchecked right now.

Posted by: euhenio May 27 2007, 11:36 PM

QUOTE
what is Cleaning Project

this service for project . recommendable before and after creation
QUOTE
How do I create a DVD that will boot MobileOS?

first "Quick test"
if it's working then "IMG and ISO" and manually write img's to physical disks

Posted by: greno May 28 2007, 12:07 AM

QUOTE(euhenio @ May 27 2007, 11:36 PM) *
this service for project . recommendable before and after creation

first "Quick test"
if it's working then "IMG and ISO" and manually write img's to physical disks


Ok, ran Quick Test and it says "Ram.img not found" for any drive. confused1.gif

...
I then ran Cleaning Project script and tried to rerun 007 after I fill in Version paths. Then it says Check Ok, but then:
Access violation at address 00403BC5 in module WinBuilder.exe. Read of address 72502F33.

So, I retry rerun 007. It is now in Copy and Expand very long time. We will see...


Posted by: euhenio May 28 2007, 12:16 AM

QUOTE
It created both the ram.img and bin.img


So where ram.img ?

Posted by: greno May 28 2007, 12:21 AM

QUOTE(euhenio @ May 28 2007, 12:16 AM) *
So where ram.img ?


In Target/img

Posted by: greno May 28 2007, 12:25 AM

Now, Copy and Expand shows error box:
file(s) usbehci.sys not found. Copy manually these files:
usbehci.sys in [ram.img]\winnt\system32\drivers directory.

Also cfadisk.sys not found...

Then it says RAM.IMG completed.

Then runs Cleaning Project and says cannot find RAM.IMG.
(of course this clears all paths from Version script)

Then runs IMG and ISO script.

Then runs Quick Test and says cannot find RAM.IMG.

Then shows error:
Cannot find file "". The specified file does not exist.

It did not do this last time. confused1.gif

I think I will restart WinBuilder.exe ...

Ok, I restarted WinBuilder.exe and it did the exact same things as above.

confused1.gif confused1.gif


Posted by: euhenio May 28 2007, 01:03 AM

view log.html after run "Quick test"

and place ram.img in "not found" path

Posted by: greno May 28 2007, 01:09 AM

QUOTE(euhenio @ May 28 2007, 01:03 AM) *
view log.html after run "Quick test"

and place ram.img in "not found" path


IF - File does not exist: [%TargetRam%\img\ram.img] executing command: [Exit, ... Ram.img not found ...]

but ram.img is already there:

C:\Users\greno\Builds\MobileOS\Target\img>dir
Volume in drive C has no label.
Volume Serial Number is 30BE-27EB

Directory of C:\Users\greno\Builds\MobileOS\Target\img

05/27/2007 11:39 AM <DIR> .
05/27/2007 11:39 AM <DIR> ..
05/27/2007 05:42 PM 1,476,395,008 bin.img
05/27/2007 08:41 PM 67,108,864 ram.img
2 File(s) 1,543,503,872 bytes
2 Dir(s) 3,063,214,080 bytes free

I think %TargetRam% has been erased by Cleaning Project ???


Posted by: euhenio May 28 2007, 01:26 AM

Ok . In "Version"

"Target directory for Ram.img" insert "C:\Users\greno\Builds\MobileOS\Target"
after "check project and set new paths now"
after run "Quick test"

Posted by: greno May 28 2007, 01:44 AM

QUOTE(euhenio @ May 28 2007, 01:26 AM) *
Ok . In "Version"

"Target directory for Ram.img" insert "C:\Users\greno\Builds\MobileOS\Target"
after "check project and set new paths now"
after run "Quick test"


Ok, when I do "check project and set new paths now" I get Check OK with an Access Violation:

Access violation at address 00403BBE in module WinBuilder.exe. Read of address EEBE6626.

But then I run the Quick Test and it says:
Restart yuor (sp=your) compi and choice (sp=choose) "MobileOS" in boot menu. So I'm trying that now.





Posted by: greno May 28 2007, 01:55 AM

QUOTE(greno @ May 28 2007, 01:44 AM) *
But then I run the Quick Test and it says:
Restart yuor (sp=your) compi and choice (sp=choose) "MobileOS" in boot menu. So I'm trying that now.


That did not work. Got BSOD 0x7b.

Also gave me other problem :-) My beta copy of VMware WS 6.0 expired!! So now I need to go get QEMU and see if the vmdk will run under 0.8.2 in Linux.
So this will take some time I think.

Gerry

Posted by: euhenio May 28 2007, 02:12 AM

Thanks for corrections !

QUOTE
That did not work. Got BSOD 0x7b.

maybe were errors in logs\MobileOS ?

this testing for real compi

QUOTE
My beta copy of VMware WS 6.0 expired!! So now I need to go get QEMU and see if the vmdk will run under 0.8.2 in Linux.


MobileOS use only Qemu 0.9.0 (see first post)

Posted by: greno May 28 2007, 02:22 AM

QUOTE(euhenio @ May 28 2007, 02:12 AM) *
MobileOS use only Qemu 0.9.0 (see first post)


Unless MobileOS uses feature specific to 0.9.0 I think 0.8.2 should work. We'll see. Did not find package for 0.9.0 just 0.8.2.

Well, first attempt did not work. Got BSOD 0x7b for either boot menu choice in vmdk using QEMU. :-(

Ok, first choice in boot menu (regular install) just keeps rebooting into the LNGC boot selection page.
Second choice in boot menu (MobileOS) always gets BSOD 0x7b.


Posted by: greno May 28 2007, 04:47 AM

Ok, I finally got VMw WS6 running again by setting clock back a week. But I don't want to run too long like this because it messes up things.

So, now, in boot menu the REGULAR INSTALL boots ok with VMw WS 6 but continually reboots when started with QEMU 0.8.2. I even tried converting to raw image using qemu-img. It made the raw image but it behaves this same way. The MOBILEOS boot choice still produces BSOD 0x7b. And there are no log entries anywhere. So I do not know what is going on with this. Maybe it's emulated hardware. Maybe I waste a DVD-R and see what it does in real machine.



Posted by: greno May 28 2007, 04:59 AM

euhenio,
I ran IMG and ISO script and it created bin.img and MobileOS.iso. But iso is only 64MB. Is this right? Now, how do I create bootable DVD for MobileOS in RAM? Do I use bin.img?



Posted by: euhenio May 28 2007, 11:45 AM

qreno

maybe you haven't administrator right ?

QUOTE
But iso is only 64MB. Is this right?

yes !
you haven't usb-disk ?


I recommend
- create new folder C:\WB
- unpack WB071b2 thither
- download v007
- collect bin-files
- compare my WB-dir and your WB-dir
- run only "BinImg"
- before closing WB (in "Preparation") save log.html and rename him (binimg.log) , move in logs\MobileOS
- check all logs (logs\MobileOS) on errors




Why you use VMw . What sense in this ?

Posted by: greno May 28 2007, 12:41 PM

QUOTE(euhenio @ May 28 2007, 11:45 AM) *
qreno
you haven't usb-disk ?

No USB disk. Just want DVD. My goal is to have quick sysadmin MobileOS and put everything else I need on network and mount it.

QUOTE(euhenio @ May 28 2007, 11:45 AM) *
I recommend
- create new folder C:\WB
- unpack WB071b2 thither
- download v007
- collect bin-files
- compare my WB-dir and your WB-dir
- run only "BinImg"
- before closing WB (in "Preparation") save log.html and rename him (binimg.log) , move in logs\MobileOS
- check all logs (logs\MobileOS) on errors

I do not understand redo WB? If I cannot get vmdk to run under QEMU I will just zip up entire Users and put in a new WinXP VM in QEMU.
Still playing with all this right now.
QUOTE(euhenio @ May 28 2007, 11:45 AM) *
Why you use VMw . What sense in this ?

I have used VMw on Linux for many years before many open source emulators became good enough to use. Now I will look at QEMU. I have no real Windows machines. Only Linux. BUT, I sitll need to perform maintenance under Windows many times on real machines for things like updating firmware on various devices as manufacturers have quit producing DOS-based firmware updaters (due to demise of floppy drive) and only have Windows-based firmware updaters. So MobileOS would work for this especially for DVD drive since you can also remove the media and put in new firmware disk.

So please explain how MobileOS work:
What is ISO?
What is IMG?
How do they work together?

Can I build just one DVD that will boot XP in RAM?

Posted by: euhenio May 28 2007, 11:56 PM


MobileOS is based on USB-disk because boot-CD is outdated method.
Boot-CD(MobileOS) needed only for stupid-bioses which can't provide booting from USB

QUOTE
Can I build just one DVD that will boot XP in RAM?

It is possible , but you have no worker MobileOS-CD


Using dvd, you cannot save yours settings !

Posted by: bicarbon May 29 2007, 10:57 AM

moved project to C:\WB

source T:(xpsp2slipstreamed)

all WB files now match except:

ntldr (295,536 bytes) (2k3 sp1)
minlogon.exe (17,408 bytes) (xpembedded)
Winbuilder.ini absent
Projects\updates.ini absent

check project paths log - no errors

Bin.img log below

thanks

 Copy_and_Expand.html ( 50.54k ) : 10

Posted by: greno May 29 2007, 01:23 PM

QUOTE(euhenio @ May 28 2007, 11:56 PM) *
MobileOS is based on USB-disk because boot-CD is outdated method.
Boot-CD(MobileOS) needed only for stupid-bioses which can't provide booting from USB
It is possible , but you have no worker MobileOS-CD
Using dvd, you cannot save yours settings !


euhenio,
Yes, I understand that settings could not be saved. But I have many servers. Some do not even have USB. But they all have DVD drives installed.

So I need to be able to make sysadmin DVD like this:
CODE
Have MobileOS create binary image and then stop/wait.
Load binary image in emulator and tailor it with tools, service packs, whatever, then shutdown.
Then have MobileOS continue and take binary image and finish creating a DVD iso image that I can use to burn DVD.

Could you please add such capability? Some type of choice: CD/USB or DVD (cannot save settings)

Gerry


Posted by: euhenio May 30 2007, 12:09 AM

bicarbon

QUOTE
maybe you haven't administrator right ?


qreno

QUOTE
Have MobileOS create binary image and then stop/wait.
Load binary image in emulator and tailor it with tools, service packs, whatever, then shutdown.
Then have MobileOS continue and take binary image and finish creating a DVD iso image that I can use to burn DVD.


first you should receive worked MobileOS

For creation MobileOS I suggest to install winxp on real compi .

Your CD really sp2 ?

Posted by: greno May 30 2007, 05:15 AM

QUOTE(euhenio @ May 30 2007, 12:09 AM) *
first you should receive worked MobileOS
For creation MobileOS I suggest to install winxp on real compi .
Your CD really sp2 ?


I take it you mean that first I should get MobileOS working then proceed from there.

Remember, my CD is OEM XP CD w/no service pack. That is one of the reasons why I want MobileOS to stop/wait so that I can then load SP2. Although the OEM XP CD has all the files it will not slipstream because the OEM added some hotfixes and therefore it quits when you try to INTEGRATE. So only choice is to load SP2 later.

So I recreated my work environment in QEMU and looks good. So I'll continue to try to build MobileOS but I need to get USB key to test with. I should be able to load USB key from QEMU. But again, longterm I need to put all on DVD.

Posted by: greno May 30 2007, 03:15 PM

Ok, running 007 again....

Error box:

QUOTE
files(s) usbehci.sys not found.
Copy manually these files:

usbehci.sys





in

[ram.img]\winnt\system32\drivers

directory


And another error box:
QUOTE
cfadisk.sys not found


Both of these happened during Copy and Expand.

So then it finishes creating RAM.IMG, runs the Cleaning Project, the starts IMG and ISO script and then another error box:
QUOTE
Ram.img not found


Then it runs Quick Test and another error box:
QUOTE
Ram.img not found


Then it goes back to the V007 window and another error box:
QUOTE
Cannot open file "". The system cannot find the path specified


So under my Target/img directory there is a RAM.IMG file but no BIN.IMG file. It did not appear that it even ran a BIN.IMG creation script.
EDIT: Ok, I expanded BinImg block and nothing was checked except "key.script" so this is why BIN.IMG not created.

Stuck here now. frusty.gif

Posted by: euhenio May 30 2007, 11:49 PM

You hasten

QUOTE
For creation MobileOS I suggest to install winxp on real compi .

What your opinion ?

QUOTE
Remember, my CD is OEM XP CD w/no service pack. That is one of the reasons why I want MobileOS to stop/wait so that I can then load SP2. Although the OEM XP CD has all the files it will not slipstream because the OEM added some hotfixes and therefore it quits when you try to INTEGRATE. So only choice is to load SP2 later.

You tried nLite for integration ?

Posted by: greno May 31 2007, 12:32 AM

euhenio,
I made a change to the scripts and added the following to the qemu install command line:

QUOTE
-no-acpi

This makes the install process for BIN.IMG run much faster. At least within my QEMU dev environment. Since we are using a WinXP guest this is necessary (see QEMU forum). This should also generate a Standard PC instead of ACPI Uniprocessor PC.

UPDATE: this argument, -no-acpi, does not work reliably so I quit using it - it has hung the install several times.

A little OT, but is it possible to have a DVD-RW with a UDF packet-writing filesystem using DLA/InCD etc. that would be writeable and could save settings? thumbup.gif

Posted by: Nuno Brito May 31 2007, 09:51 AM

QUOTE(greno @ May 30 2007, 11:32 PM) *
....
A little OT, but is it possible to have a DVD-RW with a UDF packet-writing filesystem using DLA/InCD etc. that would be writeable and could save settings? thumbup.gif



A little more OT - how would it be possible to partition a CD-RW into 2 different partitions? blink.gif

- since mobileOS runs from RAM wouldn't it be simple to re-write the CD/DVD or just apply the changes on specific files and then update the filesystem structure?

This would be fun.. thumbsup.gif


Posted by: greno May 31 2007, 02:48 PM

QUOTE(Nuno Brito @ May 31 2007, 09:51 AM) *
A little more OT - how would it be possible to partition a CD-RW into 2 different partitions? blink.gif


As far as I know the UDF spec only permits one partition. Now in UDF 1.5 I think there were things like Spared type that would do wear-leveling but still only one partition.


Back OT,
I'm finding that running WinBuilder/MobileOS build in QEMU is much slower than running it in VMware 6. It is taking about 14 hours to complete! It took about 2.5 - 3 hours in VMware 6. I do not know why this should be because QEMU does not seem that much slower than VMware 6 when you use the QEMU acceleration. Maybe QEMU within QEMU has some problem. sad.gif

UPDATE: I'm beginning to suspect that the Windows installer itself has something to do with this. The installer window has the menu on the left and the propaganda messages running in the right pane. Well thousands more messages have run over the course of the install inside QEMU than inside VMware and these of course take CPU. You can even see the pane freeze up for a while and then display the next message. So I think QEMU is just slow enough to cause the message display timing loop to consume proportionately a great deal more CPU than normal.

Posted by: Nuno Brito May 31 2007, 09:55 PM

14 hours to complete just seems a bit too long, would you also have some pacience to try out emulating under VirtualBox? huh.gif

Hard to find an alternative to vmware on this case.. mellow.gif

edit: wouldn't it be possible to change the system timer to boost performance?


NTGear is a freeware alternative that is used to speed to the system timer - mostly used for speeding games, but seems a good tool for this task..

Homepage of NTgear:
http://www.wangrong1002.com/ (chinese)
(translated to english) http://64.233.179.104/translate_c?u=http%3A%2F%2Fwww.wangrong1002.com%2F&langpair=zh-CN%7Cen&hl=pt&ie=UTF8

A quick download link http://forum.cheatengine.org/viewtopic.php?p=422414&sid=22d4dc0e6e2654a5b5c68277e7d70826

There's also the full setup of the latest release on the site but I suspect it contains some nocive malware because avast has complained for two files which had a know malicious code signature.

In either case I've extracted manually these files from the installer and these files seem clean enough, to avoid this setup hassle I'll be uploading the latest build of ntgear to the download section.

Look here:
http://www.boot-land.net/index.php?ind=downloads&op=entry_view&iden=81

cheers.gif

Posted by: greno May 31 2007, 11:02 PM

QUOTE(Nuno Brito @ May 31 2007, 09:55 PM) *
14 hours to complete just seems a bit too long...

Oh, yeah... frusty.gif
QUOTE(Nuno Brito @ May 31 2007, 09:55 PM) *
...would you also have some pacience to try out emulating under VirtualBox? huh.gif


Not until they support tap interfaces on Linux. Maybe in the next release?


Posted by: euhenio May 31 2007, 11:46 PM

This configuration : v002/nLite.script take about 1 hours (KQemu installed)

Of course in real winxp

Posted by: greno Jun 1 2007, 12:50 AM

QUOTE(euhenio @ May 31 2007, 11:46 PM) *
This configuration : v002/nLite.script take about 1 hours (KQemu installed)

Of course in real winxp


Sounds about right for a small install.

I'm really disappointed in QEMU. They really need to profile the code and see where all the cycles are going. Something is very wrong in QEMU when using an XP Guest. thumbdown.gif It is much worse than VMware 6 and probably VirtualBox from what I read.

So my choices are: unsure.gif
Spend $200 for VMw6. Although I may be able to get GSX server for free - have to check (it is not based on 6.0)
Wait for next release of VirtualBox and hope that it supports tap interfaces (otherwise, no network).
Buy another hard drive or repartition hard drive thumbdown.gif and load WinXP on it and figure out a dual boot situation (and I thought I was all done with this).

UPDATE: Going to dual boot onto new hard drive. Take me a little while to load it. dots.gif

Posted by: greno Jun 1 2007, 05:21 AM

Ok, back up and running on a USB HDD.

So now I performed another run at 007.
It takes 1:01 to get through the install part. Then QEMU reboots.
Now it says "Applying computer settings..." during boot up and there it has been sitting for 40+ minutes. And my CPU fan is running on high now.
The hard drive light blinks very rarely. Maybe every 2-3 minutes. So whatever it is doing is not writing to the drive very often.
So I'll update this later if it ever finishes.

UPDATE: 9+ hours and it's still "Applying computer settings...". CPU at 100%. QEMU really has some kind of serious problem with XP Guest.
UPDATE: It finally pops up an error that says "Cannot find C:\WINDOWS\SYSTEM32\MSJAVX86.EXE". I OK'd the error and it's now at a blank turquoise screen.
UPDATE: Finally killed this and put it out of its misery. This was going to run for days!!!

frusty.gif

Posted by: euhenio Jun 1 2007, 01:14 PM

Sorry , current BinImg not working.

After some hours I upload new version BinImg.

Posted by: greno Jun 1 2007, 01:50 PM

QUOTE(euhenio @ Jun 1 2007, 01:14 PM) *
Sorry , current BinImg not working.

After some hours I upload new version BinImg.



Ok, I'll wait until you upload new version.

Also, can we use 'kqemu' acceleration for QEMU after the initial installation part? Maybe this would help for XP Guest?


Posted by: euhenio Jun 2 2007, 12:50 AM

v008

After download replace BinImg or move RamImg and Tools in v008 folder

Attention! Be cautious!

Posted by: euhenio Jun 2 2007, 01:51 AM

QUOTE
Also, can we use 'kqemu' acceleration for QEMU after the initial installation part? Maybe this would help for XP Guest?


In "Applying settings" this is possible , but in it there is no sense

Posted by: greno Jun 2 2007, 02:13 AM

QUOTE(euhenio @ Jun 2 2007, 12:50 AM) *
v008

After download replace BinImg or move RamImg and Tools in v008 folder

Attention! Be cautious!


Uh, what are you saying here?
Are you meaning delete current BinImg under v007 and rebuild BinImg under V008?
And you mean copy my RamImg and Tools from V007 to V008?


Posted by: greno Jun 2 2007, 02:35 AM

QUOTE(greno @ Jun 2 2007, 02:13 AM) *
And you mean copy my RamImg and Tools from V007 to V008?


Ok, I just downloaded V008 and I see that RamImg and Tools are missing. I didn't know I could just copy these from one to another. Might be better if you just included them though.

UPDATE:
In Version:
Error on RamImg target directory
Error on Project is not holistic!

BinImg scripts will not run.


Posted by: euhenio Jun 3 2007, 12:45 AM

Ok , I updated :

v008\ "Version"
v008\BinImg "Preparation"

Posted by: greno Jun 3 2007, 03:05 AM

QUOTE(euhenio @ Jun 3 2007, 12:45 AM) *
Ok , I updated :

v008\ "Version"
v008\BinImg "Preparation"



Ok, things were much better now!

I noticed that when I went to Version and clicked the button, it asked me to hit Refresh which I did, but then after that the button did nothing anymore.

So then I made sure every box was checked under V008 and then I clicked on V008 and pressed Play icon on top and the scripts started to run.

When the BinImg script starts, it says it created a 1.5G bin.img file and asks to check if it is fragmented. How do we do that? I just clicked OK and let it run.

So then the QEMU starts up and the XP install proceeds. It only took about 45 minutes - very good (this was with user mode kqemu). Then some other scripts start compressing/uncompressing images and making the image 1GB. And eventually it says BIN.IMG created! Yea!!! But the image is about 1.37GB not 1GB.

But then all processing stops and it goes back to the main MobileOS window. The BinImg box is now unchecked but all the other boxes are still checked.

So it didn't run automatically all the way to the RamImg and Tools, in fact you cannot even run these manually, but maybe this is because these were copied from V007 ???

Great progress though... cheers.gif

Posted by: euhenio Jun 3 2007, 06:29 PM

QUOTE
maybe this is because these were copied from V007


Yes , current "Version" not support with old RamImg

In end of day I upload new RamImg

But I recommended study an errors in logs\MobileOS folder

Posted by: euhenio Jun 3 2007, 11:30 PM

v008 is updated

Before download v008 remove v008 folder


For easy download

WinBuilder.ini

CODE
[Main]
WebServer=mobileos.boot-land.net
Last_Download_Level=2

Posted by: greno Jun 5 2007, 01:02 PM

QUOTE(euhenio @ Jun 3 2007, 11:30 PM) *
v008 is updated

Before download v008 remove v008 folder
For easy download

WinBuilder.ini

CODE
[Main]
WebServer=mobileos.boot-land.net
Last_Download_Level=2


Ok, d/l new V008.

Click Version
Set Paths
Source Disk: I:
Target Directory: C:\Users\greno\Builds\....
Target Directory for RamImg: C:\Users\greno\Builds\...

Click check path button

Receive these errors:

cmd.exe window: SUCCESS: The process "WinBuilder.exe" with PID 1064 has been terminated.

Windows Explorer window: The path "H:\Project MobileOS" does not exist or is not a directory.

H:\Project MobileOS\Winbuilder.exe window: Windows cannot find "H:\Project MobileOS\Winbuilder.exe". Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.

confused1.gif

Posted by: euhenio Jun 5 2007, 05:01 PM

greno
Many thanks for testing !

greno
bicarbon
update

Version
BinImg\Preparation
RamImg\Preparation

Try Again !

Posted by: greno Jun 5 2007, 05:20 PM

new V008 now just says: This project require 7z version 4.46 beta.

But my 7z is already at 4.47 beta.

Test should allow newer as well. Can you change?

Also, what does it mean to "use old bin.img"? Does this mean old but empty bin.img or fully populated bin.img?


Posted by: greno Jun 5 2007, 05:39 PM

QUOTE(greno @ Jun 5 2007, 05:20 PM) *
new V008 now just says: This project require 7z version 4.46 beta.

But my 7z is already at 4.47 beta.

Test should allow newer as well. Can you change?

Also, what does it mean to "use old bin.img"? Does this mean old but empty bin.img or fully populated bin.img?



Ok, nevermind about 7z version error. I had to copy 7z 4.47beta to my Downloads directory and it then worked.


But in RamImg Copy and Expand I get this 7z error in:
7z_ramimg_Copy_and_Expand_gen.log:

can not open output file W:\WINNT\system32\drivers\vga.sys
Skipping WINNT\system32\drivers\vga.sys
can not open output file W:\WINNT\system32\drivers\videoprt.sys
Skipping WINNT\system32\drivers\videoprt.sys
can not open output file W:\WINNT\system32\drivers\volsnap.sys
Skipping WINNT\system32\drivers\volsnap.sys
can not open output file W:\WINNT\system32\drivers\wanarp.sys
Skipping WINNT\system32\drivers\wanarp.sys
can not open output file W:\WINNT\system32\watchdog.sys
Skipping WINNT\system32\watchdog.sys
can not open output file W:\WINNT\system32\win32k.sys
Skipping WINNT\system32\win32k.sys
Skipping WINNT\LastGood.Tmp\System32\win32k.sys
can not open output file W:\WINNT\system32\drivers\wmilib.sys
Skipping WINNT\system32\drivers\wmilib.sys

I don't have a drive W: that I know of. Is this something that MobileOS creates?

Also in RamImg Prep:
Creation ram.img:
Error: cannot open image file: C:\Users\greno\Builds\MobileOS\Target\img\ram.img

Posted by: euhenio Jun 5 2007, 08:51 PM

qreno

QUOTE
But in RamImg Copy and Expand I get this 7z error

In "RamImg\Preparation" will increase "image size"

I wish to look your "logs\MobileOS\Applying_settings.html"
also unpack Settings folder from MobileOS.7z and inform me his size


Posted by: greno Jun 5 2007, 09:01 PM

QUOTE(euhenio @ Jun 5 2007, 08:51 PM) *
qreno

In "RamImg\Preparation" will increase "image size"

I wish to look your "logs\MobileOS\Applying_settings.html"
also unpack Settings folder from MobileOS.7z and inform me his size



 Applying_settings.html ( 24.38k ) : 9



Settings 0B 0B 2007-06-02 22:47 D

Settings (unpacked) 1.83MB

Posted by: euhenio Jun 5 2007, 10:11 PM

qreno

QUOTE
Applying_settings.html

QUOTE
Settings (unpacked) 1.83MB

good

For "Target directory for Ram.img" is better to use high-speed (ram) disk

QUOTE
In "RamImg\Preparation" will increase "image size"

your result ?

Posted by: greno Jun 5 2007, 10:22 PM

QUOTE(euhenio @ Jun 5 2007, 10:11 PM) *
qreno
good

For "Target directory for Ram.img" is better to use high-speed (ram) disk
your result ?



No result.
RamImg scripts just give:
Error: cannot open image file: C:\Users\greno\Builds\MobileOS\Target\img\ram.img

But it is there, 64MB.

Posted by: euhenio Jun 5 2007, 11:52 PM

frusty.gif
It is stupid error ... I overdo .
Re-download "RamImg\Preparation" and try again ( i checked now RamImg )

QUOTE
But it is there, 64MB.

try 70Mb

Posted by: greno Jun 6 2007, 01:13 AM

Ok, I re d/l, select 70MB, run RamImg.

RAM.IMG created. but got error about usbehci.sys and cfadisk.sys.

Rebooted. Selected MobileOS from boot menu.

BSOD 0x7b confused1.gif

Posted by: euhenio Jun 6 2007, 08:11 AM

QUOTE
BSOD 0x7b


In your a case it can be caused by two reasons:

1.
QUOTE
but got error about usbehci.sys

this file included in sp1.cab or sp2.cab. Sp2.cab or sp1.cab should be in the same folder, as MobileOS.7z.

2. Probably ramdisk.sys(2003sp1) require only XPsp1 or sp2


Possibly for successful integration SP2 to your OEM CD need to be removed svcpack.inf


Posted by: greno Jun 6 2007, 03:28 PM

QUOTE(euhenio @ Jun 6 2007, 08:11 AM) *
In your a case it can be caused by two reasons:

1.
this file included in sp1.cab or sp2.cab. Sp2.cab or sp1.cab should be in the same folder, as MobileOS.7z.

2. Probably ramdisk.sys(2003sp1) require only XPsp1 or sp2
Possibly for successful integration SP2 to your OEM CD need to be removed svcpack.inf



1. Ok, when you d/l SP2 from the MS website it is this file:
WindowsXP-KB835935-SP2-ENU.exe

How do I get sp2.cab from this file?

2. Where do I get cfadisk.sys file?

Ok, on the OEM CD I found svcpack.inf and it has about a dozen hotfixes in it. So if I remove this file you think my XP will then integrate with SP2?


Posted by: euhenio Jun 6 2007, 05:07 PM

QUOTE
So if I remove this file you think my XP will then integrate with SP2?


I assume, possibly someone more skilled on this forum will help you

Maybe it :

CODE
WindowsXP-KB835935-SP2-ENU.exe /?



QUOTE
Where do I get cfadisk.sys file?

Now I do not know the direct link . This is optional component only for usb flash



Additional question:

During work BinImg you saw "checking disk Y..."

Posted by: jaclaz Jun 6 2007, 05:45 PM

QUOTE(greno @ Jun 6 2007, 05:28 PM) *
1. Ok, when you d/l SP2 from the MS website it is this file:
WindowsXP-KB835935-SP2-ENU.exe

How do I get sp2.cab from this file?

2. Where do I get cfadisk.sys file?

Ok, on the OEM CD I found svcpack.inf and it has about a dozen hotfixes in it. So if I remove this file you think my XP will then integrate with SP2?


greno,
1.
OEM CD's are notoriously tricky, you better use an application like Autostreamer or nlite to do the integration, moreover, do check this thread and links I give therein:
http://www.911cd.net/forums//index.php?showtopic=16381

2. Comeon, go to www.google.com, input in the search box "cfadisk.sys" and click with the mouse on the search button wink.gif
one of the resulting pages will be this one:
http://www.911cd.net/forums//index.php?showtopic=14292

jaclaz


Posted by: greno Jun 7 2007, 02:48 PM

QUOTE(jaclaz @ Jun 6 2007, 05:45 PM) *
1.
OEM CD's are notoriously tricky ...


Yeah, after 7 hours of experiments I finally got this Dell OEM XP CD to integrate. I would have to have one of the hardest OEM XP CD's to integrate. What a pain.
I see usbehci.sy_ in i386 so that should take care of that problem.


QUOTE(jaclaz @ Jun 6 2007, 05:45 PM) *
... one of the resulting pages will be this one:
http://www.911cd.net/forums//index.php?showtopic=14292


I read this page and I'm actually more confused now wink.gif

I'm going to spend some time today and figure out this cfadisk.sys issue ...

Posted by: jaclaz Jun 7 2007, 03:11 PM

QUOTE(greno)
I read this page and I'm actually more confused now


Let see if I can explain a bit the matter.

USB Mass Storage devices, or to be more exact controllers inside USB Mass Storage devices, can be set as to "present" themselves as either "Removable" or "Fixed" to the 2K/XP OS.

The default for USB Hard Disks is generally "Fixed".
The default for USB Flash drives is generally "Removable".

If a drive is seen as "Removable" ONLY one partition (First Active) will be accessible (mountable) in 2K/XP, if it is seen as "Fixed" ALL partitions on the device will be accessible/mountable.

Flipping this bit inside the controller is possible only with some Manufacturer "specific" program, some have been found, MOST were not.

The cfadisk.sys aka "Hitachi Microdrive Filter", as well as the CodeProject "dummydisk.sys"
see here:
http://www.911cd.net/forums//index.php?showtopic=14181&st=1954
are Filter Drivers that "filter" information sent by the USB device controller to the OS, tricking it into believe that the device is either "Fixed" or "Removable", in other words it is a software replacement for the hardware bit flipping seen before.

Hope that the above helps.

jacla

Posted by: greno Jun 7 2007, 03:12 PM

QUOTE(greno @ Jun 7 2007, 02:48 PM) *
I'm going to spend some time today and figure out this cfadisk.sys issue ...


Ok, I found the Hitachi Microdrive filter. But I going to skip this for the moment. MobileOS says it's optional.


Posted by: greno Jun 7 2007, 04:06 PM

So now back to V008:

When I try to create new BIN.IMG during Setup I get the error message:

QUOTE
The file usbehci.sys is corrupted.
Press any key to continue.

After keypress:
Setup failed. Press any key to restart your computer.


Why would it say this? usbehci.sy_ came right from XP2. I checked and it's the same size and timestamp on the CD as in XP2.

Ok, I see all kinds of posts with this exact same problem after slipstreaming and none of them appear to know any solution to the problem. The filename, filename case, filesize, timestamp all appears to have been ruled out as a source of the problem. My guess is that there is some entry in an INF file somewhere that is conflicting with the new usbehci.sy_ from SP2. But many people have explored this and come up empty so not sure how to track this problem down.


Posted by: euhenio Jun 7 2007, 05:21 PM

Try to delete all lines "usbehci.sys" from txtsetup.sif

Posted by: greno Jun 7 2007, 06:27 PM

QUOTE(euhenio @ Jun 7 2007, 05:21 PM) *
Try to delete all lines "usbehci.sys" from txtsetup.sif


Do you mean every 'usbehci...' entry including the [files usbehci] and all files underneath?
Or just specifically usbehci.sys where found?


Posted by: greno Jun 8 2007, 12:14 AM

QUOTE(greno @ Jun 7 2007, 06:27 PM) *
Do you mean every 'usbehci...' entry including the [files usbehci] and all files underneath?
Or just specifically usbehci.sys where found?


Ok I deleted everything usbehci related in txtsetup.sif and retried V008.

Now the Setup gets a little further but displays this error:
QUOTE
The file usbohci.sys is corrupted.
Press any key to continue.


This will take eons if it is going to do this for every file.

There must be something else to try besides just deleting these one by one from txtsetup.sif and reburning new CDs.


Posted by: euhenio Jun 8 2007, 01:07 AM

QUOTE
reburning new CDs.

maybe "virtual"

------------------------------------

Version 009 beta

-- FBWF
-- VBEMP http://www.geocities.com/bearwindows/vbemp.htm
-- DbgPrint logger http://alter.org.ua/en/soft/win/dbgdump/ (create log for http://www.boot-land.net/forums/bearwindows-m8262.html)

Posted by: greno Jun 8 2007, 02:04 PM

QUOTE(euhenio @ Jun 8 2007, 01:07 AM) *
maybe "virtual"

------------------------------------

Version 009 beta

-- FBWF
-- VBEMP http://www.geocities.com/bearwindows/vbemp.htm
-- DbgPrint logger http://alter.org.ua/en/soft/win/dbgdump/ (create log for http://www.boot-land.net/forums/bearwindows-m8262.html)


Using V008:
When I try to use 'Virtual' CD (Mapped Network Drive) it says Installation Error.

Using V009b:
Prompting for fbwf.sys location.
I cannot find this file.


Posted by: euhenio Jun 8 2007, 05:13 PM

QUOTE
Mapped Network Drive

Local Drive
QUOTE
I cannot find this file.

This file is included in Microsoft® Windows® XP Embedded

You tried v002 to your NEW OEM CD SP2 ?

Posted by: greno Jun 9 2007, 12:29 AM

QUOTE(euhenio @ Jun 8 2007, 05:13 PM) *
Local Drive

This file is included in Microsoft® Windows® XP Embedded

You tried v002 to your NEW OEM CD SP2 ?


Yes, I tried under V002. It just says Error Installation. There are no settings. How does it know where to find my Slipstreamed CD?


Posted by: greno Jun 9 2007, 03:51 PM

Problem: After loading and running V009b now all versions give me Error Installation on BinImg scripts.

UPDATE: After I rebooted my computer and selected MobileOS yesterday. Now when I boot normally and log in with my regular user id it shows that I am SYSTEM. And the "My Documents" directory is showing as "SYSTEM's Documents" in Explorer Folders. How is this possible? How can I fix this? I think this is why I am getting Error Installation on every script because they do not have access to any files!

UPDATE: Upon further investigation, I think this has happened mid-session while running MobileOS scripts. Because I have one old cywin window open which says that I am 'greno' and now I just opened another which says I am 'SYSTEM'. Is MobileOS doing anything with SYSTEM id?



Also, I think that deleting all usbehci and usbohci entries from txtsetup.sif will cause problems because my hard drive is USB and my cdrom is USB. Therefore the text install portion of setup would not be able to see these devices.

What comparison could the Setup be doing that it thinks that usbehci.sys, usbohci.sys are corrupt? Does it compare them to contents of DRIVER.CAB? I looked in there and I do not see usbehci.sys but I do find usbohci.sys.

Posted by: euhenio Jun 9 2007, 04:55 PM

QUOTE
all versions give me Error Installation on BinImg

Describe more in detail

QUOTE
because my hard drive is USB and my cdrom is USB

QEMU in MobileOS don't use USB

QUOTE
What comparison could the Setup be doing that it thinks that usbehci.sys, usbohci.sys are corrupt?

SFC

QUOTE
Does it compare them to contents of DRIVER.CAB? I looked in there and I do not see usbehci.sys but I do find usbohci.sys.

SP2.CAB



Your new OEM CD work without MobileOS ?


Posted by: greno Jun 9 2007, 06:31 PM

QUOTE(euhenio @ Jun 9 2007, 04:55 PM) *
Describe more in detail
QEMU in MobileOS don't use USB
SFC
SP2.CAB
Your new OEM CD work without MobileOS ?


See my update to post #224.

Posted by: euhenio Jun 10 2007, 01:28 AM

QUOTE
How can I fix this?


After reboot all it should be restored ( for me it's true )

Posted by: greno Jun 10 2007, 02:13 AM

QUOTE(euhenio @ Jun 10 2007, 01:28 AM) *
After reboot all it should be restored ( for me it's true )


I rebooted and things look normal. Are they normal? That's too weird. Please don't have your scripts do this. It messes up a lot of things. Everything went crazy. Icons disappeared. Scripts wouldn't run right. Things were grayed out. Was this V008 or V009 that was doing this? Now I'm afraid to run either one.


Posted by: euhenio Jun 10 2007, 11:08 PM

QUOTE
Please don't have your scripts do this.

This necessity

Your suggestions ?

Posted by: thunn Jun 13 2007, 09:30 PM

Do any of the 3 version of your project work as a 'light touch' operation yet??

I'm waiting for more scripting to be completed so I can just press one or two buttons and sit back.
I already had the plessure of finishing a manual 'XP InRAM' build using nlite and lots of coffee.

Posted by: euhenio Jun 14 2007, 12:27 AM

thunn

Now I little slowed down work

I would like to read your impressions of version 008 or 009

Also

QUOTE
Your suggestions ?


Posted by: euhenio Jun 24 2007, 02:08 AM

beta 2

Add Display Control for Windows http://alter.org.ua/en/soft/win/vidcontrol/

 

Posted by: euhenio Jul 6 2007, 01:51 AM

beta 3

Posted by: TheHive Jul 6 2007, 06:52 AM

Can someone define what is "MobileOS" and or its goals. I went to the first post to get a sense or picture of what its suppose to do but I dont have a good mental picture of what it is. Thanks!

Posted by: euhenio Jul 6 2007, 11:23 PM

MobileOS - it's FREEDOM!

Posted by: hooovahh Jul 19 2007, 08:35 PM

What I think euhenio means, is that Mobile OS is not a Live OS, or a Bart PE, or WinPE like OS. It is not a PE OS at all. Instead of being Preinstall Environment, it is the Installed Environment. You install XP in a virtual machine, make use the hard disk image, and then load that into ram in a real machine and boot off of it.

It's essentially windows XP installed into Ram each time you boot. So any software you can install in the real windows, you can install in the Mobil OS. I haven't gotten it fully working yet, but I monitor the project in hopes that it will mature more.

Posted by: TheHive Jul 20 2007, 06:19 AM

QUOTE(hooovahh @ Jul 19 2007, 03:35 PM) *
What I think euhenio means, is that Mobile OS is not a Live OS, or a Bart PE, or WinPE like OS. It is not a PE OS at all. Instead of being Preinstall Environment, it is the Installed Environment. You install XP in a virtual machine, make use the hard disk image, and then load that into ram in a real machine and boot off of it.

It's essentially windows XP installed into Ram each time you boot. So any software you can install in the real windows, you can install in the Mobil OS. I haven't gotten it fully working yet, but I monitor the project in hopes that it will mature more.

Thanks hooovahh, that make more sense to what its goals. thumbsup.gif
Sounds like a good objective.

Posted by: euhenio Jul 21 2007, 12:43 AM

QUOTE
Sounds like a good objective.


Sorry , I don't know how correctly translate it :
QUOTE
То есть эта та операционная система , которая всегда может быть с нами и обеспечивать привычную обстановку за любым compi .

(from http://euhenio.mam.by/)

Posted by: Nuno Brito Jul 21 2007, 12:54 AM

roll1.gif

Posted by: TheHive Jul 21 2007, 04:59 AM

QUOTE(euhenio @ Jul 20 2007, 07:43 PM) *
Sorry , I don't know how correctly translate it :

(from http://euhenio.mam.by/)

The projected goal of this Project appear to be good in that it will work similar to an OS install, but will work using RAM.

Posted by: euhenio Jul 25 2007, 10:11 PM

New script !

flashnul (IMG Writer)

Posted by: Nuno Brito Jul 25 2007, 10:30 PM

I still haven't managed to run this project even once.. sad.gif

Would there be time for some step-by-step post? (the first post is not anywhere clear to start..)

Also - we're starting to automate unattended windows installs, add the webserver unattended.boot-land.net to your download center to see how it works.

There is a new qemu.script file inside that can likely speed up your install by disabling ACPI support.

You can also apply the same tweak inside the windows source to make things run faster under the emulator.

Look here: http://kvm.qumranet.com/kvmwiki/Windows_ACPI_Workaround

Also using kemu can most likely increase the install speed.

With qemu you can also directly use a folder as an virtual drive, read the documentation and you can likely tweak qemu to install windows directly to a folder and then apply all needed changes.


Would really like to try out mobileos and help things going forward - sorry for the rant.. cheers.gif

Posted by: euhenio Jul 26 2007, 05:36 PM

only download MobileOS and press "Play" button

I shall glad see your result ! (even failed)



beta 6 smile.gif

Posted by: Nuno Brito Jul 26 2007, 05:44 PM

Thank you will try, once I get this step done I hope to also start posting more info to help others getting started too, glad to hear the new beta.. thumbup.gif

Posted by: amalux Jul 27 2007, 06:16 AM

QUOTE(Nuno Brito @ Jul 26 2007, 10:44 AM) *
Thank you will try, once I get this step done I hope to also start posting more info to help others getting started too, glad to hear the new beta.. thumbup.gif

Hi Nuno,

Just a friendly warning about this project - I tried to run it earlier today and it's taken me hours to clean up the mess! Obviously, this is only anecdotal and it's possible that I didn't follow the instructions exactly but the amount of damage done to my computer was extensive and troubling and I feel an obligation to warn others. So this is exactly what I did and what happened as a result; First I downloaded a fresh copy of WinBuilder.exe 072, set it up as usual in its own folder at the root of my C: drive. Selected the 'mobileos.boot-land.net' server and downloaded the default 'MobileOS' project (complete). Selected my source and target directories as usual and hit 'Play'; I received several messages like these:

so I started over from scratch and re-checked everything but got the same errors the next time and decided to just get through to the end and sort it out in the log (never got there); a few more windows popped up directing me to set the directories (again) in a different location:

Strangely, I can't reproduce the window that it took me to (upon clicking OK to the second warning) with Source and Target options! It was in the pane to the right of the project directory with 'Version.script' selected. If I go to that window now (without running the scripts) all I see is a blank, white pane! Very strange. Anyway, I set the Source and Target directories as before and continued the project. This is where it gets bizarre and you'll just have to take my word that I'm not exaggerating... Within moments, my desktop had been completely changed, wallpaper went black, windows became skinned and changed color, different Start and Taskbar configuration; all the while many windows and programs starting (some I didn't even recognize!) Things like 'Windows Tour' and Help Tutorials and what appeared to be live chat sessions in fast playback! All happening so fast that I couldn't focus on any one window before another new one covered it etc. The whole thing only lasted maybe 10 seconds but left my computer devastated! All the folders and icons on my desktop were gone, many windows remained open but the computer was frozen and I could only see the top ones; many new and unfamiliar icons appeared in my system tray etc. etc. When I tried to reboot, the system hung at the boot screen and I was forced to try a System Restore from DOS - It failed. If I didn't have my hard drive backed up with Drive Image, I'd be reinstalling Windows right now. Not only was everything on my desktop lost but it affected files and folders on other partitions! I'm still sorting out all the damage but wanted to get this warning out as soon as possible. Obviously I don't think any of this was malicious or intentional, it was obviously just some scripts run amok and I'm sure others will have different experiences than mine. All I can say is BACKUP your HDD first! Good luck. wink.gif

Posted by: jaclaz Jul 27 2007, 10:00 AM

@amalux

Hmmm, dubbio.gif,
without entering in the details of this project, which I don't know, I can provide you and all other members with some general "rule of thumbs":
1. WHENEVER a script, program or whatever, pops up a message containing the words:
ERROR, WARNING, or similar ones, even if you do not understand the rest of the message, STOP the program.
2. Then try to understand what the message is trying to say, if you can't, ask for help of more experienced people, DO NOT, for any reason, ignore a WARNING, DO NOT, for any reason, continue executing the script/program UNLESS you really know what you are doing and are prepared to repair the problems caused by IGNORING a WARNING.
3. The whole idea of testing something is that, well, testing. Tests should NEVER, for any reason, be conducted on a "production" PC, nor on your only one.
4. ALWAYS backup or image the system (as you did smile.gif) to be able to get it back the way it was before the test.
5. ALWAYS, ALWAYS, and I mean ALWAYS be aware that Murphy's Law, in it's entirety is beside you, waiting patiently to prove itself right:

QUOTE
Murphy's Law was named after Captain Edward A. Murphy and is formed by eight laws.
  • If anything can go wrong, it will.
  • If there is a possibility of several things going wrong, the one that will cause the most damage will be the one to go wrong.
  • If anything just cannot go wrong, it will anyway.
  • If you perceive that there are four possible ways in which something can go wrong, and circumvent these, then a fifth way, unprepared for, will promptly develop.
  • Left to themselves, things tend to go from bad to worse.
  • If everything seems to be going well, you have obviously overlooked something.
  • Nature always sides with the hidden flaw
  • Whatever has happened wrong, is bound to happen again .... maybe even worse.

6. Don't try to be smart, Murphy's Law is ALWAYS right! mad.gif

Specifically, "failed the integrity check" means that a file is corrupted, you don't expect to have "right " results from a "wrong" file, don't you? unsure.gif

Happy however you managed to recover. smile.gif

jaclaz

Posted by: Nuno Brito Jul 27 2007, 10:45 AM

Hi Amalux!

Thanks for the warning, sorry to hear about all the hassle caused - but I will keep it mind.. cheers.gif

Since you have been downloading sucessfully script from other web servers I think that euhenio has uploaded directly the newer versions of his scripts without updating "updates.ini" which contains individual information about each available file.

This updates.ini contains the MD5 signature of each file listed for download - this is a good safe mechanism to avoid possible file corruption while downloading.

Files are temporarily downloaded with extension (.web) and only if they pass this MD5 check they are allowed to overwrite older files or correctly take their place with the proper extension.


Euhenio needs to reupload his web server from scratch so that people can get a working project - at the moment we should only be able to manually download these files one by one using the direct link to them on the explorer window.


----------------------------------------------

This is why documentation and examples are so important to explain how things are meant to work.. rolleyes.gif

Posted by: amalux Jul 27 2007, 04:21 PM

@jaclaz!

You are absolutely right! I know Murphy well and have shown his theorems to be accurate on numerous occasions wink.gif . I had become complacent (and a bit cocky, I think) having had such good success on other projects recently (LiveXP; nativeEx etc.) and expected the errors to just show up as items in the log to track down and work through roll1.gif . I learned an important lesson (for the 10,000th time) and will be very careful in future 'testing'. Honestly, the Active drive being scrambled wouldn't have even evoked a response (that's what PowerQuest and Ghost are for); what did 'surprise' and concern me was the thousands of files deleted or scrambled on other backup drives. Fortunately, I do back everything up (hdd images, redundant physical drives and mobile media) so, no worries, I'm back to normal now but I thought it worth a warning to those who might not realize the potentially destructive nature of these corrupted scripts.

@Nuno!

QUOTE
This updates.ini contains the MD5 signature of each file listed for download - this is a good safe mechanism to avoid possible file corruption while downloading.

Files are temporarily downloaded with extension (.web) and only if they pass this MD5 check they are allowed to overwrite older files or correctly take their place with the proper extension.


That's interesting, I will be paying very close attention to these warnings in the future thumbsup.gif

Thanks buddy cheers.gif

Posted by: euhenio Jul 27 2007, 06:07 PM

amalux

Thank you , Try now (in WinXP)



Current Version of WinBuilder(072) not compatible with MobileOS because "Wait" command is changed ...

Posted by: amalux Jul 27 2007, 07:08 PM

QUOTE(euhenio @ Jul 27 2007, 11:07 AM) *
amalux

Thank you , Try now (in WinXP)
Current Version of WinBuilder(072) not compatible with MobileOS because "Wait" command is changed ...

Just setting up a seperate 'Test HDD' for these projects (better late than never dry.gif )

When you say wb072 isn't compatable, please confirm the version which is currently recommended for MobileOS. Also a link to the latest instructions if you have it, sorry if this is posted already (I'm lazy). Will test this afternoon and let you know (I'll post the log if I get that far)

Thanks euhenio thumbsup.gif

Posted by: Nuno Brito Jul 27 2007, 07:29 PM

Remove a 0 to the wait value.

If it was 40 use 4 - the multiplier on the older versions was wrong, instead of multiplying the value for 1000 miliseconds it would multiply by 100.. frusty.gif

This can be quickly fixed.. smile.gif

Posted by: jaclaz Jul 27 2007, 09:01 PM

QUOTE(amalux)
I'm back to normal now but I thought it worth a warning to those who might not realize the potentially destructive nature of these corrupted scripts.


Yep, you did the right thing thumbsup.gif , better safe than sorry! rolleyes.gif

cheers.gif

jaclaz

Posted by: euhenio Jul 27 2007, 09:16 PM

amalux

see first post

I need in bugreport for this project for correcting his


Nuno Brito

QUOTE
If it was 40 use 4 - the multiplier on the older versions was wrong


I found this bug usable , because step 1s is very big

Please return this command (better 10ms step)

Posted by: Nuno Brito Jul 27 2007, 09:59 PM

Beware that the wait command is very superficial - this might be dangerous when applied to different hardware which migth work either faster or slower and then cause the same results posted by amalux..

Better use another method not dependant on any timer at all.. wink.gif

Will study the project and try to help solving this matter.

Would you please upload a package to download as direct link for the project files? huh.gif

Thank you! smile.gif

Posted by: amalux Jul 27 2007, 11:00 PM

QUOTE(Nuno Brito @ Jul 27 2007, 02:59 PM) *
Would you please upload a package to download as direct link for the project files? huh.gif

Thank you! smile.gif

@euhenio!

This would be fantastic, I am having trouble tracking down some of these files in the versions you specify i.e. WinServ03 SP1, I have SP2 and some of my file sizes don't match yours etc.

Upload, upload thumbup.gif

Posted by: euhenio Jul 28 2007, 04:53 AM

Nuno Brito

QUOTE
Would you please upload a package to download as direct link for the project files?


Download Center - method seems have not now problems


amalux

QUOTE
I am having trouble tracking down some of these files in the versions you specify


See other pages this topic

Posted by: Nuno Brito Jul 28 2007, 05:07 AM

Yes, I've downloaded all project files.

Don't mean to be picky, but wouldn't it be easier to include the external tools inside your project? huh.gif

(except for the ones that require licensing - MS files in most cases)


Will start googling for the needed files.. rolleyes.gif

Posted by: Nuno Brito Jul 28 2007, 06:33 AM

Euhenio - please post a tutorial about the correct procedures to use this project.

It took a long time to find all needed files, extract and place them on the correct folder.

Wasn't able to find FBWF and also created the nlited image - but the version script still complains saying that I need to use wb071 beta 2? huh.gif

It wasn't easy to have a notion of what needed to be done in the first place.

A simple text file would make our life so much easier for testing and helping this project go forward - and I consider myself to know my way around these sort of things, but I can't really guess every step and risk the health of my work machine.


I'm posting here my set of needed tools (except MS licensed files)

 Tools.7z ( 1.17mb ) : 12


-------------

Would be a good option to avoid using winlogon.exe and FBWF since these are not easy to find - why not using diskless angel driver to replace these MS files and make things simpler?

Do we really need to use windows 2003 files to boot into RAM - wouldn't it be possible to just run from the drive itself and add Win2003 RAM boot as default only if add the needed files? huh.gif

I guess that in most cases we'd already be happy to have a mobile XP booting from USB using only a XP install disk and nothing more.

-------------

Please post more documentation, I know you're not very confortable with english - but posting some screenshots on your website and preferably some youtube clips would make so much easier to understand and follow your examples to replicate the same results.

Or at least post small text descriptions inside these scripts so that we can know why they even exist - each script comes with absolutely no descriptions inside that let us know how to be used and this really doesn't help a project which already has a few complicated steps included.

This way it's just unusable for further trying out and help with beta testing, sorry. thumbdown.gif

Posted by: amalux Jul 28 2007, 09:14 AM

@euhenio!

This is as close as I can come to the file list you specified:


This version of winlogon should work in place of minlogon (not available in my installation of XP-Embeded SP2) fbwflib could work for fbwfdll ??? it seems to work for that purpose in other applications. Please let me know if these files are acceptable and I will attempt further experimentation. I agree with Nuno that more instruction and documentation would really help get this project off the ground.

@Nuno!

Please let me know if I should upload this file set; everything was obtained legally by me but not too clear on what is allowed here unsure.gif

Posted by: Nuno Brito Jul 28 2007, 11:11 AM

In most cases it's just fine to upload freeware tools or apps that have the expressed consent to be distributed - MS is usually quite restrictive about this matter.

However I would really like to suceed on getting this project to work and see it in action and lately MS itself has been much more permissive than some years ago.

Please post it temporarily until we can find a solution that doesn't require these MS files and can be used as default - once we've got a good alternative there will no longer be any need for MS not included by default on XP Install Disk.

cheers.gif

Posted by: amalux Jul 28 2007, 02:54 PM

QUOTE(Nuno Brito @ Jul 28 2007, 04:11 AM) *
In most cases it's just fine to upload freeware tools or apps that have the expressed consent to be distributed - MS is usually quite restrictive about this matter.

However I would really like to suceed on getting this project to work and see it in action and lately MS itself has been much more permissive than some years ago.

Please post it temporarily until we can find a solution that doesn't require these MS files and can be used as default - once we've got a good alternative there will no longer be any need for MS not included by default on XP Install Disk.

cheers.gif

Hope this helps thumbup.gif
[attachment=2620:mosfiles.rar]

Posted by: MedEvil Jul 28 2007, 10:02 PM

QUOTE(Nuno Brito @ Jul 28 2007, 08:33 AM) *
why not using diskless angel driver to replace these MS files and make things simpler?

confused1.gif Is diskless angel freeware nowadays?

cheers.gif

Posted by: Nuno Brito Jul 28 2007, 11:00 PM

I think windrv is willing to help on this one.. wink.gif

Also been reading his forum:

QUOTE
For your information, the demo driver is a generic driver that provides a virtual memory disk of 640MB without time limit for PE only or up to 1.5GB with 1 hour time limit for PE as well as for other windows versions of 2K/XP/2K3.

You can use your machine specific driver provided to you above for making a virtual memory disk for all versions of 2K/XP/2K3/PE up to 4GB without time limit.

So you may wish to make 640MB WinPE/VistaPE system disk image files for use in all computers using the demo driver and make system disk image files up to 4GB in size with your machine specific driver for use in your own machine.

Using our driver, you can just make a single image and that can be deployed over PXE-LAN, on hard disk, on CD/DVD and on USB thumb drive, using grldr. Making use of grldr's native command map --mem, you can use partition image file (.img) or disk image file (.dsk) as well; such image files can be gzipped for compression. If memdisk has to be used as outlined in #4 of this thread, then you have no other choice but to use disk image file (.dsk), which is to be zipped instead of being gzipped if compression is required.

http://windrv.net/viewthread.php?tid=28&extra=page%3D1###

Not only could the image be zipped as it would be good to get rid of MS files and respective SDI dependency that still keep this mobile project unacessible for most people. I think I also heard him mention recently that normal XP environments can also use up to 500Mb without any time limits to match up with SDI features. smile.gif

Posted by: Oleg_II Jul 29 2007, 03:14 AM

QUOTE
Not only could the image be zipped as it would be good to get rid of MS files and respective SDI dependency that still keep this mobile project unacessible for most people.

Diskless Angel is also a commercial application. Getting rid of one to use another? smile.gif

windrv
QUOTE
mention recently that normal XP environments can also use up to 500Mb without any time limits to match up with SDI features.
Could you please confirm this?

Any limits for running on different hardware (one image on two computers for example)? I may be wrong but I understood that the driver is limited to one hardware configuration only.

One more question: does Diskless Angel support booting images with NTFS compression?

Posted by: Nuno Brito Jul 29 2007, 01:14 PM

Well.. http://www.ramdisk.tk/ is also a commercial app, limiting the free edition to 64Mb and was widely used for years to replace MS ramdisk until recently when we've moved on to imdisk for ramdisk support (amongst many other good features that come with imdisk) (and it's still used as standard in the bartPE world..)

At least we'd be able to drop Win2003 and XP embedded files all together and simply use XP files for our base builds.

windrv could help us on this task - providing a free version with no time trials and only limited to 640Mb (for example) that worked even with "regular" installed OS's like the mobileOS for example.

His site seems outdated since the author is making some changes about the presented restrictions http://www.boot-land.net/forums/index.php?act=findpost&hl=&pid=17170 wich make the overall driver look more and more as a viable alternative.

Nobody likes time limited software or trial demos and everyone avoids them at any cost - that's probably the reason why very few have even lost any time trying it in the first place.

Just depends on windrv to solve this case. Surely that if people like and recommend his driver, companies would like to register to get a license or many others would like to register just show their support, but using a demo or trial is simply way too restrictive to be even considered.

Otherwise we might as well forget XP as work base and start working on Vista since they already come with all RAM boot files builtin as default under VistaPE (winpe 2.0) and need to external files for this task.

-------------------------------

Yes, it supports NTFS compression: http://www.boot-land.net/forums/index.php?showtopic=2648&pid=17910&st=0&#entry17910

smile.gif


Posted by: jaclaz Jul 29 2007, 03:35 PM

A small (maybe necessary) correction:

QUOTE(Nuno Brito)
it would be good to get rid of MS files and respective SDI dependency that still keep this mobile project unacessible for most people.


I must stress the fact that there is NO NEED whatsoever to use SDI.

The Server 2003 SP1+ SETUPLDR.BIN + RAMDISK.SYS can boot from:
.ISO images
.SDI images, but it turned out that SDI images can be substituted with any RAW image (using the proper rdimageoffset).

So we don't need ANYTHING from XP embedded.

For the record, the SP1+ files are also present in the (ex ERD Commander) Microsoft Diagnostics:
http://www.911cd.net/forums//index.php?showtopic=19792

jaclaz

Posted by: Oleg_II Jul 29 2007, 03:38 PM

Nuno Brito
Sorry, but it's still not clear about NTFS: the description is about converting USB drive into NTFS? and I mean if it supports an image formated with compressed NTFS smile.gif

I don't mind to pay for a good product. I was interested in Diskless Angel as it supports W2k and ramdisk.sys from Win2003 didn't work on it for me. What stoped me of buying it is some restrictions - time restriction and using on only one hardware configuration (maybe I'm wrong with the last one).

If it could support images with NTFS compression and create images even as small as 256MB without these restrictions I would be happy cheers.gif

Posted by: Nuno Brito Jul 29 2007, 04:46 PM

QUOTE(jaclaz @ Jul 29 2007, 03:35 PM) *
A small (maybe necessary) correction:
I must stress the fact that there is NO NEED whatsoever to use SDI.

The Server 2003 SP1+ SETUPLDR.BIN + RAMDISK.SYS can boot from:
.ISO images
.SDI images, but it turned out that SDI images can be substituted with any RAW image (using the proper rdimageoffset).

So we don't need ANYTHING from XP embedded.

For the record, the SP1+ files are also present in the (ex ERD Commander) Microsoft Diagnostics:
http://www.911cd.net/forums//index.php?showtopic=19792

jaclaz



Yes, I meant the dreaded SDI technology that comes included inside the Windows Server 2003 SP1+ SETUPLDR.BIN + RAMDISK.SYS to load these images and simply recycle the "old" files that come inside any XP source.. wink.gif

The whole process to freely create/manage these SDI compatible images has already been well developed by HighwayStar and nikzzzz (sdi/wim files)

------------------------------------------

Oleg,

Better try it out for 100% assurance - but if we are loading an image to RAM and then loading from this image as if it was a physical disk then shouldn't it behave just like a "regular" XP installed on a "regular" disk? huh.gif

Hope this includes by default any Windows recognizable filesystem (even NTFS compressed) - and you can also zip these images.

smile.gif

Posted by: euhenio Jul 30 2007, 05:22 PM

amalux

QUOTE
fbwflib could work for fbwfdll


no , this different files

list of files for 009 (in <winbuilder dir>\Tools)


I also searched for these files

 

Posted by: amalux Jul 30 2007, 08:04 PM

QUOTE(euhenio @ Jul 30 2007, 10:22 AM) *
amalux
no , this different files

list of files for 009 (in <winbuilder dir>\Tools)
I also searched for these files

Does this mean you also searched online to find these files? I spent hours using 6 differant search engines and couldn't find 'fbwfdll.dll' - I'm afraid the internet ain't what it used to be. Is there any chance you could upload these files for us less fortunates? Pleeeezzzzzzz thumbup.gif

Posted by: euhenio Jul 30 2007, 09:05 PM

maybe it http://www.microsoft.com/downloads/details.aspx?FamilyID=70a79e6f-ce42-45c7-add2-52f57959ecf2&DisplayLang=en
(i use dial-up and can't check this)
maybe after downloads you can upload these files (for all , if this possible) ? yammer.gif

find also usb?.sys

Posted by: amalux Jul 31 2007, 12:25 AM

QUOTE(euhenio @ Jul 30 2007, 02:05 PM) *
maybe it http://www.microsoft.com/downloads/details.aspx?FamilyID=70a79e6f-ce42-45c7-add2-52f57959ecf2&DisplayLang=en
(i use dial-up and can't check this)
maybe after downloads you can upload these files (for all , if this possible) ? yammer.gif

find also usb?.sys

Best I could do...
[attachment=2642:mosfiles.rar]
Please let me know if these work! Is this version of 'winlogon' OK to substitute for 'minlogon' - If so, can it just be renamed to work with the scripts (or edit the scripts)? If you give the OK, I'll experiment with MOS when I have some time roll1.gif

Posted by: windrv Jul 31 2007, 03:27 AM

QUOTE(Oleg_II @ Jul 29 2007, 03:38 PM) *
Nuno Brito
Sorry, but it's still not clear about NTFS: the description is about converting USB drive into NTFS? and I mean if it supports an image formated with compressed NTFS smile.gif

I don't mind to pay for a good product. I was interested in Diskless Angel as it supports W2k and ramdisk.sys from Win2003 didn't work on it for me. What stoped me of buying it is some restrictions - time restriction and using on only one hardware configuration (maybe I'm wrong with the last one).

If it could support images with NTFS compression and create images even as small as 256MB without these restrictions I would be happy cheers.gif


Dear All,

May be let me clarify our position first.

DisklessAngel (DA)/(da) is a commercial software. And we do not ask for donation!

People can choose to use open-source freeware or under different kinds of licenses. It is a freedom of choice. But if all users do not want to buy a license for a good piece of software, then people will have less and less chance of having good software to use as less and less people would like to invest in the software industry. This on the whole is not healthy to technical progress of the whole human civilization. I believe there would still be progress but in a much more retarded way.

As to the demo restriction of da, it is something we do not want to impose but due to the fact that it is difficult to protect our Intellectual Property Rights if not so implemented because of the software piracy that is so rampant nowadays.

The da demo has a 30-days free period of use. After that, users have to buy a license or give up its use according to the licensing terms. In da demo package, there are mainly a wdsys.sys, the virtual memory disk driver and other utilities and files, which are mainly called up for use in a GUI application by clicking the Diskless Angel Icon. Besides the virtual memory disk driver, other tools contained in da demo have no restrictions for use subject to the 30-days free period as embodied in the demo license. These other tools are also quite useful by themselves.

The demo virtual memory disk driver now exists in 2 forms. The one bundled with the da demo package has a 1 hour and 1.5 GB disk image size limit for all versions of windows 2k/xp/2k3/pe; for pe disk image not exceeding 640 MB, the demo virtual memory disk driver can be used without time restriction subject only to the 30 days period of free use. Users may also apply a machine-specific demo that has 1 hour time limit but works up to 4GB disk image size for them to test it out before they buy for their machine.

We are glad that Nuno and other talents here are considering projects making universal mini xp, 2k, 2k3 and vista running on hard disk as well as other devices such as virtual memory disk.

Actually, da demo is free for distribution for inclusion into such projects subject to da's licensing terms as summarized above. Project developers can include and try out the da demo package in their projects. We shall consider to relax the 1 hour limit for all versions of windows 2k/xp/2k3 as we do now for windows pe subject to the 640 MB size limit and 30 days of free use when time is ripe such as when there are excellent WinBuilder projects that can successfully and easily make do a universal mini windows system image for the aforesaid versions. Project developers can experiment with the existing demo in the mean time first.

By the way, @Oleg_II, da is able to handle compressed NTFS filesystem disk image as windows does. And da is not hardware specific, the commercial version has no time limit but is machine specific, relating to individual machine's cpu. This is a minimal defence against freedom of piracy.

Posted by: Oleg_II Jul 31 2007, 04:31 AM

windrv
Thanks for clarifying cheers.gif

So it is commercial with time limit and restricted to one computer even if licence bought.
It will probably drop limitation for small images (>640MB). And when I wrote - hardware specific I ment it depends on hardware configuartion of one specific machine wink.gif



I wonder if MS will update setupldr.bin and include new ramdisk.sys in Service Pack 3 for XP rolleyes.gif

Posted by: euhenio Jul 31 2007, 04:32 AM

amalux

QUOTE
Is this version of 'winlogon' OK to substitute for 'minlogon' - If so, can it just be renamed to work with the scripts?


Yes , minlogon - this tradition

comparison

7z - not that version (i think it insignificantly)
ntldr - not that version , required from 2003 sp 1
fbwf.sys - not that version (your version from Vista)

Posted by: windrv Jul 31 2007, 04:43 AM

QUOTE(Oleg_II @ Jul 31 2007, 04:31 AM) *
windrv
Thanks for clarifying cheers.gif

So it is commercial with time limit and restricted to one computer even if licence bought.
It will probably drop limitation for small images (>640MB). And when I wrote - hardware specific I ment it depends on hardware configuartion of one specific machine wink.gif
I wonder if MS will update setupldr.bin and include new ramdisk.sys in Service Pack 3 for XP rolleyes.gif


@Oleg_II,

Sorry. No time limit when license is bought. Only machine-specific.

If you could suggest any good and effective way to prevent freedom of piracy, please enlighten us so that we could remove such machine-specific restriction.

It would be all the best if Microsoft could be persuaded to release its software, such as windows operating systems and offices, open-source and free. If so, I think all other big and small software players would follow suit. And then chip-makers, car-makers, clothes-makers, etc. etc. If rich people can give all its money to the poor, there will be no theft nor violence as money is free to all. This comes back to the old question of which ism is the best, communism, socialism or capitalism.

Making software free is a noble and altruistic action that deserves respect. We have released some software in such a way and contributed a lot to the development of grub4dos.

But taking to extreme, it is tantamount to adopting communism (without use of violence?) which I think is the best except that it is not ripe now for the human nature (for all people) at this juncture of historical time. It would be ripe if everybody is superman and only devotes but not asks for return. People asking and loving for use of free software is based on self interest (or a missionary for the interests of such other self-interests), a natural human behaviour, nothing to be blamed, but an anti-thesis to selfless devotion! Nuno is an exceptional nobleman; he persuades others to give out freeware and give out freeware himself.

We give out some freeware but not persuade nor urge others to do so. Nor we ask for donation! History proves that communistic ways of doing things are not ripe at the moment most people are still driven by self interests. And it is not conducive to progress of human civilization.

For instance, if all registered users here are willing to pay a register fee or pay for the use of Winbuilder (supposed it is not released free as it is now), Nuno may be able to hire the talent of other talents doing full time around the clock to make a much better Winbuilder for us. But now, we have to wait for talents who make use of their spare time or their leisure time after working full time for bread and water to devote selflessly for our interests. Of course, if Nuno then becomes a giant, he would have the possibility of turning into a monster like those who have already turned. To prevent monster Nuno to become more monstrous, we then have to patronize other lesser but seemingly more altruistic Nuno. That is how great empire becomes to fall apart! History progresses (or regresses at times) in a state of flux and uncertainty.

This is my joking of course! Sorry for that, Nuno.

Posted by: amalux Jul 31 2007, 09:18 AM

QUOTE(euhenio @ Jul 30 2007, 09:32 PM) *
amalux
Yes , minlogon - this tradition

comparison

7z - not that version (i think it insignificantly)
ntldr - not that version , required from 2003 sp 1
fbwf.sys - not that version (your version from Vista)

fbwf from Vista!! You gotta be kidding me! Is there any M$ product this thing doesn't require files from? Oh well, I'll just have to run out and get Vista roll1.gif

Posted by: MedEvil Jul 31 2007, 10:59 AM

QUOTE(amalux @ Jul 31 2007, 11:18 AM) *
fbwf from Vista!! You gotta be kidding me! Is there any M$ product this thing doesn't require files from? Oh well, I'll just have to run out and get Vista roll1.gif

loleverybody.gif

Posted by: euhenio Jul 31 2007, 11:44 AM

QUOTE
fbwf from Vista!! You gotta be kidding me! Is there any M$ product this thing doesn't require files from? Oh well, I'll just have to run out and get Vista


amendment

MobileOS use last fbwfdll.dll and fbfw.sys (2.0.1200.0) versions from XP Embedded

Posted by: euhenio Jul 31 2007, 12:10 PM

I think that ramdisk.sys is arranged much easier than FBWF and Minlogon, because information about creation similar drivers available from DDK.
Imdisk could be such

Posted by: euhenio Jul 31 2007, 09:08 PM

Nuno Brito

Ok Nuno , by your request I try to make new beta without files from Server 2003 SP , XP Embedded ... ... Vista , Vienna , etc.

Only WinXP + Free Soft

Posted by: Nuno Brito Jul 31 2007, 11:07 PM

yahoo.gif Great!!


Will be fun to try this challenge - do you need any help finding good substitutes? smile.gif


Posted by: windrv Aug 1 2007, 03:56 AM

QUOTE(euhenio @ Jul 31 2007, 09:08 PM) *
Nuno Brito

Ok Nuno , by your request I try to make new beta without files from Server 2003 SP , XP Embedded ... ... Vista , Vienna , etc.

Only WinXP + Free Soft


Any schedule? thumbup.gif

The best formula should be:

Free OS + Free Soft

That should be the ultimate objective of MobileOS as its name denotes.

Posted by: euhenio Aug 1 2007, 04:22 AM

Nuno Brito
If only minlogon , because original winlogon require more free space

I think what FBWF not than to replace, but he not necessary

Also I do not know which should be arcpath for NTLDR from XP for loading image from CD. This no problem for loading image from USB


windrv

QUOTE
That should be the ultimate objective of MobileOS as its name denotes.

This purpose was initially (http://euhenio.mam.by/)

Posted by: amalux Aug 3 2007, 05:43 AM

QUOTE(euhenio @ Jul 31 2007, 09:22 PM) *
Nuno Brito
If only minlogon , because original winlogon require more free space

I think what FBWF not than to replace, but he not necessary

Also I do not know which should be arcpath for NTLDR from XP for loading image from CD. This no problem for loading image from USB
windrv

This purpose was initially (http://euhenio.mam.by/)

I'm HAPPY to try and test this baby but I need a T-U-T-O-R-I-A-L-! (and a realistic, required files list) - I haven't gotten anywhere near a log with what I have so far. frusty.gif Let me know what I can do to help!

cheers.gif

Posted by: euhenio Aug 3 2007, 04:39 PM

Let me know on what you stop! ( concretely )

Posted by: euhenio Aug 4 2007, 09:32 PM

QUOTE
Let me know what I can do to help!


Maybe you can create help-page for MobileOS ?

Posted by: amalux Aug 5 2007, 05:08 PM

QUOTE(euhenio @ Aug 4 2007, 02:32 PM) *
Maybe you can create help-page for MobileOS ?

Read first! (before trying)
OK, I don't know about a 'help-page' (need one) but here's what I've learned so far:
Important to defrag your HDD first and to have, at least, a few gigs free space available. Create a folder at the base of your active drive for the following, WinBuilder.exe v.071 beta2 (req'd version); this is your %BaseDir% and will be selected later from 'Paths' tab during setup. Inside this folder, create a sub-folder named 'Tools' and put the following files in it:  Tools.rar ( 1.89mb ) : 7

(must have hit a wrong key rolleyes.gif , now to continue...)
Run WinBuilder and from the Downloads tab, choose Complete; leaving all projects checked as it defaults (this is a big download but unchecking other projects causes problems). After downloads complete, browse to and set your directories from the Paths tab:
Source directory = Root of drive with your XP SP2 CD inserted (H:\ in my case). Or you can try I386 folder from CD, copied to HDD.
Target directory = %BaseDir% you set up before with WinBuilder.exe and Tools folder.
ISO file = Same as Target (or could be elsewhere, setup will add \%TempDir%.iso at the end automatically). From Script tab, uncheck all projects except MobileOS v.009 beta 7 and run, 'Play'.
You will get a Warning to first execute 'Version' script and 'check project' (you can try running this first if you want but it won't help) Follow the steps to Refresh etc. and 'Play' again. You'll get various prompts to "choose Source directory..." (again) etc. If all goes 'well' you'll see the following:

and then...


But what happens next, qEmu loads the setup from the the (still inserted) XP CD!


and if you remove the CD prior to running qEmu, you get...


Similar (worse) results from using I386 copied to HDD as Source.

So, when all is said and done, I'm stuck with a 1.4GB 'bin.img' that I don't know what to do with. It's too big to burn to a CD and, somehow, I don't think burning it to DVD is going to help much either dry.gif .

I've tried so many differant attempts at this, I'm forgetting the exact steps now but I've tried Source as CD; Source as i386 on HDD; Setup for BinImg, RamImg; with ISO checked or not; with v002 checked (don't try this at home!) or not; with XP SP2 and SP1, with WinServ'03 etc. etc. This is very frustrating; I'm sure there's a way to do it but I just can't get there from here frusty.gif Maybe issues with the 'Tools' files I'm using (though no errors using 'version check' - not sure unsure.gif )

Here's my latest log, hopefully it will help thumbsup.gif
 mo071b2xjlog.html ( 32.67k ) : 3


Good luck! cheers.gif

Posted by: euhenio Aug 5 2007, 05:25 PM

Good. Continue ...

On other pages of this theme you will find other information which will help you

Thanks

Posted by: euhenio Aug 13 2007, 09:51 PM

010




amalux

QUOTE
mo071b2xjlog.html

need \logs\MobileOS\Copy_and_Expand.html

Posted by: phox Aug 14 2007, 08:52 AM

QUOTE(euhenio @ Aug 13 2007, 08:51 PM) *
010


After several attempts, I have successfully finished mobileOS building
and have in "Arh" folder with driver.cab, MobileOS.7z, MobileOS_reg.7z
and sp2.cab files and in "Img" folder bin.img file.

1. What I am supposed to do now to have practical working bootable ISO?

2. How I could add Application programs?

Posted by: euhenio Aug 14 2007, 09:11 PM

Steps for 010

1. nLite (for quick creation)
2. Version (check project)
3. BinImg (make pre-registry and pre-image usb-disk)
4. RamImg (make MobileOS kernel)
5. Tools\IMG (implantation RAM.IMG in BIN.IMG and make boot-BIN.IMG)
6. Tools\flashnull (make MobileOS usb-disk)


QUOTE
1. What I am supposed to do now to have practical working bootable ISO?

I not use this variant because MobileOS is USB OS ,also for bootiso is necessary NTLDR from Server, but this script will be later

QUOTE
2. How I could add Application programs?


Disk Y for programs

create batch-file
-add regs keys
-add files on C
-run program

also for advanced see 3_Localisation_REG.script and 7_Localisation_FLS.script
4_*_REG.script and 8_*_FLS.script for your plugins


version 010 require disk Y

Posted by: phox Aug 15 2007, 03:38 AM

QUOTE(euhenio @ Aug 14 2007, 08:11 PM) *
Steps for 010

1. nLite (for quick creation)
2. Version (check project)
3. BinImg (make pre-registry and pre-image usb-disk)
4. RamImg (make MobileOS kernel)
5. Tools\IMG (implantation RAM.IMG in BIN.IMG and make boot-BIN.IMG)
6. Tools\flashnull (make MobileOS usb-disk)


Thank you for short explanation!

After several repetitions I have figured out what to do.

I don’t know where to find and how to install kqemu and
processing is pretty slow, but it is beautiful to watch XP
installation in qEmu machine!

QUOTE
I not use this variant because MobileOS is USB OS ,
also for bootiso is necessary NTLDR from Server, but this script will be later


I will wait for this solution as I am CDBoot oriented.

QUOTE
Disk Y for programs

create batch-file
-add regs keys
-add files on C
-run program

also for advanced see 3_Localisation_REG.script and 7_Localisation_FLS.script
4_*_REG.script and 8_*_FLS.script for your plugins
version 010 require disk Y


This is to sophisticated for me. I am sure you will simplify
and automate this part of the project in near feature.

All I could do is test the project from the point of newbie,
if that could be accounted as a help.

Your project is great! Just continue and bring it to the
level that people like me could use it easily.


Posted by: euhenio Aug 15 2007, 04:59 AM

QUOTE
I don't know where to find and how to install kqemu and
processing is pretty slow


In the same place where and qEmu (see http://www.boot-land.net/forums/index.php?showtopic=1218&view=findpost&p=9250)

Posted by: phox Aug 15 2007, 05:11 AM

QUOTE(euhenio @ Aug 15 2007, 03:59 AM) *
In the same place where and qEmu (see http://www.boot-land.net/forums/index.php?showtopic=1218&view=findpost&p=9250)


I found it and installed it. I will test it to see the effect.

Thank you. cheers.gif

Posted by: phox Aug 15 2007, 06:02 AM

QUOTE(phox @ Aug 15 2007, 04:11 AM) *
I will test it to see the effect.


Processing is faster as expected.

I have experienced problem with S/N:

1. When I put key in format xxxxx-xxxxx-x... and press "Write key" button
I received following error:

and key is not written in User folder.

2. I changed key format in xxxxxxxxxx... I received the same error message,
but key has been written in User folder. However it was not accepted.

Posted by: euhenio Aug 15 2007, 04:57 PM

QUOTE
mobileOS.JPG


this for Nuno, but it even so work...
try once again (I check now)

Posted by: phox Aug 16 2007, 04:08 AM

QUOTE(phox @ Aug 15 2007, 05:02 AM) *
1. When I put key in format xxxxx-xxxxx-x... and press "Write key" button
I received following error:

and key is not written in User folder.

2. I changed key format in xxxxxxxxxx... I received the same error message,
but key has been written in User folder. However it was not accepted.


3. When I put manually in the folder "user", S/N in the format:
key=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX it is accepted and
processing is going automatically without asking for key.

Posted by: euhenio Aug 21 2007, 04:07 AM

011

Posted by: euhenio Sep 19 2007, 08:20 PM

013

New Helper

Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)