Recommended Posts

How to use autopatcher, where do i start? :)

Firstly, does it matter which autopatcher release i apply to my machine? Does the newest pack contain all the previous patches or do i have to download all indivitual packages and install the one by one? How do i know where to start from?

I couldnt find any real information about this process and i dont want to screw up my computer(s) on the first try...

Thanks in advance!

EDIT: i forgot the tag...

Link to comment
https://www.neowin.net/forum/topic/317168-general-first-time-autopatcher/
Share on other sites

Hi!

First, you have to download the AutoPatcher you want (the Full or the Lite). You just have to download the latest version 8every month, because it includes all the previous hotfixes.

The next step is running the AutoPatcher_XP_Apr2005_xxxx_.exe (were xxxx is Full or Lite). It will be created a shortcut in your desktop, and then you just have to double-click it.

Just select the things you want to install and click "Update".

And that's almost everyting...

(There is a tutorial in Portuguese (made with my help), and there is a Google's translation here...)

Just to be sure, do you mean that i need to download and install ALL the released packages? OR can i just download and install the latest one?

Example, ive got february, march and april packages, do i need to install all of these or just the april (latest)?

585880747[/snapback]

No, i mean you just have to install the latest version (April). You may delete the old packages, because they aren't needed anymore. :)

No, i mean you just have to install the latest version (April). You may delete the old packages, because they aren't needed anymore.  :)

585880772[/snapback]

Hi Gandolas,

Maybe it's time to make a manual.... :)

Or a book in the context of the series "..for dummies". Now it's time to make "Autopatcher for dummies" whould that be something? :rofl:

Just kidd'n... I think it would be nice for people when they have something read about it. You as Autopatcher-teammember should do that... :whistle:

:ninja: Pascal B :ninja:

Hi Gandolas,

Maybe it's time to make a manual.... :)

Or a book in the context of the series "..for dummies".  Now it's time to make "Autopatcher for dummies" whould that be something? :rofl:

Just kidd'n... I think it would be nice for people when they have something read about it. You as Autopatcher-teammember should do that... :whistle:

585880930[/snapback]

Hi Pacal!

I've also made a Portuguese FAQ... Maybe it's time to try to translate it to English and time to make a "How To Install AutoPatcher"...

Pascal, carrying out an AutoPatcher release usually makes you a team member candidate. That means you're quite close yourself...

Oh, this goes just as a note: The AutoPatcher 6.0 UI will have enough window-space for a small FAQ (probably accessible via the sidebar).

Oh, this goes just as a note: The AutoPatcher 6.0 UI will have enough window-space for a small FAQ (probably accessible via the sidebar).

585881125[/snapback]

That sounds like music in my ears.....to do some more to "our" customers....Raptor.

:ninja: Pascal B :ninja:

Pascal, carrying out an AutoPatcher release usually makes you a team member candidate. That means you're quite close yourself...

Oh, this goes just as a note: The AutoPatcher 6.0 UI will have enough window-space for a small FAQ (probably accessible via the sidebar).

585881125[/snapback]

gimme english version of FAQ and i'll port it to Lithuanian

Here's a quick port from Gandolas' FAQ.

585881629[/snapback]

good work :D

i think you forgot to mention making a cd though !

it may also be helpful if we had a copy explaining how to create modules, and one for translators explaining which fields need changing.

i also think it would be good if translators made two copies of releases, one with the names and descriptions left in english, for those who mainly speak english but have a foreign copy of windows.

And we should have a copy of AP with english only files missing, as a quick small download for translators to use as a base for tanslation without downloading the large english release.

Here's a quick port from Gandolas' FAQ.

585881629[/snapback]

It's much better that my poor little and colorless FAQ... :blush: You really did a great job (as usual)! :happy:

i also think it would be good if translators made two copies of releases, one with the names and descriptions left in english, for those who mainly speak english but have a foreign copy of windows.

And we should have a copy of AP with english only files missing, as a quick small download for translators to use as a base for tanslation without downloading the large english release.

585881758[/snapback]

I don't think it will be helpfull for the Portugueses versions...

Yes, i agree with that, having a "Translation pack", with the AP structure, but without the enu files... If raptor agrees, i can make one.. or even you Blaze...

good work  :D

i think you forgot to mention making a cd though !

it may also be helpful if we had a copy explaining how to create modules, and one for translators explaining which fields need changing.

i also think it would be good if translators made two copies of releases, one with the names and descriptions left in english, for those who mainly speak english but have a foreign copy of windows.

And we should have a copy of AP with english only files missing, as a quick small download for translators to use as a base for tanslation without downloading the large english release.

585881758[/snapback]

1. The questions answered in the FAQ were initially written by gandolas. I just rephrased some things so they make sense.

2. The trouble is that I see things from a developer's point of view. I believe people like you should create these manuals/guides/faqs. For instance, translators can write a faq based on their experience. And they will propably cover parts which I wouldn't.

3. That's up to the translators to decide. In some countries, English is a (secondary) official language, so it would be a good thing to have two releases. In others, English is rarely (or never) used, so there's no real point.

4. I like the common-base idea. If we keep a nice list of things which apply to all languages, then why not!

/Raptor

2. The trouble is that I see things from a developer's point of view. I believe people like you should create these manuals/guides/faqs. For instance, translators can write a faq based on their experience. And they will propably cover parts which I wouldn't.

3. That's up to the translators to decide. In some countries, English is a (secondary) official language, so it would be a good thing to have two releases. In others, English is rarely (or never) used, so there's no real point.

/Raptor

585882527[/snapback]

That's true Raptor, developers see these kind of things in a different point of view. After my work behind the scenes, I started with user support. That's the kind of work I like to do. Helping them, giving the support they need and looking for. Making user manuals and installation manuals, could be used be person who never seen a Personal Computer. That's my personal point of view.

I think that a manual will depend on the need of the people. If you have a lot of questions then it's useful to spend time making it. In a FAQ you can't always find what you want to know. New users to Autopatcher can't use it.

Personally, I think that I would be a great opportunity to build it in Autopachter. Either in the program itself or as a module.

:ninja: Pascal B :ninja:

so true, we find most things pretty self explanatory and beginner can't even figure out what they mean, it would be best if we could get list of questions from them, this way FAQ would be built best

585884991[/snapback]

Exactly!!! First things first, you need to explain what Autopatcher is, what is does and how you can use it. If you do this in a very easy way, 95% off all question are coverd. That's first hand experience .........

I will spend time make a nice one!

:ninja: Pascal B :ninja:

1. The questions answered in the FAQ were initially written by gandolas. I just rephrased some things so they make sense.

2. The trouble is that I see things from a developer's point of view. I believe people like you should create these manuals/guides/faqs. For instance, translators can write a faq based on their experience. And they will propably cover parts which I wouldn't.

3. That's up to the translators to decide. In some countries, English is a (secondary) official language, so it would be a good thing to have two releases. In others, English is rarely (or never) used, so there's no real point.

4. I like the common-base idea. If we keep a nice list of things which apply to all languages, then why not!

585882527[/snapback]

1 & 2. I've made the FAQ based in the questions adressed to me, and some that i thought they could be made.

3. Yes, we don't use English, only Portuguese, so no need for the second release.

4. I can do that, after doing the versions off this month... What do you think Raptor?

is there a way you could it so we could choose languages like we can in nLite?

it opens some box says hello world! and there's drop down box with list of languages, you choose one, menu insta changes into that language and setup continues?

First, you have to download the AutoPatcher you want (the Full or the Lite). You just have to download the latest version 8every month, because it includes all the previous hotfixes.

From what I read, there are 2 versions for XP. One for SP1 and one for SP2. :huh:

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

    • No registered users viewing this page.
  • Posts

    • Absolutely NOBODY has suggested such a conclusion. I am affirming the sober reality check that AV2's overall market adoption will take longer than AV1's adoption rate -- which, by the way, is the whole point of the article! While PCI-SIG is productive (on paper), other WGs have created all sorts of confusing progress plans that consumers have tuned-out of their improvements... HTML/W3C, USB, HDMI, BT, WIFI (ieee802.11) as a few other groups where spec naming conventions, split progress paths, overlapping ambitions... I'm not critiquing the AV specs group; I'm simply affirming that adoption for AV2 faces headwinds beyond the macroeconomics of it all.
    • Segra 1.5.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.5.2 changelog: Settings: Added an Airplane Mode that hides account, login, and upload features. Storage: Added a button to migrate videos into the recording path after changing it. Import: Added auto-scroll and a highlight pulse to videos right after importing. Recording: Added graceful handling of low disk space and output failures, finalizing files safely with clear errors. Recording: Added a guard blocking recording when any drive exceeds 99% full. OBS: Removed the download timeout to support users with slow internet. Clips: Fixed an error modal incorrectly appearing when clip creation was cancelled. Settings: Fixed the content folder path not refreshing in the UI after changes. Updates: Improved error handling for multiple simultaneous update checks. Stability: Fixed a WebSocket reconnect loop that ran while the window was backgrounded. Dependencies: Updated project dependencies. Maintenance: Removed dead code, reduced duplication, and fixed several latent bugs. Download: Segra 1.5.2 | 73.1 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • No thanks! WebView trash is unacceptable. I only use software that's native.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      69
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!