Recommended Posts

Alrite this outa be my final post for some days cuz I ran out of ideas-

Whether this will go with the Bonus Pack or AutoPatcher, The K++ Codec Pack is very usefull, So are the emulators for real player and apple player. I doubt its a good idea to include KazaaLite or something tho but its just a suggestion.

Maybe also include some of those winbeta coversion files kits for the option to alternate between OS'sor install options from other OS's? (not probably) like TweakNT and similar programs.

Also maybe some video/sound format convertors would be useful to include along with some free unzip program?

All those addons that Ms has posted before for windows media player skins, and plugins and all the extra stuff for movie maker 2.0 as well such as transitions.

I think that pretty much covers it all...

hello,

I am sure it has been written before but I must add too.

Customize thing must be added again. after november update autopatchercustumize.dat (or any custumizatin options) is deleted. I can't figure out why ?? I had to download the previous version to customize !

ArgoN: in november release, you can customize the autopatcherxp.dat :D But dont worry, starting from december release, you will love TDI :D Triple Database Indexing will allow AutoPatcher to index a database using three different database files, thus allowing you to keep a custom database (autopatcherxp_custom.dat) intact between monthly releases, a bonus database (autopatcherxp_bonus.dat) which also wont be affected by bonus releases (this way you wont need to download a bonus pack every month), and a normal main database, which will be the only database affected by monthly releases... TDI will make it possible to customize your database (again, autopatcherxp_custom.dat) without worrying about the next month's release overwritting your database, thus losing all your custom entries...

Judging from that, i believe that you will love december release :D

/Raptor

ArgoN: in november release, you can customize the autopatcherxp.dat :D But dont worry, starting from december release, you will love TDI :D Triple Database Indexing will allow AutoPatcher to index a database using three different database files, thus allowing you to keep a custom database (autopatcherxp_custom.dat) intact between monthly releases, a bonus database (autopatcherxp_bonus.dat) which also wont be affected by bonus releases (this way you wont need to download a bonus pack every month), and a normal main database, which will be the only database affected by monthly releases... TDI will make it possible to customize your database (again, autopatcherxp_custom.dat) without worrying about the next month's release overwritting your database, thus losing all your custom entries...

Judging from that, i believe that you will love december release :D

/Raptor

ok thanks.

btw I found custom_pack in this thread https://www.neowin.net/forum/index.php?show...pic=114367&st=0

Edit:

waw I read it again. TDI rules :laugh:

btw I found custom_pack in this thread https://www.neowin.net/forum/index.php?show...pic=114367&st=0

Edit:

waw I read it again. TDI rules  :laugh:

Yeah, that's the instructions on how to make the custom pack in the November release. It will be different in December, and from then on it will remain the same. :) So once December come out and we have the TDI working, then everything will be fine. :D

i have already arranged a party tomorrow to celebrate TDI?. AutoPatcher is the first program that uses my TDI? technol:Dy :D... Hell, it was the first with DDI?!

Long live TDI?!

/Raptor

Raptor, put the drugs down man, it'll be oka:laugh: :laugh: I like TDI? as much as the next guy... but a party?? :pinch:: :pinch:

I also have a suggestion.

will TDI be same as this ? I mean will we create *.bat files again ?? If so, is it possible to add something so that *.bat files are automatically created ? for example, there can be an option like "this is a windows update" so the program (if checked) automatically creates bat files with /q ?? and does the copying to "customprogfiles" and does the dat file modification ?? ;)

I also have a suggestion.

will TDI be same as this ? I mean will we create *.bat files again ?? If so, is it possible to add something so that *.bat files are automatically created ? for example, there can be an option like "this is a windows update" so the program (if checked) automatically creates bat files with  /q ?? and does the copying to "customprogfiles" and does the dat file modification ??  ;)

Actually, TDI means it can now detect/read off of 3 distinct Databases at once, if found. That way you can make one called autopatcher_custom.bat, and once the AP sees it, it will add your stuff in easily. That way you can do the monthly updates, without having to redo your custom entries.

The batch files will still have to be made by you, but the December version will have a new Documentation folder that will include specific instructions on how to do that. :)

I also have a suggestion.

will TDI be same as this ? I mean will we create *.bat files again ?? If so, is it possible to add something so that *.bat files are automatically created ? for example, there can be an option like "this is a windows update" so the program (if checked) automatically creates bat files with /q ?? and does the copying to "customprogfiles" and does the dat file modification ?? ;)

TDI=Triple Database Indexing... AutoPatcher populates a database combining three files instead of just one... that will help you keep everything in order...

But why wouldnt you make custom entries on windows update fixes? AutoPatcher will haev them in sooner or later (next month for example!). As for non-windows-update stuff, we cant possibly know where you will have the file, or what kind of file it is, or what switches it needs... Even then... what if a program needs more than one line? How would we know what lines we need?

/Raptor

TDI=Triple Database Indexing... AutoPatcher populates a database combining three files instead of just one... that will help you keep everything in order...

But why wouldnt you make custom entries on windows update fixes? AutoPatcher will haev them in sooner or later (next month for example!). As for non-windows-update stuff, we cant possibly know where you will have the file, or what kind of file it is, or what switches it needs... Even then... what if a program needs more than one line? How would we know what lines we need?

/Raptor

Well said, but don't worry, I'll try to make sure I have something explaining it in the Dec Update. :)

How about...CoFNoD? Combination of a Finite Number of Databases allows you to have any number of databases you want and they get all mixed together?

Also, I propose a new directory structure:

AP

AP\batch

AP\wupd

AP\bonus

AP\custom

AP\db

AP\prog

Program files would go in AP\prog. The only file in the root AP folder is a shortcut to AutoPatcher_XP.exe in AP\prog. This would hide all the confusing files from a newbie.

Finally, I suggest you use an XML file instead of an old-fashioned INI file. Windows XP comes with MSXML 3.0 and 4.0 (albeit not the newest SP), so you wouldn't need to worry about dependency issues with that. :D

@memodude: Directories for December Update:

AutoPatcher

AutoPatcher/Batch

AutoPatcher/Documentation

AutoPatcher/ProgFiles

AutoPatcher/CustomProgFiles

In the main AutoPatcher Directory, will be the main exe, the dat file, and the ocx files. BUT outside the main directory will be a AutoPatcherXP.exe file that will launch a menu that will give users a choice of what to run the AutoPatcher, or view some of the Documentation.

I think this should be okay and cut back on the confusion. Also today Raptor and I worked on a new way to update the previous versions to the current ones. It will stop all the problems that happened before. In fact, you won't be able to even mistake it for a normal version of the file. :)

As far as XML goes, we don't use a ini file, we use a dat file. And it's so that it will be easy for people to edit it. Also we can continually change it to add new features easily. We're here for ease! :D

Thanks for the very quick response. :)

One more idea: change the extension on the databases to .apdb. That would be more specific. Also, that would make it possible for someone to make an AutoPatcher Database Editor (hey, I'll do that! :)) and associate it in Windows Explorer. Finally, the database is an INI file, it has INI syntax, it just has a DAT extension. :p

Off-topic: OptiPlex, how often do you change your avatar? First it's that black avatar (forget what it is), then a Pentium 4 HT logo, then a Pentium 3 logo, and now a Designed for Windows XP logo. What next? :p

Thanks for the very quick response. :)

One more idea: change the extension on the databases to .apdb. That would be more specific. Also, that would make it possible for someone to make an AutoPatcher Database Editor (hey, I'll do that! :)) and associate it in Windows Explorer.

Are you readin' our minds? :unsure: lol We just today started doing that. We changed all the bat files to "axp" files, since they can't be run outside of the AutoPatcher anymore. As far as the database goes, not sure if we can do that (change dat to apdb), but if we can we probably will. :D As far as the editor goes, we now have a "AutoPatcher_Custom" dat file that will be used soley for custom things. No more editing the main dat. So I'm not sure if we'd need an editor. Thanks for the offer, and who knows, we may decide to get one from ya. :D

Oh, and I know that it's in INI format. :p I just was sayin'... it's a dat file. hahaha

Thanks for the very quick response. :)

One more idea: change the extension on the databases to .apdb. That would be more specific. Also, that would make it possible for someone to make an AutoPatcher Database Editor (hey, I'll do that! :)) and associate it in Windows Explorer.

Are you readin' our minds? :unsure: lol We just today started doing that. We changed all the bat files to "axp" files, since they can't be run outside of the AutoPatcher anymore. As far as the database goes, not sure if we can do that (change dat to apdb), but if we can we probably will. :D As far as the editor goes, we now have a "AutoPatcher_Custom" dat file that will be used soley for custom things. No more editing the main dat. So I'm not sure if we'd need an editor. Thanks for the offer, and who knows, we may decide to get one from ya. :D

Oh, and I know that it's in INI format. :p I just was sayin'... it's a dat file. hahaha

Nice! One idea: the bat files should be apui, for AutoPatcher Update Information.

Sorry about the INI thing, didn't mean to insult your intelligence. :D

Nice! One idea: the bat files should be apui, for AutoPatcher Update Information.

Sorry about the INI thing, didn't mean to insult your intelligence. :D

No prob man, I was just messin' with you about the ini thing. I know what you meant. lol ;)

As far as the file extensions go... hmmm... .apui is nice, but I was kinda partial to .axp myself. haha :)

But why wouldnt you make custom entries on windows update fixes? AutoPatcher will haev them in sooner or later (next month for example!). As for non-windows-update stuff, we cant possibly know where you will have the file, or what kind of file it is, or what switches it needs... Even then... what if a program needs more than one line? How would we know what lines we need?

/Raptor

ok I see. I only use /q, not because I know what it does, but it is used in every *.bat file created for WU :rolleyes:. is there a thread where I can find what

/q /z

/qn REBOOT=Suppress

/q:a /r:n

/silent

/qb

/q

means ?? :unsure:

sorry this is not a wish :(

Not sure if this was already suggested (if so:sorry:).

I use bginfo (sysinternals freeware) to add information on my desktop image on every computer I own. Just add a key to the RUN-key in your system that points to the executable (on my machine I just copied it to SYSTEM32 directory): bginfo /timer:0

Hope this adds value to the list.

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

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • 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
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!