WinNTSetup
#26
Posted 07 May 2009 - 02:07 PM
well i am pretty busy for now too, it will be nice to test next week.
Cu
#27
Posted 12 May 2009 - 07:00 AM
For driver integration select a folder (which can have also subfolders) with the driverfiles.
Let's hope it works, I only tested it with the VMWare LSI Logic driver
#28
Posted 18 May 2009 - 08:35 AM
OemPnPDriversPath was only been working with subfolders. Was the dirverfolder selected direct then could windows setup not find the driver at hardware detection stage.
Fixed the Buttons for winnt.sif and driver folders, they wasn't working at all.
#29
Posted 19 May 2009 - 08:52 AM
#30
Posted 19 May 2009 - 12:32 PM
Your welcomeThanks @JFX.. Very good.
@All I need some feedback if every think is working correctly, I only have one 64Bit PC (and Vmware) to test it.
#31
Posted 19 May 2009 - 01:56 PM
/Turkish
JFX gerçekten çok başarılı bir program. Tekrardan teşekkürler.
Wmware 6.5 sistemi fazla kasıyordu ve eski sürüme geri döndüm malesef. (Wmware 6.0)
Ama programı denemek uğruna tekrar 6.5 kuracağım. Sonra tekrar kaldıracağım tabi.
Bu arada programda ufak bir soruna rastladım. Sistemimde şuanda çok fazla bölüm var ve boot sürücü hatalı çıkıyor.
picture: http://f.imagehost.o...157/sshot-1.png
Budaki ufak sorunu çözesen fena olmaz.
"CODE REMOVED" due to respect to author's not opensource project (again sorry) --> Required Fix already done with newer versions of winntsetup
#32
Posted 19 May 2009 - 02:01 PM
/English
JFX really very succesful utility, thanks again.
Wmware 6.5 was too much for me so i return back to older version. (Wmware 6.0)
To test WinNTSetup i will reinstall v6.5
I guess i found a small problem, currently system have too many sections and boot drive fails
"picture"
i guess problem is here
"code"
"maybe sth like that"
@Jacklaz
I dont have right to edit Blue Life post like I used to do with saydin77's posts, yep i know my limits, further is up to you.
#33
Posted 19 May 2009 - 02:39 PM
I will take a look at the code.
Did it gives an error message or returns the _FindActivePrimary Function a wrong drive letter?
#34
Posted 19 May 2009 - 04:30 PM
/Turkish
Herangi bir hata mesajı felan gelmiyor. Sistemde 10 dan fazla bölüm olursa böyle bir sorun çıkıyor.
Mesela 3 hdd var ve bölümlerinin toplam sayısı 10 geçiyor diyelim.
O zaman program doğru boot sürücüsünü göstermiyor.
Wmware 6.5.1 ile XP X64 denemesinde herangi bir sorun çıkmadı. Tekrardan teşekkürler JFX........
#35
Posted 19 May 2009 - 04:34 PM
no error message, When there is more than 10 partition , this happens. [Lancelot add: (H: on picture is extended )]
Example: there is 3 hdd and total number of partitions exceeds 10, than
@JFX
waiting for 1.2.2 to upload
#36
Posted 19 May 2009 - 05:03 PM
Ok, I use your code, think the ExitLoop will solve the problem.
Before I add it to 1 post let me know it works
#37
Posted 19 May 2009 - 05:33 PM
@JFX@Blue Life
I will take a look at the code.
Did it gives an error message or returns the _FindActivePrimary Function a wrong drive letter?
WinNTSetup.exe is interesting for Install of XP.
The difference with USB_XP_Setup.exe is that you always copy the complete XP Source to folder $WIN_NT$.~LS on the Install Drive.
In USB_XP_Setup.exe the XP Source is only copied to folder on the Install Drive, when the XP Source is not located on USB-stick or on partition 1 of ANY Harddisk.
This saves some copy time, but requires to take more care to ensure that the XP Source is found during XP setup.
In general, things are less complicated when booting occurs always from the Install Drive.
This ensures that the XP bootfiles NTLDR, NTDETECT.COM and boot.ini are made on the Install Drive, which might be preferred.
BTS DriverPacks integrated in the XP Source are not yet supported, but may be you will add this to your program.
From the discussion it seems to me that the source code is public.
If so, can you add the source to the attachment, then we also can have a look at it.
#38
Posted 20 May 2009 - 06:33 AM
@Blue Life
Ok, I use your code, think the ExitLoop will solve the problem.
Before I add it to 1 post let me know it works
No problem @JFX. Thanks...
#39
Posted 20 May 2009 - 07:56 AM
Yes copying the entired folder was the easiest way to get the progessbar running.The difference with USB_XP_Setup.exe is that you always copy the complete XP Source to folder $WIN_NT$.~LS on the Install Drive.
In USB_XP_Setup.exe the XP Source is only copied to folder on the Install Drive, when the XP Source is not located on USB-stick or on partition 1 of ANY Harddisk.
This saves some copy time, but requires to take more care to ensure that the XP Source is found during XP setup.
If BTS DriberPacks is allready integrated it should work. Decompressing the packs to a folder and select this one as driverfolder may work also.BTS DriverPacks integrated in the XP Source are not yet supported, but may be you will add this to your program.
No actually is not!From the discussion it seems to me that the source code is public.
If so, can you add the source to the attachment, then we also can have a look at it.
I'm not so happy to see what has happend here. As other authors of closed source I don't like see my code reversed.
The only protection is the Autoit EULA, which seems a very week one.
But since I get a improvement, I think ignore it is the best reagtion.
Ok I add it to the 1st post.No problem @JFX. Thanks...
#40
Posted 20 May 2009 - 11:00 AM
ps: @JFX: can you put above line to post 1
#41
Posted 20 May 2009 - 07:02 PM
The OEM folder, where the BTS DriverPacks reside, is NOT copied to the Root of the Install Drive.If BTS DriberPacks is allready integrated it should work.
http://driverpacks.net/DriverPacks/
WinNTSetup.exe should take care of copying the OEM folder if present, otherwise DriverPacks don't work.
#42
Posted 22 May 2009 - 02:40 PM
Thanks, you right it was no copying the OEM folder only the $OEM$ one.The OEM folder, where the BTS DriverPacks reside, is NOT copied to the Root of the Install Drive.
http://driverpacks.net/DriverPacks/
WinNTSetup.exe should take care of copying the OEM folder if present, otherwise DriverPacks don't work.
Ok, here comes a new testversion which fixed this and has a new option to run DriverPacks Base between copying source files and creation of bootfolder.
DriverPacks Base has to be unzip to a writeable location. DPs_BASE.ini will be update with location of windows sourcefiles and integration method.
Just select DriverPacks you like an push the Slipstream button.
#43
Posted 25 May 2009 - 08:49 AM
Another idea:
If winnt.sif file is present in I386 folder, it would be handy if this winnt.sif file was recognised and auto used as the default winnt.sif which could then be overruled if desired by selecting another winnt.sif file.
#44
Posted 25 May 2009 - 09:15 AM
Yep, good idea, I will add this to the next versionAnother idea:
If winnt.sif file is present in I386 folder, it would be handy if this winnt.sif file was recognised and auto used as the default winnt.sif which could then be overruled if desired by selecting another winnt.sif file.
#45
Posted 30 May 2009 - 11:29 AM
#46
Posted 11 July 2009 - 01:43 PM
Changes:
- There is now a little Tweaks button for Usercreation and some Registry tweaks.
- Windows 9x Support is gone since is now a Unicode App.
- The Add Drivers function will now disable Build-In nVidia Display Drivers to allow unsigned ones during Setup.
Hope nobody sees a problem with this, or want someone use the forceware drivers from year 2001?
Usercreation should be language independent, but I appreciate some feedback at this point
About bootsect.exe, I hope nobody feels ignored by me but even if there were good solutions I don't like to replace a safe solution with a possible risky thing. Also Version 2 will need a lot more files from Vista/Seven.
#47
Posted 12 July 2009 - 12:25 PM
I intend to test language independent usercreation but I guess found another bugy. You forgot to set partition active
ps: bootsect.exe 6.1.7100.0
Will test language independency when i find time
CU
#48
Posted 12 July 2009 - 01:11 PM
Yeah, bootsect.exe can't do this and I never really liked to touch the mbr, maybe there is no go without mbrfix, I will see.You forgot to set partition active
But something else can you temporary take WinNTSetup.script down from LiveXP Project? I've think there is a Big Bad Bug in the driver integration wich can give a lot of users an BSOD instead of the welcome site.
I'm really sorry for everyone who has experienced this problem.
Currently I've not much time, but I hope next week I can release somethink stable.
CU
#49
Posted 12 July 2009 - 05:02 PM
Besides, whatabout a checkbox for "Select location of BootDrive". So user who likes to use winnt setup make required changes with "bootsect.exe" (maybe +mbrfix) leave the checkbox enabled (default enabled), others make required mbr operations themselves. (ps: A checkbox is more easy than deleting bootsect.exe on folder first )I never really liked to touch the mbr
DoneWinNTSetup.script down from LiveXP Project?
waiting for next release
#50
Posted 14 July 2009 - 08:34 AM
http://img190.images...ntsetuptest.gif
an "autologon" checkbox would be nice on tweaks
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users