Recommended Posts

I have read the documentation, specifically the following:

"4.6 - ReleaseDate

This property defines the date on which the setup file the module installs was created. It must be an eight digit number in the format YYYYMMDD (year, month, day).

* However * This property is much more important than it sounds. It actually defines the order that things are installed! AutoPatcher will install modules in the order: older date to newer date (smaller number to bigger). It also has an effect on the order things are listed in the selection window. "

I basically want to list the Stand Alone programs in alphabetical order. First I tried setting the release date all the same - that didn't work. Then I tried setting the release date to a sequence: 20000101, 20000110, 20000120, 20000130. I expected these 4 items to be sorted accordingly, but no luck.

(BTW, the standalone.apm parent file has a release date of 00000005).

This happened in 5.6.72 and 5.6.76

Any suggestions?

-John

  M2Ys4U said:
As far as I know ReleaseDate is the oder in which things are installed, not displayed. I do not think you can control the order.

I know that the documentation is not always correct but it does say:

"It also has an effect on the order things are listed in the selection window."

I guess I was assuming that this "effect" was something I could utilize to alpha sort the selection list.

-John

i believed it did when i wrote the documentation because i gave sub-parents lower values and they appeared first. i didn't actually experiment though i have to admit and it could have been through raptors design that sub-parents come first... if so a correction to the documentation is in order... (on the todo list to check it out at some point and correct if necessary)

I've been playing with the order a lot so I know the answer to this one. The display order is 100 percent dependent on the module's releasedate property. Lowest release date on top, highest on bottom.

I was thinking about asking Raptor to create a new property to control the order of displayed updates compared to what order they are installed in but I've been having him play with the executable so much lately, I was going to suggest this later. <hint, hint>

  Tenchi103 said:
I've been playing with the order a lot so I know the answer to this one. The display order is 100 percent dependent on the module's releasedate property. Lowest release date on top, highest on bottom.

I was thinking about asking Raptor to create a new property to control the order of displayed updates compared to what order they are installed in but I've been having him play with the executable so much lately, I was going to suggest this later. <hint, hint>

Tenchi103,

Sounds like it works for you - what am I doing wrong? - I tried setting the ReleaseDate for 4 modules to a sequence: 20000101, 20000110, 20000120, 20000130. I expected these 4 modules to be sorted accordingly, but no luck!

Thanks, John

  Tenchi103 said:
How are you're modules currenlty being displayed when you run AP?

I tried a number of different schemes, even setting all the ReleaseDates to the same number (9010). Here is a list of the ReleaseDates from the APM files in the same order as displayed on the 'List of Available Items' screen:

ReleaseDate=00009010

ReleaseDate=00009010

ReleaseDate=20000130

ReleaseDate=00009010

ReleaseDate=00000050

ReleaseDate=00009010

ReleaseDate=00009010

ReleaseDate=20000120

ReleaseDate=00009010

ReleaseDate=00009010

ReleaseDate=20000101

ReleaseDate=20000110

I am running AP ver 5.6.76, but the same was happenong with 5.6.72

-John

First thing you should always practice is to create a standard naming scheme for your ReleaseDates making sure that the number is greater than the parent module they are in.

Try beginning with 2000005 and go in increments of 5 (Example: 2000005, 2000010, 2000015...)

Give this a try and see what happens.

  Tenchi103 said:
First thing you should always practice is to create a standard naming scheme for your ReleaseDates making sure that the number is greater than the parent module they are in.

Try beginning with 2000005 and go in increments of 5 (Example: 2000005, 2000010, 2000015...)

Give this a try and see what happens.

Tenchi103,

I finally found some time to play with the ReleaseDate. I set the modules to the following sequence:

ReleaseDate=20000110

ReleaseDate=20000120

ReleaseDate=20000130

....

ReleaseDate=20000360

And the Parent Module had a ReleaseDate=00000005

No luck, display order had no relationship to ReleaseDate order.

BUT, when I changed the Parent Module ReleaseDate to 20000005 it all worked fine!

So I hope this helps others....

John

  major4579 said:
Tenchi103,

I finally found some time to play with the ReleaseDate. I set the modules to the following sequence:

ReleaseDate=20000110

ReleaseDate=20000120

ReleaseDate=20000130

....

ReleaseDate=20000360

And the Parent Module had a ReleaseDate=00000005

No luck, display order had no relationship to ReleaseDate order.

BUT, when I changed the Parent Module ReleaseDate to 20000005 it all worked fine!

So I hope this helps others....

John

I'm curious, is the parent module you created inside another module or is it on the root of AP? If it's inside another module, this would explain why you had to up the ReleaseDate from 00000005 to 20000005. (The parent module has have a larger number than the module that it's in)

  Tenchi103 said:
I'm curious, is the parent module you created inside another module or is it on the root of AP? If it's inside another module, this would explain why you had to up the ReleaseDate from 00000005 to 20000005. (The parent module has have a larger number than the module that it's in)

It's a root module - the APM file resides in "\autopatcher\modules".

All the actual modules (the ones I numbered sequentially) reside in "\Autopatcher\modules\stand_alone_mods".

Here's the contents of the root module APM file:

-----------------------------------------------------------------------------

[AutoPatcher 5.6 Module]

[General]

Title=Stand-Alone Modules

Description=

Author=Various

ModuleAuthor=ModuleEditor2

WebPage=

ReleaseDate=20000005

[behavior]

ParentID=

UniqueID=STAND_ALONE_PARENT

Critical=False

AutoExpand=True

Depends=

TimeToInstall=0

TimeToRemove=0

RequiresReboot=False

[DetectionRegistry]

RegistryPath=

KeyName=

KeyValue=

[DetectionFile]

FilePath=

FileName=

FileVersion=

[OperatingSystem]

WindowsVersion=ANY

SystemLanguage=1033

[systemComponents]

InternetExplorer=ANY

WindowsMediaPlayer=ANY

DotNetFramework=ANY

WindowsInstaller=ANY

MSNMessenger=ANY

[OfficeComponents]

Word=ANY

Excel=ANY

PowerPoint=ANY

Outlook=ANY

Publisher=ANY

Visio=ANY

Project=ANY

OneNote=ANY

FrontPage=ANY

InfoPath=ANY

Access=ANY

[installation]

[Removal]

--------------------------------------------------------------------

-John

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

    • No registered users viewing this page.
  • Posts

    • This was cool back in the day when done properly - loved having icons of specific devices.
    • Microsoft quietly burying a massive Windows 7 hardware driver feature as Windows 11 kills it by Sayan Sen Last month Microsoft announced a big update for Windows hardware drivers. The company declared that it was killing Windows Device metadata and the Windows Metadata and Internet Services (WMIS). For those wondering what it is, device metadata, as the name suggests, is the collection of additional, user-facing information that an original equipment manufacturer (OEM) provides about a hardware device. The feature was introduced with Windows 7 and can include stuff like icons, logos, descriptive texts, among other things, that help the Windows UI display details about such devices in places like Task Manager or Device Manager. This was a huge deal back in the day when Windows 7 debuted. The company called the feature "Device Stage" and Microsoft described it as a "new visual interface" that essentially worked like a "multi-function version of Autoplay where it displays all the applications, services, and information related to your device." It is often considered synonymous with the Windows "Devices and Printers" Control Panel applet. Neowin did an in-depth overview of the feature when it first launched which you can find in its dedicated article here. The Windows OS was able to obtain the device experience metadata from the WMIS, but now that the feature is being deprecated, Microsoft has begun removing information about Device Stage from its official support documents. Neowin noticed while browsing that a support article regarding automatic Windows hardware drivers was updated for Windows 11 and 10 sometime last year after the release of Windows 11 24H2. Previously, this article was geared for Windows 7 and was much longer. It also contained information about Device Stage, which, as mentioned above, was a headlining feature on Windows 7. In the said article, the section "If Windows can't find information about your device in Device Stage" has been deleted. You can find the archived version of the support page here. Aside from shortening the amount of information on the page, Microsoft has also added some more details on it. The company has now tried to define what the Microsoft Basic Display Adapter is, how updating drivers through Device Manager works, as well as a thorough and detailed troubleshooting section for common hardware driver errors on Windows, including one for USB-C. You can find all the new details on the updated support page here on Microsoft's website.
    • Sounds creepy to say the least. Don't need nor want AI having access to my history. They're claiming it to be an "offline" model now, but how can we guarantee they don't go behind our backs and change that?
    • Exactly! Without those fundamentals you've mentioned, Democracy is literally just Demonstration of Crazy, nothing to be proud of in such system.
  • Recent Achievements

    • Veteran
      Yonah went up a rank
      Veteran
    • First Post
      viraltui earned a badge
      First Post
    • Reacting Well
      viraltui earned a badge
      Reacting Well
    • Week One Done
      LunaFerret earned a badge
      Week One Done
    • Week One Done
      Ricky Chan earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      481
    2. 2
      +FloatingFatMan
      264
    3. 3
      snowy owl
      238
    4. 4
      ATLien_0
      233
    5. 5
      Edouard
      176
  • Tell a friend

    Love Neowin? Tell a friend!