11 replies to this topic

[s4b3r6]

Well, considering I've got a domain through you for this project, I may as well show you a little more detail with the project:

James Operating System H builds is a operating system made to
run off a live media, either CD or USB, this live OS saves no settings, or files within itself, but supplies access to the
computer's drives, allowing it to be used as a recovery
OS.
JOS.H is built on the proven system of Windows Preinstallation Environment (3.0 ie. Windows 7 Preintsllation Environment), and
is not designed as a recovery operating system, or an everyday operating system. It is supplied as a way of testing softwares
that you are unsure of, or as a development tool to run existing Win32 applications to debug and continue development in a workspace where a full-blown Windows 7 Environment is not a plausible option. This means that it does not breach the
standard End User License Agreement for use with
WinPE.

Yesterday I had an online meeting with Terry Larson and two representatives from Microsoft about the project, and they gave me a few messages.
I have approval to self-market JOS.H, use OpenOffice as the office suite for the OS, I have approval to use and modify Windows PE as the basis as much is neccesary, and I was given an ultimatum.

The final allowable delivery date for Build 1.0 of the James Operating System H build (Codename Hannibal) is August the 3rd 2012.

Check out the site for more detail, and be aware I am still in the process of building it...

Thanks all.

Find it here: http://josh.w07.net

[Brito]

It's good to hear your progress.

Just some tips.

- Include the project homepage on your forum signature and also on the first topic so that people can visit your site and learn more about it

- On the overview page there is a small typo: "And several other irrelvant programs." and "Microsoft .net Framwork 1,2 and 3."

- If possible, please add some screenshots of the running system as it will help people to get a quick glimpse of the project.

[was_jaclaz]

Good

Now we have TWO posts without a link to where the project actually is.

I won't allow a third one

The site given here:
http://www.boot-land...?...=9884&st=10

http://www.josh.w07.net/

gives:

Forbidden

You don't have permission to access / on this server.
Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.5.1 mod_jk/1.2.25 mod_python/3.3.1 Python/2.5.2 PHP/5.2.4-2ubuntu5.6 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g mod_perl/2.0.3 Perl/v5.8.8 Server at www.josh.w07.net Port 80

So what?

WHERE THE HECK can be found something about this project?

jaclaz

[s4b3r6]

Good


WHERE THE HECK can be found something about this project?

jaclaz

My mistake... It isn't 'www.josh.w07.net' it IS however 'http://josh.w07.net'
I'll update my first post.

[was_jaclaz]

Good

We are allowed to post clickable links (at least to things we actually do/host ), so finally here it is in all it's beauty:
http://josh.w07.net



jaclaz

[MedEvil]

@s4b3r6

I would like to know:
- Do you plan on using winbuilder?
- Where do you see the difference to the already existing Win7 projects?
- In what stage is your project at the moment?

[was_jaclaz]

@s4b3r6

And now of course the problems begin:
since you are a new user on the board, you might not know how picky I am, but trust my word on it, I am very, very picky .

A couple of questions/considerations about this:

If you agree to this license and can tell me why I should agree to letting you test the software for me, yes.
For now that's how things stand, hopefully in future it'll be a more user friendly way of doing things. Until JOS.H
is ready for the light of day though I don't think this will change much. The testing phase is one of the most important parts of developing this OS, and currently it hasn't passed muster.

The license requires two signatories to sign, the beta testor and myself. You would be required to print and read the document, sign if you agree, and attach on the back a paragraph or three about why you would like to test the software.
You would then have to either fax or scan/email the document to my email. Include the header 'James Operating System Habile' in your email or I may disregard it.

I would like to have some link to the Microsoft OEM licensing program, to better understand the implications of the linked to EULA.

I can understand "passed muster":
http://www.thefreedi...nary.com/muster
but it's a bit idiomatic, as I see it, for an international audience.

and attach on the back a paragraph or three about why you would like to test the software.

does this mean that if I attach TWO paragraphs I won't be eligible?






jaclaz

[Brito]

You can read the overview log, it has some details of the current project status.

[s4b3r6]

@s4b3r6

And now of course the problems begin:
since you are a new user on the board, you might not know how picky I am, but trust my word on it, I am very, very picky .

A couple of questions/considerations about this:


I would like to have some link to the Microsoft OEM licensing program, to better understand the implications of the linked to EULA.

I can understand "passed muster":
http://www.thefreedi...nary.com/muster
but it's a bit idiomatic, as I see it, for an international audience.


does this mean that if I attach TWO paragraphs I won't be eligible?






jaclaz

The paragraph or three is my way of saying I don't want a one liner answer. I would very much like to have testers that will actually test correctly and have the correct mindset. Testing without using any parameters to guide you is not what I am looking for. I want people who will be looking for bugs that need to be fixed, such as a call to explorer.exe for example.

The Individual Developer OEM License under which I operate allows me to modify and create systems. It is listed under No. 018317A6AE418.

From the OEM 018317A6AE418:

•••• General License Grant to Install and Use Software Product. You may install and use as many copies as necessary of the Software Product on multiple computers, devices, workstations, terminals, or other digital electronic or analog devices (“Devices”). You may make a second copy of the Software Product and install it on a portable Device for the exclusive use of the person who is the primary user of the first copy of the Software Product. You also may make and use copies of the Software Product to develop and test Your software products so long as there is only one (1) unique user who accesses and uses all such copies of the Software Product, the only exception of this is the ‘testing phase’ of the development process whereby You may grant a single testing license to another user. A license for the Software Product may not be shared

[s4b3r6]

@s4b3r6

I would like to know:
- Do you plan on using winbuilder?
- Where do you see the difference to the already existing Win7 projects?
- In what stage is your project at the moment?

No. 1, I have used WinBuilder in the past for other projects, however for this project I haven't so far, and probably won't in the future. Not because of WinBuilder itself, but I'd rather create it using the PE Commandline, which has proven itself many times over. It's a personnal choice.
I particularly like Dism, the switch from imagex to Dism was difficult at first, but now I run most commands off the top of my head.

The main difference I see between JOS.H and many other Windows 7 projects is for one, is the fact that I have recieved approval from Microsoft directly, not many other projects do have this, secondly is that though it is not an everyday system, it is meant to be a complete package with an out-of-box expirience, where everything just works.
Many systems are aimed at a particular task, such as multimedia, internet and OS repairs, however JOS.H is as I have said, a complete package, which is the main reason for getting DirectX and OpenGL fully working, as well as incorporating the .net frameworks.

You can check the overview page at the site for the current progression, but as of now several components are working:

RocketDock as shell, (Looking for alternatives currently. It's a little too common.)
Wired networking works correctly.
Firefox.
Thunderbird.
Sunbird.
OpenOffice 3.0
Pidgin (Instant Messenger.)
ClamWin and Stinger antivirus
Ghostfirewall and the inbuilt firewall
FreeCommander as file manager
128mb scratchdisk
OpenGL ES 1.1 (Security limited version of OpenGL)
Direct3D (Partial DirectX implementation.)
VLC Media player
Xirrus WiFi Inspector (Currently untested - I'm about to load it up to test it. I have the WiFi nic working, just getting a script that will make it connect is my issue, as WinPE doesn't have the netsh wlan implementation like Vista/7 does.)

[was_jaclaz]

I would like to have some link to the Microsoft OEM licensing program, to better understand the implications of the linked to EULA.

The Individual Developer OEM License under which I operate allows me to modify and create systems. It is listed under No. 018317A6AE418.

I'll try to rephrase.

Can you give me a link to a Microsoft Resource of some kind where the "Individual Developer OEM License" is explained/talked about?

I wasn't able to find anything called "Individual Developer OEM License" on MS sites like this one:
https://partner.microsoft.com/40019037

Maybe the MS name for it is slightly different.



jaclaz

[s4b3r6]

I'll try to rephrase.

Can you give me a link to a Microsoft Resource of some kind where the "Individual Developer OEM License" is explained/talked about?

I wasn't able to find anything called "Individual Developer OEM License" on MS sites like this one:
https://partner.microsoft.com/40019037

Maybe the MS name for it is slightly different.



jaclaz

I'll see if I can get you the direct link once the site is back up. (Volume License Service Center is down for maintainence.)

Edit- There is no public documentation of Volume Licensing Agreements. The public cannot truly learn much about Volume Licensing from Microsoft.
The EULA does cover all the specifics of the OS though, and is not in conjunction with the agreement that binds the creator.
Becuase of your concerns I will update the EULA to remove End Users responsibility from the license agreement by which I am bound.