Recommended Posts

so far i have most of it working... im testing on a box later tonight (1~2 hours)

i'll give you all an update as soon as i confirm all is good...

thanks for all the beta testers interested!!

i'll have something for you all in the next hour or so!!

hit me up on IM!!

so far i have most of it working... im testing on a box later tonight (1~2 hours)

i'll give you all an update as soon as i confirm all is good...

thanks for all the beta testers interested!!

i'll have something for you all in the next hour or so!!

hit me up on IM!!

Shifty,

If you still need Beta Testers, I've got some time. Let me know.

BTW I don't do IM. :no:

so far the batch file is done, but the testing process is very annoying...

so far i have tried once and the "un-attended" part was far from it

and the XP keys that i have are not liked by the installer...

the key i had was invalid...

i am using a xp key generator for testing purposes so that i dont accdientally

have my key leaked or registered...

and NO you can not get that generator from me!! nor will i let anyone have any keys!!

i wish i had a xp key tester program...

oh well...

i'll be sending testers a batch file tonight for them to mess with.

sorry about all the delays...

between work, having the flu for 3 weeks and my girlfriend who thinks

i make sweet love to computer, its been super rough.

thanks for all your patience guys!!

so far the batch file is done, but the testing process is very annoying...

so far i have tried once and the "un-attended" part was far from it

and the XP keys that i have are not liked by the installer...

the key i had was invalid...

i had this same problem with unattended install and this fixed the issue.

Under [userData] in the winnt.sif put this:

ProductID="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

i got the product key issue fixed...

i generated about 23 keys and i figured

anyone woutld work.

unfortunately after reading the read me file, states

that a certain percentage of the generated keys will

be accepted by the installer.

i had to do some trial and error, but i got it though.

thanks nonametek for the tip though!!

i'll be sure to add it to the final guide!!

There are 4 basic types of licenses issued for RAR, these are:

A single computer usage license. The user purchases one license to use the RAR archiver on one computer.

A multiple usage license. The user purchases a number of usage licenses for use, by the purchaser, the purchaser's employees or accredited agents, on the same number of computers. The number of licenses in network environment must not be less than the maximum possible amount of simultaneous users.

A SITE usage license. The user purchases a single usage license, authorising the use of RAR, by the purchaser, the purchaser's employees or accredited agents, on an unlimited number of computers at the same physical site location. This site location would normally be defined as a single building, but could be considered to be a number of buildings within the same, general, geographical location, such as an industrial estate or small town.

A CORPORATE, NATIONAL or INTERNATIONAL usage license. The user purchases a single usage license, authorising the use of RAR, by the purchaser, the purchaser's employees or accredited agents, on an unlimited number of computers, regardless of location, but owned or under the control of the purchaser.

http://www.rarlabs.com/license.htm

probably no difference in the actual software.

HAHAHAHAH!!!!

its finished!!!

i have successfully installed windows xp w/ slipstreams of sp1a and decembers autopatcher!!!!

all the tester should contact me ASAP and i'll send then the zip file w/ the batch file and instructions!!

I just finished making my own WinXP Unattended CD, but I'm stuck as to what the code is in the winnt.sif file to run the AutoPatcher.exe :blink: Can anyone enlighten me on this? Can AutoPatcher run unattended before setting up the user's login? I'm soooooo close I can taste it. Please help me.

I just finished making my own WinXP Unattended CD, but I'm stuck as to what the code is in the winnt.sif file to run the AutoPatcher.exe :blink: Can anyone enlighten me on this? Can AutoPatcher run unattended before setting up the user's login? I'm soooooo close I can taste it. Please help me.

read this: https://www.neowin.net/forum/index.php?showtopic=110946&hl=

-----

i've been testing and tinkering with the beta, and i had to make a few changes to get it to work...but the copy in my hands now works flawlessly. i just have to talk to Shifty to get his approval on some of the changes i've made :) then more testing!

i've been testing and tinkering with the beta, and i had to make a few changes to get it to work...but the copy in my hands now works flawlessly. i just have to talk to Shifty to get his approval on some of the changes i've made :) then more testing!

I made my Unattended Manually, not the CD Maker Tool. Can you tell me this... Can AutoPatcher run unattended before setting up the user's login? Perhaps you can just give me a clue as to the command in the winnt.sif that runs the AutoPatcher\AutoPatcher.exe :whistle:

here's what happens...

when you do the unattended install, you have the option to skip the "welcome screen" (not the welcome screen where you logon, but the one where you set up users and such...)

on my unattended install, that's what i did, and had it automatically login as administrator, run APXP (before explorer loads), restart, and show the welcome screen. (the login one)

you'd then have to login as administrator to create an account for yourself, unless you wanted to use the "Administrator" account.

mind posting your winnt.sif? i'll tell you what you need to change.

here's what happens...

when you do the unattended install, you have the option to skip the "welcome screen" (not the welcome screen where you logon, but the one where you set up users and such...)

on my unattended install, that's what i did, and had it automatically login as administrator, run APXP (before explorer loads), restart, and show the welcome screen. (the login one)

you'd then have to login as administrator to create an account for yourself, unless you wanted to use the "Administrator" account.

mind posting your winnt.sif? i'll tell you what you need to change.

Okay, here it is (edited slightly)

;SetupMgrTag

[Data]

AutoPartition=0

MsDosInitiated="0"

UnattendedInstall="Yes"

[unattended]

UnattendMode=FullUnattended

OemSkipEula=Yes

OemPreinstall=No

TargetPath=\WINDOWS

[GuiUnattended]

AdminPassword=3e3b63bb83ad17fdf9393d97e7a1873c0bf12506d378347a19cee6b

EncryptedAdminPassword=Yes

OEMSkipRegional=1

TimeZone=4

OemSkipWelcome=1

[userData]

ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

FullName="DEFAULT"

OrgName=""

ComputerName=DEFAULT

[Display]

BitsPerPel=32

Xresolution=1024

YResolution=768

Vrefresh=85

[identification]

JoinWorkgroup=LAN

[Networking]

InstallDefaultComponents=Yes

[branding]

BrandIEUsingUnattended=Yes

[Proxy]

Proxy_Enable=0

Use_Same_Proxy=0

I really appreciate this! :cool:

Change:

OemPreinstall=Yes

at the end, add...

[GuiRunOnce]

"%systemdrive%\InstallAP.cmd"

now, on the root of the CD, you will need to create a folder called $OEM$, within that folder create a folder called $1, and inside that folder, you will need to create a batch file called InstallAP.cmd also in the $1 directory, you'll need to put the contents of your autopatcher inside a folder called whatever you want...when you extract AP, it is the folder that is in the same directory level as the autorun information...just take that folder and yeah...here's an example:

CDROOT\$OEM$\$1\AutoPatch <--that's where all my AP files are...

now here's my batch file:

%systemdrive%\AutoPatch\autopatcher.exe /noeula /unattend

the .CMD is important!!!! don't use .bat (this warning is from the unattended guide, i don't know what happens if you use a bat.)

Edited by cpugeniusmv
i'd also recommend editing that administrator password out of your post, there are ways of decrypting that :)

------

everyone else: keep waiting for the CD-maker!! it's super cool.

Thanks.

BTW I did edit the admin password before I posted it. :yes:

I'll give this a shot and let you know.

Thanks again

i made some changes to my original post after doing a little more reading into the unattended guide some more....

apparently something important :)

Thanks for the heads up :yes:

I just made a minor corection (autologin) and this.

Time to burn another disc and try again.

I'm getting really close now :woot:

well, i just got back from work and after reading some of these posts, i think i may have sent out some wrong

commands in the batch... i just re-did mine and i had no problems

as soon as the testers get online i shall collaborate w/ them and hammer this out by monday night (hopefully)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Unofficial script lets you install unreleased Windows 11 features without Microsoft Account by Sayan Sen Microsoft has been steadily evolving the Windows Insider Program over the years, introducing new channels and testing paths that allow enthusiasts to experience upcoming and yet-to-be-released Windows features (some interesting hidden ones too) before they reach the public. However, one long-standing requirement has remained largely unchanged as users are generally expected to enroll in the Program and with a Microsoft account. That's where a third-party tool called "OfflineInsiderEnroll" can help. OfflineInsiderEnroll is said to be a lightweight script that enables access to Windows Insider Program builds on systems that are not signed in with a Microsoft account. Essentially the tool configures the necessary Insider settings locally and hence allows users to select and switch between available preview channels while continuing to receive builds through the normal Windows Update channel. If you are wondering how it manages to do so, it is made possible by a Registry value known as TestFlags. When configured to"0x20", Windows stops communicating with Microsoft's online Insider enrollment services thus preventing locally configured Insider settings from being overwritten. This allows the script to apply its own channel configuration directly through the Registry as Windows Update does not verify whether a device has been officially enrolled in the Insider Program or not. Previously the utility has had already supported the traditional Insider branches including Dev, Beta, and Release Preview. However following Microsoft’s recent restructuring of its preview channels, the script has now been updated. The latest OfflineInsiderEnroll version, 2.6.6, adds support for the newly introduced Insider channel lineup. As such, users can now choose from several Experimental channels in addition to Beta and Release Preview options. The update also retains tools for refreshing the Insider cache, resetting Insider settings, and completely stopping Insider enrollment when needed. Keep in mind though that will need elevated privileges when running the script (run as Admin). You can get the latest version of OfflineInsiderEnroll from this page on its official GitHub repo.
    • The "Classic" Outlook has done that for a few years as well. The option to even change that is really hidden away too... It really shouldn't be hard to respect user defaults. Sadly we are the product now, not Outlook. To change in the Classic Outlook: File > Options > Advanced > change "Open hyperlinks from Outlook in"
    • Get yo ass to space
    • Vivaldi 8.0.4033.44 is out.
    • For the purpose that it was built for, it’s a great machine. It’s okay to own multiple machines, it’s okay for machines to be different. If every computer was the same, they’d be boring af.
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      PsYcHoKiLLa
      249
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!