DriverPacks.net Forum - Windows Home Server with Power Pack 1

Re: Windows Home Server with Power Pack 1

null@example.com (OverFlow) — Sun, 03 Jan 2010 01:46:14 +0000

just use DriverPacks BASE to integrate the DriverPack MassStorage to your Windows_Home_Server\SVR_2003 folder

it will add the DriverPack MassStorage support to the 2k3 portion of your installation...
You probably need to integrate textmode drivers only.

If you create a SAD disc you should be able to update all of your drivers post install.

Should work just fine!

Re: Windows Home Server with Power Pack 1

null@example.com (temporalwar) — Sat, 02 Jan 2010 20:08:27 +0000

The install starts like Server 2008 ,and then finshes like Server 2003 R2
I had a machine running a AMD785+SB710 Chipset running 'AHCI'
the first part of the install worked great and then '7B" errors after the server 2003 part started
lucky for me, gigabyte lets you turn on a few ports to 'native' mode so I could load the F6 drivers and reboot and turn on AHCI again
=
I'm thinking we need just to figure out how to intergrate the drivers into the 'XP/Server03' part of the disk, server08 has alot of base driver support that doesnt need updates

Re: Windows Home Server with Power Pack 1

null@example.com (OverFlow) — Wed, 05 Aug 2009 03:06:25 +0000

Yeah I was able to download the eval version from MS...

http://www.microsoft.com/DOWNLOADS/deta … laylang=en

It does appear to be a standard 2k3 server layout for the OS... However the Boot.wim is definately the NT 6.x boot image.

So the solution must be a hybrid...
BASE for Slipstreaming PnP drivers
Vista Tool for slipstreaming the TextMode drivers...

Should be doable with existing DriverPacks software... But it will require both tools be run on the source.

Re: Windows Home Server with Power Pack 1

null@example.com (mr_smartepants) — Sun, 26 Jul 2009 12:49:14 +0000

Well I had a look at a borrowed WHS disc and it has a hybrid layout. It has a \sources\boot.wim for the PE just like Vista, but then as you pointed out it has a \svr_2003\i386 folder with all the files you'd expect from 2003 server.
Adding DriverPacks as method 2 shouldn't really be that difficult I would think since the files DriverPacks BASE modifies are right there.. Just point to the nested folder.
But textmode mass-storage might be completely different since it uses the boot.wim like Vista. And yet it has our typical dosnet.inf and txtsetup.sif files.
Hmmmm...

Re: Windows Home Server with Power Pack 1

null@example.com (OverFlow) — Fri, 24 Jul 2009 20:07:52 +0000

SBS is a bullet proof platform if correctly tweaked

That is what i like to run at home and for my small clients who need a server

Re: Windows Home Server with Power Pack 1

null@example.com (IvanHo) — Fri, 24 Jul 2009 19:08:59 +0000

I tested it on 5 years old Asus P5GD1 mobo with only 512 MB of RAM in a single DDR package, it was using only 195 MB of RAM in idle with no clients connected, and generaly was working flawlessly. So, good luck

Re: Windows Home Server with Power Pack 1

null@example.com (mr_smartepants) — Fri, 24 Jul 2009 18:59:41 +0000

I'm actually looking at buying an HP mediasmart WHS for my home so adding this functionality would be in my best interest soon.

Re: Windows Home Server with Power Pack 1

null@example.com (IvanHo) — Fri, 24 Jul 2009 16:41:38 +0000

Hi,
here is some more info:

http://social.microsoft.com/Forums/en-U … 173bb22471

"A point to note with WHS is that the basic install is based on Windows Server 2003 and does not support some motherboards that Windows XP or Windows Vista may support. This is through the drivers supplied within Windows Server 2003 do not support all the Motherboards (we) use for general PC's. If you watch the WHS install you will see it installs Windows Server 2003 (Small Business Server version) then overlays WHS components. If the motherboard requires drivers for the chipsets on the motherboard to enable access to devices beyond then these will need to be loaded once WHS is installed.
This is the same process for Windows XP or Vista, even though XP or Vista provide basic chipset support or drivers to see the Hardware or device within a PC install. This is highlighted within the Device manager by a yellow “?” mark(s) till the correct device driver(s) are loaded.
The point to note is if you are going to build your own WHS check that the motherboard can be used for Windows Server 2003 – Small Business Server. This will enable all devices to be seen by WHS at install and then load additional drivers to give full/enhanced operation of the device. This is more relevant with the new generation Motherboards produced over the last year which Windows Server 2003 do not know about Sata Drive chipsets........"

Best regards,
Ivan

Re: Windows Home Server with Power Pack 1

null@example.com (IvanHo) — Fri, 24 Jul 2009 08:37:55 +0000

Hi,
to help clarify my first post, here's the original unmodified directory structure from DVD.
At start one must point DP to i386, there is no other way known to me,
but then afterwards obviously something has to be done to make it boot correctly - but what?
That was my original question. And yes, perhaps I overreacted a bit...

Best regards,
Ivan

Re: Windows Home Server with Power Pack 1

null@example.com (OverFlow) — Fri, 24 Jul 2009 04:57:18 +0000

I also mistakenly thought it was a win NT 6.x platform... and googled it to discover i too was wrong...

NBD... You were wrong... it happens, I wouldn't have called it flame though

Welcome to our board IvanHo

It seems logical to support home server since we do advertise that we support Win NT 5.x x32 platform support...

Let's talk about it...

Re: Windows Home Server with Power Pack 1

null@example.com (mr_smartepants) — Fri, 24 Jul 2009 04:29:07 +0000

Doh! You're right, I was wrong.
My apologies to you.
Google & wikipedia are indeed trusted friends now.
It's possible that if the disc folder structure is different than 2003, that DriverPacks won't work. DriverPacks isn't advertised to work on Home Server.
I'll have to get ahold of an evaluation copy and see what the differences are. OverFlow would have to make the modifications to the code to support it though.

Re: Windows Home Server with Power Pack 1

null@example.com (IvanHo) — Thu, 23 Jul 2009 20:59:34 +0000

Hi, thank you or your prompt, but unfortunately incorrect answer.
Windows Home Server is based on Windows Server 2003.
It can very easily be checked, usually by Google, and an evaluation copy is available at Microsoft.
I appreciate your wish to... lets say help, but would appreciate even more an usable answer.
And by the way, it's not the first time from you, to flame on this and other forums...

Best regards,
Ivan

Re: Windows Home Server with Power Pack 1

null@example.com (mr_smartepants) — Thu, 23 Jul 2009 20:49:54 +0000

Your post doesn't even make sense. Win Home server is based on Vista/Server2008. RVMI won't work with that.

Windows Home Server with Power Pack 1

null@example.com (IvanHo) — Thu, 23 Jul 2009 19:50:43 +0000

Hi,
my problem is:
I modified original .iso with RVMI, adding post-SP2 hotfixes, tested it, all OK, boot and everything.
I added DP, and at boot DVD errors are: CDBOOT: coudn't find ntldr.

I presume that its because I386folder is under SVR_2003 folder, not in root, but to put it simple I don't know what and where to change to correct it.

Please advise.

Best regards,
Ivan