View topic - Intrested in making your own OS as a team? - Windows, Apple, Application, Abandonware and Game Beta Downloads/Repository

Whistler2600

Hey all,
First: I think this is the right forum...
Anyway: You are here to join a team of people that will custom make a Windows OS. There can be alphas, betas, RC's, and RTM's (except without the "release to" part). Then there will be the final.
RULES!
-------
To make this legal and comply with site rules (warez...), THIS PROJECT IS A BETAARCHIVE PROJECT ONLY! THE PRODUCTS ARE NOT TO BE DISTRIBUTED. THE SAME GOES FOR ALPHAS AND BETAS. I will assign product keys to participants in the project. Me and participants above "1337 beta collector" status will be given Master (oem) product keys. DO NOT DISTRIBUTE THE KEYS EITHER!
HOW
-----
The windows 2000/NT 3.1/4.0, DOS 6.22, etc source code can be recompiled. If you do not have a copy, PM me and I will show you a link to whatever you need. :wink:

Everyone makes suggestions about what to put in the OS. The best of each OS will go into the next build. The build # will start with 2196 (not 2195, this will be very 2000-ish

) All changes must be approved by me or any Mod/admin that participates. If no mod/admin participates, I will assign 2 people. The final will bear the final name (chosen by us all, I WILL decide along with any mod/admin or the 2 special people I assign, however, I choose the codename

) I will post links to the build ISO's in the forum. They will be in TAR/7z/RAR format. They will also include a password so that sharing will be harder. I will PM all participants passwords. If this is not allowed, We MUST PM eachother the ISO's as they are produced by me. Once you compile something, compress it (rar/tar/7z only), and I will make the ISO. The ISO will be bootable. Try it out! If it works, tell us! Give feedback! If it doesn't, or is unstable, tell us!
INFO
-----
Must STRIVE to make it run on x86 AND x64 processors
Minimum ram: 128 MB, 300 MB recommended.
HD: Idk, 2 GB min, 10 recommended.
Support for FAT16/FAT32 and NTFS
OTHER STUFF
--------------

Current participants:
Blizzardo1
DBlake
DjRob
Me

PortalCake
Windows OCManage
dirtwarrior
vm.Xeon
Awesome
The Distractor
digidude2008
tushar_verma_333
pizzaboy192
4512jth
angelwolf71885
ReactOS
darthtk118
skywalker06
leonbollerup

My assistants project coordinators are in BLUE text. Contact them when I am not around.

PortalCake

I can join. I don't know much programming beyond VB, but I'm really good as a tester.
However, I have a legal Dreamspark copy of VS 2008 Pro and 2003.

NOTE: We do not want this to go the JoeJoe way. (remember LHR?)
And don't we have only 600~ MB of Windows 2000 source?

Kenneth

I compiled the NT source successfully and implemented a new BSoD in the WRK, why not?

I recommend that we start With Server 2003 SP1.

EDIT: We have WinNt 3.1 source?

PortalCake

Can W2k run with Server 2003 kernel?
If so, then let's start with that.
And remember, W2k doesn't have a certain "SLSVC", so that means we can play around.
I don't even need to mention the hack that allows you to install W2k without a serial.

Kenneth

No, no, no, no. The typedef structs are too different.

I am saying Server 2003 SP1 because it supports WIM Boot, Correct RAM Boot, TFTP server in Ntldr, Extended support in WDK.

Remove WPA, and place Win2Ks Licensing Subsystem in W2k3.

PortalCake

Windows OCManage wrote:

No, no, no, no. The typedef structs are too different.

I am saying Server 2003 SP1 because it supports WIM Boot, Correct RAM Boot, TFTP server in Ntldr, Extended support in WDK.

Remove WPA, and place Win2Ks Licensing Subsystem in W2k3.

Oh, okay. Sorry for the misunderstanding.

But doesn't W2k's SLSVC is almost nonexistent?

Awesome

I'll join in.
I can make batch files and test anything needed.

I don't have access to the FTP yet though...
Any ideas for the new OS?

Kenneth

PortalCake wrote:

Windows OCManage wrote:

No, no, no, no. The typedef structs are too different.

I am saying Server 2003 SP1 because it supports WIM Boot, Correct RAM Boot, TFTP server in Ntldr, Extended support in WDK.

Remove WPA, and place Win2Ks Licensing Subsystem in W2k3.

Oh, okay. Sorry for the misunderstanding.

But doesn't W2k's SLSVC is almost nonexistent?

Windows 2000 doesn't have SlSvc, neither does VLK Windows Server 2003/XP.

Use a WinLogon Patch to go back to a Windows 2000 style Licensing Style, where the Product Key uses pidgen.dll and that's it, no verification by WPA.

PortalCake

Windows OCManage wrote:

PortalCake wrote:

Windows OCManage wrote:

No, no, no, no. The typedef structs are too different.

I am saying Server 2003 SP1 because it supports WIM Boot, Correct RAM Boot, TFTP server in Ntldr, Extended support in WDK.

Remove WPA, and place Win2Ks Licensing Subsystem in W2k3.

Oh, okay. Sorry for the misunderstanding.

But doesn't W2k's SLSVC is almost nonexistent?

Windows 2000 doesn't have SlSvc, neither does VLK Windows Server 2003/XP.

Use a WinLogon Patch to go back to a Windows 2000 style Licensing Style, where the Product Key uses pidgen.dll and that's it, no verification by WPA.

Oh, okay, now I get what you mean by using 2k3 as a base, you use the whole of 2k3, then strip off activation, then go mod-happy, am i right?

vm.Xeon

So, Can I join?
I can test anything/everything. (I have very old PC to test this 8-)

)
So, Can I give you some ideas?

And one question: You're talking about Windows Server 2003 like about a base for the new OS. I know what Win2k3 32-bit support up to 32 Gb of RAM. Are you going to insert this option into the new OS? If you do this it will be great

Kenneth

PortalCake wrote:

Windows OCManage wrote:

PortalCake wrote:

Windows OCManage wrote:

No, no, no, no. The typedef structs are too different.

I am saying Server 2003 SP1 because it supports WIM Boot, Correct RAM Boot, TFTP server in Ntldr, Extended support in WDK.

Remove WPA, and place Win2Ks Licensing Subsystem in W2k3.

Oh, okay. Sorry for the misunderstanding.

But doesn't W2k's SLSVC is almost nonexistent?

Windows 2000 doesn't have SlSvc, neither does VLK Windows Server 2003/XP.

Use a WinLogon Patch to go back to a Windows 2000 style Licensing Style, where the Product Key uses pidgen.dll and that's it, no verification by WPA.

Oh, okay, now I get what you mean by using 2k3 as a base, you use the whole of 2k3, then strip off activation, then go mod-happy, am i right?

Yes.

Kenneth

*hacks up code*

Code:

 Volume in drive W is KernelLab01
 Volume Serial Number is 865A-28E4

 Directory of W:\binaries\ntlego

[.]             [..]            4mmdat.sys      adicsc.sys      agp440.sys
atapi.sys       bootvid.dll     cdfs.sys        ddmlapp.exe     ddsmc.sys
dlttape.sys     elmsmc.sys      exabyte2.sys    examc.sys       fastfat.sys
gagp30kx.sys    hpmc.sys        i2omp.sys       i8042prt.sys    intelide.sys
kbda1.dll       kbda2.dll       kbda3.dll       kbdal.dll       kbdarme.dll
kbdarmw.dll     kbdaze.dll      kbdazel.dll     kbdbe.dll       kbdbene.dll
kbdblr.dll      kbdbr.dll       kbdbu.dll       kbdca.dll       kbdclass.sys
kbdcr.dll       kbdcz.dll       kbdcz1.dll      kbdcz2.dll      kbdda.dll
kbddv.dll       kbdes.dll       kbdest.dll      kbdfc.dll       kbdfi.dll
kbdfo.dll       kbdfr.dll       kbdgeo.dll      kbdgkl.dll      kbdgr.dll
kbdgr1.dll      kbdhe.dll       kbdhe220.dll    kbdhe319.dll    kbdheb.dll
kbdhebx.dll     kbdhela2.dll    kbdhela3.dll    kbdhept.dll     kbdhu.dll
kbdhu1.dll      kbdic.dll       kbdinasa.dll    kbdinben.dll    kbdindev.dll
kbdinguj.dll    kbdinkan.dll    kbdinmal.dll    kbdinori.dll    kbdinpun.dll
kbdintam.dll    kbdintel.dll    kbdir.dll       kbdit.dll       kbdit142.dll
kbdkaz.dll      kbdla.dll       kbdlt.dll       kbdlt1.dll      kbdlv.dll
kbdlv1.dll      kbdmac.dll      kbdne.dll       kbdno.dll       kbdpl.dll
kbdpl1.dll      kbdpo.dll       kbdro.dll       kbdru.dll       kbdru1.dll
kbdsf.dll       kbdsg.dll       kbdsl.dll       kbdsl1.dll      kbdsp.dll
kbdsw.dll       kbdtat.dll      kbdth0.dll      kbdth1.dll      kbdth2.dll
kbdth3.dll      kbdtuf.dll      kbdtuq.dll      kbduk.dll       kbdur.dll
kbdurs.dll      kbdus.dll       kbdusa.dll      kbdusl.dll      kbdusr.dll
kbdusx.dll      kbduzb.dll      kbdvntc.dll     kbdycc.dll      kbdycl.dll
kdcom.dll       mcamgmt.exe     miniqic.sys     mirror.dll      mirror.sys
mouclass.sys    nsmmc.sys       ntosamd64.exe   ntosx86.exe     p2kdx.dll
parallel.sys    parport.sys     pciide.sys      pciidex.sys     perm2.sys
perm2dll.dll    qic157.sys      SerEnum.sys     serial.sys      sermouse.sys
sfloppy.sys     sonymc.sys      uagp35.sys
             136 File(s)      7,696,609 bytes
               2 Dir(s)   1,068,617,728 bytes free

vm.Xeon

@Windows OCManage
Can I ask you?
I understood, what are you going to build a new OS with Windows 2000 source code and Server 2003 Volume Activation system. Is it true? And are you going to move another Windows Server 2003 feautures into this OS?
How I understood you are going to do new OS from Windows 2000?

Kenneth

vm.Xeon wrote:

@Windows OCManage
Can I ask you?
I understood, what are you going to build a new OS with Windows 2000 source code and Server 2003 Volume Activation system. Is it true? And are you going to move another Windows Server 2003 feautures into this OS?
How I understood you are going to do new OS from Windows 2000?

No, I'm using Windows Server 2003 SP1 RTM with Windows 2000 code+Windows NT code, and WinDDK code (NtLego) to substitute for compiled MS components (Dnsrv).

dirtwarrior

This is a major undertaking but intriguing. If possible I would like to join. Not sure how much I can help though.

Awesome

We have some volunteers...

Any codenames?
I like "Onyx" (black quartz-rock)

vm.Xeon

Awesome wrote:

We have some volunteers...

Any codenames?
I like "Onyx" (black quartz-rock)

So, somewhere I heard this codename...
If you started to talk about rocks... May be "Topaz"?

And I have a question to Whistler2600: Can I give some ideas for you?

Whistler2600

anyone is free to give ideas...read first post. I will generate the keys along with Windows OCManage. I will work on straightening things out here...i like the discussion so far!

BTW: Can i get Advanced member access, along with the other non-advanced members that are interested, so we can move this to the private forum?

Codename: Illinois

Everyone that requested to join can. I don't care if you can program or can't, you can just test and give feedback! You can also photoshop/animate, we WILL need that!!

EDIT: I am planning on running this off the NT 4.0 kernel and basing it off that. We can then hack it up so that the Win2K kernel and 3.1 and 4.0 files get along nicely. We can integrate compiled files from other OS's too.

dirtwarrior

It sounds like the OS microsoft should have put out.

Whistler2600

dirtwarrior wrote:

It sounds like the OS microsoft should have put out.

that is one of my intentions

Blizzardo1

I'm all VB. I have no experience with C++ or C#. So I will be able to implement a few programs to the System.

Whistler2600

Blizzardo1 wrote:

I'm all VB. I have no experience with C++ or C#. So I will be able to implement a few programs to the System.

great!

Blizzardo1

I have an application that took me an hour to make. I call it the Basic System Info (BSI). It gives you the name of the OS, Version, Platform, Locale, Ram usage, VRam usage, and CPU usage. Tell me where to upload it and I will let you guys fool with it. Tell me what you think... Does it need another name, or does it need more things? Tell me and I will update it with the things you give me.

Whistler2600

Blizzardo1 wrote:

I have an application that took me an hour to make. I call it the Basic System Info (BSI). It gives you the name of the OS, Version, Platform, Locale, Ram usage, VRam usage, and CPU usage. Tell me where to upload it and I will let you guys fool with it. Tell me what you think... Does it need another name, or does it need more things? Tell me and I will update it with the things you give me.

Like it! I think we should integrate it into winver

EDIT: Integrate into Winver and have it on the "tools" menu on task manager

Rob Jansen · Last edited by Rob Jansen on Sun Aug 09, 2009 9:31 pm, edited 2 times in total.

Blizzardo1 wrote:

I have an application that took me an hour to make. I call it the Basic System Info (BSI). It gives you the name of the OS, Version, Platform, Locale, Ram usage, VRam usage, and CPU usage. Tell me where to upload it and I will let you guys fool with it. Tell me what you think... Does it need another name, or does it need more things? Tell me and I will update it with the things you give me.

Nice program can you upload it with a a revision or 2?:

1) RAM in MB please (and percentage full)
2) VRAM in MB please (and percentage full)
3) Keep the current version, but add this build string: ''7600.16385.amd64fre.win7_rtm.090713-1255''
It is found in:
Regedit.exe --> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Currentversion\BuildLabEx
4) Current logged in user/login time (like in the Windows XP Security box with CTRL+ALT+DEL in Domains/Classic logon).

Also, this should go into the BetaArchive ''toolbox''.

EDIT:
Maybe a small menu with some options, examples:
- Winver.exe
- sysdm.cpl (on XP and earlier, Vista/7 does have it, but not the GENERAL tab with Computer Information, CPU/RAM)
- Notepad.exe (to take notes)
- Paint.exe (to past a few screenshots for the MWCB and other sites).

All in Windows\System32 or Windows\System
but at least in every path of the every computer.

Intrested in making your own OS as a team?

Who is online