WinNTSetup

Posted 14 April 2009 - 09:43 AM

Hi at all,

I had a lot time the last weeks and were trying to setup Windows XP x64 through LiveXP.

It seems the best way is to imitate the winnt32.exe Process. So I wrote this small program called WinNTSetup.

Features:
Install Windows 2k/XP/2003 x86/x64
patch uxtheme to allow unsigned Themes
Chooseable driveletter for the new Windowsinstallation *New
Install Windows also if nlite has remove winnt32.exe *New
Integrate Drivers: normal PNP and Textmode Drivers also *New

Changelog:

WinNTSetup_JFX.script is now available in project


Version 1.4.2

• fix problem with windows server editions
• MiniNT Mode (XP,2003) Systemdriver letter assignment is now calculated instead of using listed ones in Mounted devices key, this should hopefully address an issue with default LiveXP project
• New hotkeys: Save Settingfile Ctrl + S, Load Settingfile Ctrl + L
• Optional Using BootIce for MBR / PBR Update
• Partition indicator icons should now work with Partition on other drives than drive 0

Version 1.4.2.1

• small fixes (UnUpx)

Version 1.4.3

• fixed bug in Patch engine
• fixed bugs in Settingfile
• new: detection of some OEM Manufacturers
• fixed bug with FAT32 partitions (Thanks adric )
• updated BOOTICE to v0.73

Version 1.5

• fixed bug in dosnet.inf parsing
• fixed bug in recursive listing of drivers in winnt.sif
• a lot of gui fixes
• theoretical it should support Windows NT.3x NT.4x now
• fully functional x64 version (you will need x64 bootsect.exe or bootice + wow64 emulator)
• updated MSSTMake 10.3.30.1 http://forum.oszone....ead-117423.html
• updated BOOTICE to v0.78

WinNTSetup_x86_x64_v15.7z

Big Thanks to Mr. dUSHA for making x64 version of his famous MSSTMake.exe tool

Required files: expand.exe, reg.exe, MSSTMake.exe

bootsect.exe or bootice.exe




For VMWare testers of MassStorge integration : VmwareDrivers

• Back to top

Posted 14 April 2009 - 10:43 AM

This is nice, thanks for the program.

• Back to top

Posted 14 April 2009 - 10:52 AM

Yep, nice.

Thanks for sharing it.

jaclaz

• Back to top

Posted 05 May 2009 - 08:29 AM

• Back to top

Posted 05 May 2009 - 08:58 AM

yummy yummy

Thank you a lot


Edit:
Being an obvious xp64 fun around , i believe this is a "must" utility on a PE.
I made a pretty script now.
Sady i dont have VT support or empty hd (or partition) to make a quick test, but will do in couple of days and have good feeling to add it to LiveXP project.
Here is the script, I hope you like

• Back to top

Posted 05 May 2009 - 04:57 PM

Thanks Lancelot,

this is a nice script, I really like it. To see it in the LiveXP project would be cool.

I just get a Windows 2000 CD and will make some test if this works also.

The focus for the next version will be integration of MassStorge drivers. But this will take some time.

By the way maybe someone could check the text in the GUI, since my english isn't really good.

• Back to top

Posted 05 May 2009 - 05:24 PM

MassStorge drivers for especially x64, i get delighted

Sadly i dont know (well not yet google-fu) a massStorage x64 pack, i hope integrating ready (fixed) mass storage driver wont have trouble with your utility. Well i am not very good about driver facts, need to read more. All i know is hardest test is my mob

I just made a test on vmware to install xpsp2tr to E: mounted drive (C: extendedfat32, D: primaryntfs, E: active ntfs) with C: setting . Everything worked fine.
Only a minnnnor thing happened, xp setup found and installed lan but required my input (as usual i wrote WORKGROUP ) but as far as i remember it was written default WORKGROUP (box was empty) (maybe my mind plays with me or maybe this is xptrsetting or malfunction). Next test will be with xp64 but need to wait a support from my friend.

I am glad you like the script, there is a minnnnor quicklaunch icon problem which i couldnt find the reason, still searching, nothing serious, just informing .

CU soon


Edit:
Script Fixed and updated , next xp64

• Back to top

Posted 05 May 2009 - 06:04 PM

Well i thought more of a select-and-onthefly-integration of the needed mass storage driver for the board where it will be installed.

I'm currently doesn't know much about mass storage integration, I will at first try to reproduce the changes nlite would do and try to understand it.

Already integrated mass storage driver should work fine with it.

Im not sure about the WORKGROUP thing, it should not change this setting. May have a look at $Bootdrive$\$WIN_NT$.~BT\WINNT.SIF if there is an entry like this :

[Identification]

JoinWorkgroup=WORKGROUP

• Back to top

Posted 05 May 2009 - 06:05 PM

Hi JFX,
It is very necessary and useful utility
But on WinXP SP3 RUS there was such problem
Look here


PS
You use the utility bootsect.exe from WAIK from MS in your program. This infringement of the license for use bootsect.exe

• Back to top

Posted 05 May 2009 - 06:24 PM

Hy olegpov,

I will check the fontproblem, are there only this 2 occurs?

About the integrated bootsect.exe and expand.exe I haven't think about this would be a problem.

Well I will remove this files but to sad this will make it pretty useless for people who haven't the network connection to download the hole WAIK.

• Back to top

Posted 05 May 2009 - 06:30 PM

• Back to top

Posted 05 May 2009 - 06:35 PM

You use the utility bootsect.exe from WAIK from MS in your program. This infringement of the license for use bootsect.exe

To have (legally) bootsect.bin from your source cd, you can extract it from spcmdcon.sys like this:

Set,%in%,%source_win%\SPCMDCON.SYS

Set,%out%,<path>\bootsect.bin

Echo,&#34;Extracting %out% from %in%&#34;

ShellExecuteEx,Hide,%ProjectTemp%\bootExt.exe,&#34;#$q-I&#58;%in%#$q #$q-O&#58;%out%#$q&#34;

bootExt.exe is written by me and has no distribution restrictions.
 bootExt.7z   21.88KB   1019 downloads

Good idea / realization.

The small (? ) issues with Cyrillic (Chinese, Japanese, ... ... ) can be solved!

Peter

• Back to top

Posted 05 May 2009 - 06:45 PM

• Back to top

Posted 05 May 2009 - 06:47 PM

Thanks Peter,

but the required file is bootsect.exe version 6.0.6001.18000 or higher.

well there is also the possibility the have it from Vista Sp1/Server2008/Windows7 DVD or the Vista SP1/SP2 but this would be also a big download.

I should read more carefully next time!

But here we have:

bootsect.exe modifies bootsect.bin

If you can give me bootsect.bin "Before" and "After" the modification propably can be included as a bootExt option.

Peter

• Back to top

Posted 05 May 2009 - 07:09 PM

• Back to top

Posted 05 May 2009 - 07:15 PM

• Back to top

Posted 05 May 2009 - 07:26 PM

Please have a look here: http://neosmart.net/...or-not-the-mbr/

That has been the "source" for my previous post.

Is that wrong?

Peter

The old bootsect.exe couldn't update the MBR but since the Vista Sp1 Version it have the /mbr option.

For creation of $WIN_NT$.~BT\bootsect.dat I use pure autoit code but this has only read support to the MBR / PBR.

maybe MbrFix will be the solution

Ok, Im tired cu tomorrow


John

• Back to top

Posted 06 May 2009 - 10:40 AM

I just updated it, bootsect.exe is now removed. Problem with RUS XP Version should be fixed.

To use it grab bootsect.exe from inside the boot - folder of Vista Sp1/Server2008/Windows7 DVD and place it the same folder as WinNTSetup (or the current workingdirector or inside the PATH enviroment) .

Using MbrFix or MbrWiz will not be that easy, let's find a small download possibility for bootsect.exe.

• Back to top

Posted 06 May 2009 - 11:04 AM

Hi JFX

for now, can we inject LSI logic drivers for the ones who test with vmware6.5
i guess vmware6.5 selects LSI logic drivers as default which made xp64 test failure with my friend blue_life.
(i pmed him to change setting of vmware from lsi logic to bus logic for test, but others may fail too, so many vmware 6.5 user around. I am waiting 2nd result )
http://img27.imagesh...791/hatasls.png

bootsect.exe solution you offer is a temporary solution i believe,
For now if not found i guess better to pop up a message sth like "bootsect.exe can not be found, please get it from Vista Sp1 or later cd and put it in the same directory, or make drive bootable yourself ", for now i guess better to focus on driver injection

• Back to top

Posted 06 May 2009 - 11:23 AM

Hi Lancelot,

Yes i will change the test message for the missing file.

About the bootsect.exe I found other programs they include older versions of it. I will contact them if they update it to a newer version so we could have a smallsize download option.

for now i guess better to focus on driver injection

Yep

• Back to top

Posted 06 May 2009 - 12:36 PM

JFX,

not sure (and not like) about your solution for bootsect.exe
(I believe it should be an option when there is no alternate, and there are around)
anyway, when time comes, besides bootsect.exe you can put support to others .
Having options are always nice (Lancelot loves options )

For now, we dont have anymore legal issues which is good for asking anyone to test
just if you are a vmware user change lsi logic to bus logic (ps: still waiting for test result)


and for driver injection, we found our test routine :), injecting driver for xp64 installation for lsi logic , looking forward to it.

script updated
http://lancelot.winb...NTSetup_JFX.rar


ps: in a couple of days i may/maynot be away for a while, job issues .

Cu soon.

• Back to top

Posted 06 May 2009 - 04:19 PM

Thanks for updating script

Well Ok I make some tests,

MbrFix could be used to update the MBR (Master Boot Record)

MbrFix /drive <num> fixmbr /yes

But how about the PBR (Partition Boot Record)?

MbrFix /drive <num> /partition <num> fixbootsector <os> /yes

Does "<os>" only accept Win98 ?

Has anyone a good solution to update the PBR that it's load NTLDR?

For The MassStorge Interation I played a bit with MSSTMAKE and the lsi logic driver. It works fine with TEXTMODE and GUIMODE.
The one needed thing seems to be of also interate the *.inf,*.cat files and let Windows Setup install the driver at the Hardware detection state of GUIMODE.

Maybe olegpov can help us there


John

• Back to top

Posted 06 May 2009 - 05:00 PM

• Back to top

Posted 07 May 2009 - 06:04 AM

Good news,

xp64 setup perfectly on vmware605 .

But i am not sure how to do with vmware 650, seems to me my friend failed and dont have time to find the reason (also he reported he failed installing xp32 with usual method by using LiveXP). And i cant find how he failed from here too (-time intersect - time available - i have 605 for a while .....issues ).

Here is fernando's gathered packages. For a looong while he updates some set of drivers regularly with making fixes if reported (includes x64).
These are not dps packages, but a nice point on internet to gather 2 popular manufacturer drivers .
http://www.msfn.org/...ve-t107504.html
http://www.msfn.org/...howtopic=107504

mostly xp32 have great sources on internet for integrating new drivers, DPs team do a great job out there. I can integrate drivers (with various nice utilities) on livexp into a untouched xp32 on hd and than use JFX's tool which will speeed up things pretty good.

But for xp/2k3-x64 , this is what excites me more about JFX tool . I need to learn more driver integration for xp/2k3-x64 (time&sources i have slows me down)

@olegpov
forum.oszone.net have a new member, With Lancelot not available, remembering Peter calling me Lancelote in my first days, now oszone have Lancelote .
I havent (cant check quickly) if "Fake-Setup Advanced" works for xp64 . Yep all my mistake not to buy non supported vt cpu (ahh if i kneww these would happen) long time ago .

ps: script updated 2 times yesterday with line fix.

cu

• Back to top

Posted 07 May 2009 - 01:41 PM

Hy Guy's

I learn me lession, about playing around with MBR/PBR, the hard way.

Fixboot works only in the recovery console of 2k/XP, dsfo/dsfi could work, but i just have seen how much damage these powerfull tools can do.

When MbrFix will be updated to support more OS Versions it could replace bootsect.exe.

Good news about driver integration, I had success with MSSTmake and the LSI Adapter for XPx64 in Vmware 6.5.2.

Copying the Driverfolder(s) to Installationdrive and use the OemPnPDriversPath of winnt.sif seems also to be an easy and working solution.

Currently I have not much time but I think next week i have a testversion ready.

Cu soon

John

• Back to top