patchworks

Of course, but it's a long-term goal, this means you've misunderstood my open sourcing idea approach. I repeat: using what ALREADY exist, build a WPI that substitutes original MS-components (Internet Explorer, Media Player, Notepad, Calculator, etc, etc, deep to the kernel) with open source ones. The benefits is to have a fully functional OS since the "0.01 pre-alpha" release (that means attract people in the project), then devs can open source every component not yet implemented by 3rd party. The drivers question is really interesting, but i think that an indipendent team should work on this; for example it would be great to involve DriverPacks.net guyz... (that joined open source last November)

Another reason to support an open source (win32?) super-FDISK & FORMAT is to implement a deep erase function. Do you remember the good old Central Point COPY ][ PC BULK ERASER ? It's the unique tool that allowed me to "revive" unmagnetized disks. Why not a Windows version ?

Again guyz, you're OT: i never talked about open sourcing drivers (even if this discussion could evolve in a very interesting way...) Uhmmm... no, i'm not a developer. I'm just purposing the idea to peoples that can do it.

Ehm... NO.

Well then, the ROS website is back on-line ! Check out my Untested open source software list and the ReactOS Applications page too. I also wanna suggest all to check the structure of the Open Source software list wich i purpose for Wikipedia, in place of List of open source software packages one, if someone wanna help me. B)

VideoLAN MediaCoder

Yeah, someone agrees that open sourcing 9x could be interesting, come other says that it's just a waste of time. My opinion is: if you REWRITE an os (such as ReactOS devs are doing) it's a really hard to see results in short time; patching fully functional os is surelly faster (you have a working os since the beginning), not so hard but not either useful for the majority of MS Windows users. Anyway people (like me, DeadDude or them) that can't upgrade (for different reasons) deprives of hope due to MS-support abandon. I think is the same reason for uSP and all unofficial patches & stuff in this forum. BTW open sourced 9x let us mantain stability and (why not) improving many features, keeping the compatibility; it can helps the community (ReactOS one in my mind...) to know better how Windows works and how implement something. We can also exchange solutions, developers and (of course) source code between similar projects, in order to keep 9x alive. Not only: it could be also a good way to approach "historical" windows users, hoping to bring them on ROS (in the future)... Well, this is one of the problems partially solved by the open source Kernel Update Project... Well... or have an open sourced version ! As already sayed my idea is more similar to your JackHammer goal... but: how to proceed ? 1. I believe that a WPI (Windows Post-Install Wizard) is the best solution for this goal; it also solve license violations (wanna remember all of you that GPL allows "mere aggregation" but not "combination" ) 2. Collecting open alternatives: MS 9x kernel -> KUP, MS (W)MP -> skinned-VLC, etc. 3. Choosing good and "resonant" name for the project (do you remember the Lindows litigation ?): GNUWIN sounds cool and has a cool bivalence (GNU sounds like 'NEW' in some language) in my opinion... Ideas are welcome !

...i rise my Open Sourcing 9x idea (gradually substitute original MS-Windows components with open source ones) again. For example: why not replace Media Player with skinned-VLC ? Addictional note: a WPI tool should be more legal (than bundling GPL with closed source softwares) to me...

I know that quoting yourself is not good, but: JackHammer is not that bad... at least in its "soul". I think it has to be modulated better... (check out the Open Sourcing Windows 9x 3ad !)

1st: i havent tried it, still downloading (torrent downloads would be apreciated) 2nd: thanks for the christmass present ! The open source nature of the project brings a question in my mind: does the jackhammer goal changed ? If i remember well, the goal was to open source windows 98... Another question: source code is about 3,5 Mb... how can become 2 cds ? According to the Installation guide the procedure is not so simple... don't you think that a "selective feature installer" (something like 98lite) would be simpler and easier for users ?

Just a question: could this patch become a part of the Kernel Update Project ?

Hey guyz, do you read my posts ?

awergh i don't want to "Bite off more than one can chew", my idea is mutch simpler: something like a WPI (Windows Post-Install Wizard) made of ONLY open source softwares that substitutes (uninstall) official components.

Since we're talking ( ) someone is working...

Of course, you live in Chicago... I live in Italy and i like free (as beer) stuff but legal (many peoples here simply don't care about copyrights: we're one of the most piracy-slaves western country). Open source is the best compromise between my, your and others (for example ones that looking for FREE as in speech or frequently updated software), i think. Nero ? -> Infra Recorder wmp9 ? -> MPC 98mp10? -> VideoLAN office2000 ? -> OpenOffice B)

Would you bet on it ? Even antiwpa/wga "lived" without problems since last week... If you "live in the fog" you must hope the sun never shine. Personally i don't like this approach; I don't think that any MS employee works for free, so: why these guys do not deserve a wage ? MS would say: "We never asked them to do this ! On contrary, they're violating our copyrights !". 1+1=2 Volunteer work should be for the whole community, but original authors have to tutelate their rights = choose an open source license for your works !

Sorry, i haven't see your question, and here's the reason: 'cause i see *many* peoples that are working as volunteers for free to build AutoPatchers, 98SE2ME, uSP, etc. and many other interesting projects that could become a "waste" of energies. I wanna remember all that MS has the right to sue them if should find something that sounds like a "lost profit". With an open source license (GPL is better) so mutch work should be preserved from any kind of attack. In other hand, all the knowledge could be shared with 3rd party projects (i have ReactOS in my mind, but there are many other interesting communities...) to help their grow. That's my point of view; anyway, like you, i'm just a user.

...or you can gradually substitute every windows component with an open source one (a sort of "extension" of the Kernel Update project philosophy to the whole OS)

Hey guyz, the discussion stage is gone 2 pages ago... Please enter the "pre-alpha working" phase ! I mean: don't talk about IF we can do this, but HOW.

I don't wanna be boring (even if i probably aready be), but check out those links for a faster explainations of licenses: CC-GPL 2.0 CC-LGPL 2.1 These are the so-called "common deeds", simply & multilanguage license explainations. HaPpY CoDiNg !

Well, an open source version ! (...and a 9x version would be great too...) I mean a version that installs just open software. Check out my post @ Windows 98 Seven Years Later Ed. Boot CD 3ad...

Dunno if there's someone interested, but here's an interesting discussion about the open source MS-Paint alternative... (...and here's a preview of the young baby imagesoft ! )

Ops... sorry ! Releasing it under GPL gives you mutch more ensurements against these kind of problems (check this article out). ....and you can get a page @ SF !

'cause (unfortunally) our -perfectly working- Guillemot Maxi Studio ISIS don't have any other driver than Win9x... We lend -almost for free- the machine equipped with this card/software to emerging artist, allowing them to learn how to autoproduce their music.