Recommended Posts

This app is great, hmmm if there is anything i could do to help, maybe beta test, help out with CD distibution.. Anything

No prob... when the time comes I may need some help in testing... I'll keep your name in the back of my mind. ;)

@livesoca - Most of what you said is being worked on. As far as an unattended instal via a program... If you have a Windows XP disk, in the XP AutoPatcher folder is Microsoft's program to make unattended installations. So maybe that can help you. :) Also, If I can figure out how to do it through the program, I'll probably make the ICF option and stuff like you suggested. :D

@livesoca Regarding the Windows XP Unattend Builder i accept the challenge and have started working on it now as i already had a base for this for something i was working on myself :) maybe this weekend i will get really stuck in and when complete i send to program authors for include in the builder or it could become a seperate program, either way it will be coded in Batch file and will work fully.

Also i am looking to organize a Windows 2000 AutoPatcher team of maybe 2-4 members if you or anybody else is interested i can send details of what is required and specific roles.

well we are looking for:

somebody who could work with the existing autopatcher sourcecode which is visual basic i believe so experience in visual basic is essential

somebody to research all the latest patches, updates and to totally maintain the list of updates and pass the information to the 1st person who programs it in. (ideally has broadband for all updates required to download)

somebody to keep watch over what is going on and keep contact with the Autopatcher XP crew, and oversees dispatch, and CD dispatch (if this is agreed upon) as well as general management.

the fourth person could help with either programming or research, although the watch keeper (person 3) would have the final say all team members would be totally equal, and if the 4th person had web design skills to make and update the website this would be very usefull, if not then an additional duty could be documentation and testing.

Jono

@livesoca Regarding the Windows XP Unattend Builder i accept the challenge and have started working on it now as i already had a base for this for something i was working on myself :) maybe this weekend i will get really stuck in and when complete i send to program authors for include in the builder or it could become a seperate program, either way it will be coded in Batch file and will work fully.

Also i am looking to organize a Windows 2000 AutoPatcher team of maybe 2-4 members if you or anybody else is interested i can send details of what is required and specific roles.

well we are looking for:

somebody who could work with the existing autopatcher sourcecode which is visual basic i believe so experience in visual basic is essential

somebody to research all the latest patches, updates and to totally maintain the list of updates and pass the information to the 1st person who programs it in. (ideally has broadband for all updates required to download)

somebody to keep watch over what is going on and keep contact with the Autopatcher XP crew, and oversees dispatch, and CD dispatch (if this is agreed upon) as well as general management.

the fourth person could help with either programming or research, although the watch keeper (person 3) would have the final say all team members would be totally equal, and if the 4th person had web design skills to make and update the website this would be very usefull, if not then an additional duty could be documentation and testing.

Jono

Jono... we're already talkin' to people about this. There will be one officially made by us. The VB end will be done by Raptor, the rest will be done by me and anyone willing to help (like the XP one was done). Dispatch and everything else will be done via me and the website. We registered autiopatcher.com because there will be other version (for 2000 and such). I'm currently working on it and it will be very nice (nothing like is there now). Please check with me on stuff like this first. ;)

Edited by FlishFun
you should document how to add whatever drivers on the page....

if need be i will help out with the web page and documentation on it..

Thanks... when the site is gettin' close to being up I may ask for some help on documentation of "How to do" certain things. :)

Jono

Jono... we're already talkin' to people about this. There will be one officially made by us. The VB end will be done by Raptor, the rest will be done by me and anyone willing to help (like the XP one was done). Dispatch and everything else will be done via me and the website. We registered autiopatcher.com because there will be other version (for 2000 and such). I'm currently working on it and it will be very nice (nothing like is there now). Please check with me on stuff like this first. ;)

i think you mean autopatcher.com :p and you should read your PM :D

Okay, thought I needed to post this again since some people (not all, just some) still don't seem to see what this thread is for. This is strictly for ideas for things that can be included in the Dec. Release. It's not to discuss other versions of the AP or anything like that. Please keep this on topic. You can discuss everthing else in the main AP thread here: Official AutoPatcher XP Thread

Thank you for all your help so far in ideas of what to include... there are many things here that I now think would be a good idea! :) Please keep up the good work! :D

@livesoca Regarding the Windows XP Unattend Builder i accept the challenge and have started working on it now as i already had a base for this for something i was working on myself :) maybe this weekend i will get really stuck in and when complete i send to program authors for include in the builder or it could become a seperate program, either way it will be coded in Batch file and will work fully.

Also i am looking to organize a Windows 2000 AutoPatcher team of maybe 2-4 members if you or anybody else is interested i can send details of what is required and specific roles.

well we are looking for:

somebody who could work with the existing autopatcher sourcecode which is visual basic i believe so experience in visual basic is essential

somebody to research all the latest patches, updates and to totally maintain the list of updates and pass the information to the 1st person who programs it in. (ideally has broadband for all updates required to download)

somebody to keep watch over what is going on and keep contact with the Autopatcher XP crew, and oversees dispatch, and CD dispatch (if this is agreed upon) as well as general management.

the fourth person could help with either programming or research, although the watch keeper (person 3) would have the final say all team members would be totally equal, and if the 4th person had web design skills to make and update the website this would be very usefull, if not then an additional duty could be documentation and testing.

Jono

erm actually, i never said anything about the source code... this is what i meant: you need a guy who has some knowledge in programming so he can understand how autopatcher works under the covers... that might or might not involve source code... the sure thing i that he will get a basic 'plan' of what AutoPatcher does under the interface... this way he can understand better what the group need to do...

/Raptor

erm actually, i never said anything about the source code... this is what i meant: you need a guy who has some knowledge in programming so he can understand how autopatcher works under the covers... that might or might not involve source code... the sure thing i that he will get a basic 'plan' of what AutoPatcher does under the interface... this way he can understand better what the group need to do...

/Raptor

Well, I've already talked to Jono about this... so we're fine. Also, I don't think we'll do the group thing... to many reasons/problems. I explained to Jono (and others) how it will be done. :)

Okay then... that's the last of this discussion here. lol Post the rest in the other thread please. :D

FlishFun, please stick to mainly Windows patches, tweaks, Java stuff, MSN stuff, and nothing more! You're bloating it :ninja:

It'd be great if you didn't put in drivers :sleep:

Um... who said Drivers? I didn't say drivers. lol :unsure: I didn't plan on bloating it... I think you have me confused with someone else. :p lol

Just adding my two cents to Reiterate that AutoPatcherXP needs to remain "clean" with ONLY "System Specific" improvements.

External softwares need to stay out......

I agree. Don't worry, I think you'll all be pleasantly surprised. :)

how about running a little reg file that removes all the entries of the hotfixes from add/remove programs?

i usually do that when i install updates, it's time consuming to sort through them when i'm trying to remove a program.

how about running a little reg file that removes all the entries of the hotfixes from add/remove programs?

i usually do that when i install updates, it's time consuming to sort through them when i'm trying to remove a program.

dunno about a reg file i use this after every install maybe it could be automated i never looked :(

Hotfix_Removal_Tool.exe

how about running a little reg file that removes all the entries of the hotfixes from add/remove programs?

i usually do that when i install updates, it's time consuming to sort through them when i'm trying to remove a program.

AutoPatcher has /noKBlog and other switches to do that I think.

how about running a little reg file that removes all the entries of the hotfixes from add/remove programs?

i usually do that when i install updates, it's time consuming to sort through them when i'm trying to remove a program.

AutoPatcher has /noKBlog and other switches to do that I think.

i think he means the "No backup" feature... cause thats what i think it does... not sure if he means logs...

/Raptor

For my 2 cents...

I would like to have a utility that would create the batch files for you. This way you can add whatever you want to the AutoPatcher. :woot: :woot:

Prompts for location, description, common switches, location in the AutoPatcherXP.dat file etc... :wacko: :wacko:

For my 2 cents...

I would like to have a utility that would create the batch files for you. This way you can add whatever you want to the AutoPatcher. :woot: :woot:

Prompts for location, description, common switches, location in the AutoPatcherXP.dat file etc... :wacko: :wacko:

Not sure if we can automate it fully (cause the database and batch files are seperate)... but it's a good idea and we'll see about it. :)

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

    • No registered users viewing this page.
  • Posts

    • Apple reluctantly forces strict new age checks on Texas users starting today by Paul Hill Apple will begin enforcing the Texas Age Assurance Law (SB 2420) following a recent court ruling that lifted an injunction on SB 2420. Starting June 4 (today), Apple will enforce strict age-verification and parental-consent rules for new Apple accounts created in Texas. This move will affect children under 18 who go to download apps or attempt to make in-app purchases. Apple previously expressed privacy concerns related to this law, but compliance is now mandatory for the company, nevertheless. Apple will use several APIs to follow the law. Principally, the Declared Age Range API will fetch the specific user age bracket (Under 13, 13-15, 16-17, or 18+) and a verification method. The Significant Change API (PermissionKit) will trigger a system dialog for parental consent if an app gets a major update or an age-rating shift. There is also a new property type in StoreKit that allows developers to automatically check when their app’s age rating has changed on a user’s device and then use the Significant Change API to request parental consent. Finally, App Store Server Notifications can be configured to tell developers when a parent revokes consent, blocking app launches. To ensure they are ready for these changes, developers must immediately use Apple’s sandbox testing environment to validate these APIs in their apps. For any developers out there finding this to be inconvenient, get used to it. Other regions, such as Utah, Louisiana, and Brazil, are looking at, or have implemented, similar rules.
    • They should show the onedrive recycle bin in a searchable manner and on app not just on the website
    • You looking at a phone or something? On my 4K HDR monitor it is frikking spectacular.
    • The Surface Pro 7+ already has a USB C port which can be used for everything you mentioned, except for eGPUs. Meanwhile, microsoft have gotten rid of ALL of the following that are present in the Surface Pro 7+:
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      230
    3. 3
      Skyfrog
      72
    4. 4
      FloatingFatMan
      60
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!