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

    • What would be the point wasting time, money and resource testing EOL operating systems?
    • expected when they force you by having to use TPM and secure boot for anti cheat crap, and lazy developers only test on windows 11.
    • The fact I need to use "Show more" like 99% of the time is so annoying. Or why I have 7-zip under 3 submenus when it could be in top. And Microslop keeps saying how they'll improve Start and I've not seen ANY improvement yet. In MONTHS. WTF?! I'll believe any of it when they actually deliver anything.
    • LosslessCut 3.69 by Razvan Serea LosslessCut aims to be the ultimate cross platform FFmpeg GUI for extremely fast and lossless operations on video, audio, subtitle and other related media files. The main feature is lossless trimming and cutting of video and audio files, which is great for saving space by rough-cutting your large video files taken from a video camera, GoPro, drone, etc. It lets you quickly extract the good parts from your videos and discard many gigabytes of data without doing a slow re-encode and thereby losing quality. Or you can add a music or subtitle track to your video without needing to encode. Everything is extremely fast because it does an almost direct data copy, fueled by the awesome FFmpeg which does all the grunt work. Features Lossless cutting of most video and audio formats Losslessly cut out parts of video/audio (for cutting away commercials etc.) Losslessly rearrange the order of video/audio segments Lossless merge/concatenation of arbitrary files (with identical codecs parameters, e.g. from the same camera) Lossless stream editing: Combine arbitrary tracks from multiple files (ex. add music or subtitle track to a video file) Losslessly extract all tracks from a file (extract video, audio, subtitle, attachments and other tracks from one file into separate files) Batch view for fast multi-file workflow Remux into any compatible output format Take full-resolution snapshots from videos in JPEG/PNG format Manual input of cutpoint times Apply a per-file timecode offset (and auto load timecode from file) Change rotation/orientation metadata in videos View technical data about all streams Timeline zoom and frame/keyframe jumping for accurate cutting around keyframes Saves per project cut segments to project file View FFmpeg last command log so you can modify and re-run recent commands on the command line Undo/redo Give labels to cut segments View segment details, export/import cut segments as CSV Import segments from: MP4/MKV chapters, Text file, YouTube, CSV, CUE, XML (DaVinci, Final Cut Pro) Video thumbnails and audio waveform Edit file metadata and per-stream metadata Edit per-stream disposition Cut with chapter marks Annotate segments with tags View subtitles Example lossless use cases Cut out commercials from a recorded TV show (and re-format from TS to MP4) Remove audio tracks from a file Extract music track from a video and cut it to your needs Add music to a video (or replace existing audio track) Combine audio and video tracks from separate recordings Include an external subtitle into a video Quickly change a H264/H265 MKV video to MOV or MP4 for playback on iPhone Import a list of cut times from other tool as a EDL (edit decision list, CSV) and run these cuts with LosslessCut Export a list of cut times as a CSV EDL and process these in another tool Quickly cut a file by its MP4/MKV chapters Quickly cut a YouTube video by its chapters (or music times from a comment) Change the language of a file's audio/subtitle tracks Attach cover art to videos Change author, title, GPS position, recording time of a video Fix rotation of a video that has the wrong orientation flag set Great for rotating phone videos that come out the wrong way without actually re-encoding the video. Loop a video / audio clip X times quickly without re-encoding LosslessCut 3.69.0 changelog: Add lossless cropping & aspect ratio override via bitstream and container metadata #643 Alow shifting tracks for each file (-itsoffset) #216 Add "decimate video" tool to filter away all non-keyframes #2111 Add Windows ARM 64 native build with native ffmpeg Move timecode out of timeline and make it copy-able #2592 #2691 #2800 #483 #2808 Upgrade Electron to latest Add new "opposing" align mode #2654 Add FFmpeg -hwaccel auto setting for hardware acceleration of certain operations Add API events export-start and export-complete Allow deleting track metadata #2819 Improve shift segments dialog #2839 Show keyboard shortcuts inside button tooltips in UI Warn if trying to cut with too few keyframes around cutpoint #516 #2780 #2756 (Linux) include app name in notification #2794 Pull latest translations Other notable changes: Advanced output directory selector #2101 #2115 #2755 increase max file name length to 250 (truncation) #2779 don't reset playback speed when using special playback modes #2889 preserve chapters when merging files that already have chapters don't merge adjacent segments in combineOverlappingSegments #2896 don't transfer segment name when filling gaps #2754 always scroll up to zoom in #2703 #2786 increase max keyframes to 10000 Don't bind ctrl/cmd+c by default (they interfer with copying text) Many other improvements and fixes Download: LosslessCut 3.69.0 | ARM64 | ~100.0 MB (Open Source) Links: LosslessCut Website | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
    • 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
  • Popular Contributors

    1. 1
      +primortal
      486
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      85
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      62
  • Tell a friend

    Love Neowin? Tell a friend!