PCI-Z Plugin

It's code release friday 

Another useful program, a member of the -Z series, it's PCI-Z

Description=PCI-Z is a freeware lightweight system utility designed to provide information about (unknown) PCI (PCI-E, PCI-X...) devices and helps you find appropriate device drivers.

It is well written so runs on almost every platform, more details on https://www.pci-z.com/
Enjoy

EDIT: New version
- new plugin version
- removed unnecessary FileInfo.exe
- adapted to the author's download link (by architecture)
- improved routine detection of pci id version (local and web source)

Always a failure in the last seconds 
Please correct line 169 with

Code: [Select]

ChangeInterface,Write,Value,%ScriptFile%,Interface,pLocBaseVer,%PCIIDVer%

I get fileinfo.exe error ...

I found reason behind, using path with space result fileinfo.exe not create fileinfo.ini

I am thinking about a workaround for fileinfo.exe 

btw, where is fileinfo.exe homepage ?

here is a workaround for fileinfo.exe space bug for current plugin:

Code: [Select]

Shellexecute,Hide,%GlobalTemp%\FileInfo.exe," #$q%ProvideFiles%\%ProgramEXE%#$q -FileVersion -ini",%GlobalTemp%
IniRead,%GlobalTemp%\FileInfo.ini,%ProgramEXE%,FileVersion,%var%
-->
Call,FileCreateBlank,%GlobalTemp%\FileInfo.ini,OverWrite
TxtAddLine,%GlobalTemp%\FileInfo.ini,"[%ProgramEXE%]",Append
Shellexecute,Hide,cmd.exe,"/c FileInfo.exe #$q%ProvideFiles%\%ProgramEXE%#$q>>FileInfo.ini",%GlobalTemp%
TxtReplace,%GlobalTemp%\FileInfo.ini," : ",=
IniRead,%GlobalTemp%\FileInfo.ini,%ProgramEXE%,FileVersion,%var%

***
never use %GlobalTemp% , use %ProjectTemp%, %GlobalTemp% is reserved and may change in future, %ProjectTemp% is static 
I feel simply replacing all %GlobalTemp% to %ProjectTemp% would do the trick.

*****
very nice plugin, good work 

 

very nice plugin, good work 

I just read the plugin without testing, seems very complete, well written and Strutured. Bravo 

@ChrisR

Will you consider to include plugin in the next update, at least through the add-on thru dl. ?
Feel free to change the use %GlobalTemp% to %ProjectTemp% suggests by Lancelot.

Another potential problem with FileInfo does not appear if you respect the old rules since BartPe era:
- simple %BaseDir% for ex. D:\WB
- no fancy letters & charactrs in folder or file names
- no blanks in folder names
- this means not put the builder and its files on the f. Desktop, can put a shortcut for start Builder
= no problems or errors.

Hi Nikky

we do not have old BartPE rules, we are far beyond.
- recommended basedir is D:\Oven , still it can be longer path or path with space, plugins makes required controls.
well path with space works fine since very first day we design projects, we had fixed many plugins 5-6 years ago, and since than continue.
- putting project to a desktop depends on things, plugins makes required controls.
== no problem or errors.

If there is an error with a path undocumented, let us know.

*
about adding plugins, we tend to put to server and distribute via \Downloads\ to avoid getting projects bigger, following ChrisR design.
If plugins are suitable, after checking all works ok...
Recently I mostly put KYHI plugins to server after some checks,
 very recently "SoftMaker FreeOffice" reply 203 http://theoven.org/index.php?topic=1413.msg19279#msg19279
 another example prz "Tera Byte" plugin http://theoven.org/index.php?topic=1290.msg18777#msg18777

We do not put all plugins to servers \Downloads\
ex: http://theoven.org/index.php?topic=1643.0
after plugin mature enough by plugin author we are glad to put to servers... 
If not, I sometimes rewrite a plugin and put to server, preserving author name and topic link 
and since I do not have that much free time, many available on topics.

This way we assure plugins distributed through servers* always work as intended, following same principles on all plugins.

++
Still up to project admin if plugin worth to put to project with spending space, balance....
Very mostly project special plugins always on project server, others up to project author, or server, or topic.

+
long story to short, I will be glad to put your PCI-Z and Aida64 plugin to servers after they fit conditions. 
and if not I may put with a simple plugin after a long time,
 knowing they available to everyone on topics, they wait on my long to do list.

All ways developed to get better with experience, to use limited time efficiently.

See You

I believe it is probably best to include it in Yomi than in SE.
It would then be available in Downloads folder for those who want to use.

SE projects has always been with only a minimal of applications to let users choose the applications that suits him in the wide Yomi's collection (> 1000 plugins).
These Plugins can be directly downloaded from the Downloads folder tree.
I think it is well like that. Also SE is already a little big with among others VC++ runtime, Opera 32 and 64 bits,...



Edit: I have not seen Lancelot's post but I believe it is ~same for the design.

I fully agree, I thought that the plugin is available if someone wants it.

Regards code Bakers 

Hi folks, as Arni said, I'll be back 

I've seen that the original plugin survived just as a bulletin at Yomi.
It's code release friday (again).

- new plugin version
- removed unnecessary FileInfo.exe
- adapted to the author's download link (by architecture)
- improved routine detection of pci id version (local and web source)
- when it is unpacked, in Options Calculate MD5=1d37be06e6e1bd532bb2766eec82737b

Regards code Bakers 

Welcome Back Nikky
 

When I tested everything was ok, but now there is some stupid error appearing on project build.
Quick fix, instead:

Code: [Select]

// Retrive files - Simpler is right now for both architectures
If,%pSelSourceCheckBox%,Equal,True,Begin
  If,Not,ExistDir,%Source_Folderx86%,DirMake,%Source_Folderx86%
  If,Not,ExistDir,%Source_Folderx64%,DirMake,%Source_Folderx64%
  If,Not,ExistFile,%Source_Folderx86%\%Source_Arhx86%,ExtractFile,%ScriptFile%,Folder,"PCI-Zx86.zip",%Source_Folderx86%
  FileRename,"%Source_Folderx86%\PCI-Zx86.zip","%Source_Folderx86%\%Source_Arhx86%"
  If,Not,ExistFile,%Source_Folderx64%\%Source_Arhx64%,ExtractFile,%ScriptFile%,Folder,"PCI-Zx64.zip",%Source_Folderx64%
  FileRename,"%Source_Folderx64%\PCI-Zx64.zip","%Source_Folderx64%\%Source_Arhx64%"
End
//

should be:

Code: [Select]

// Retrive files - Simpler is right now for both architectures
If,%pSelSourceCheckBox%,Equal,True,Begin
  If,Not,ExistDir,%Source_Folderx86%,DirMake,%Source_Folderx86%
  If,Not,ExistDir,%Source_Folderx64%,DirMake,%Source_Folderx64%
  If,ExistFile,"%Source_Folderx86%\%Source_Arhx86%", FileDelete,"%Source_Folderx86%\%Source_Arhx86%",NoWarn
  ExtractFile,%ScriptFile%,Folder,"PCI-Zx86.zip",%Source_Folderx86%
  FileRename,"%Source_Folderx86%\PCI-Zx86.zip","%Source_Folderx86%\%Source_Arhx86%"
  If,ExistFile,"%Source_Folderx64%\%Source_Arhx64%", FileDelete,"%Source_Folderx64%\%Source_Arhx64%",NoWarn
  ExtractFile,%ScriptFile%,Folder,"PCI-Zx64.zip",%Source_Folderx64%
  FileRename,"%Source_Folderx64%\PCI-Zx64.zip","%Source_Folderx64%\%Source_Arhx64%"
End
//

I apologize for the inconvenience 

Edit: Check 1. post

Hi Nikky,

as requested, added to server now

Code: [Select]

Call,DownloadX,"%BaseDir%\Projects\Yomi\AppY\System Tools\HW Info\PCI-Z.Script"

See: Downloading Plugins with a CodeBox

only cosmetics and +1 changed line due to compatibility ...

*
I have a request, can you make PCI-Z Plugin to use different folders following source
eg. %ProgramFolder_x64%=PCI-Z_x64
all other plugins already prepared that way .......

+
I can write a separate "PCI-Z Legacy" Plugin (1.31) If you are not interested in "PCI-Z Legacy"?

Hi Nikky,
I have a request, can you make PCI-Z Plugin to use different folders following source
eg. %ProgramFolder_x64%=PCI-Z_x64
all other plugins already prepared that way .......

No problem to replace, It never occurred to me that it would be in collision ...

I will change, test and put in topic 

+
I can write a separate "PCI-Z Legacy" Plugin (1.31) If you are not interested in "PCI-Z Legacy"?

What exactly do you mean by PCI-Z Legacy ?

Hi Nikky,

No problem to replace, It never occurred to me that it would be in collision ...

better few words behind my request:
exaggerated eg.
Using all the same plugins, you can build both x86 and x64 with
Gena Win7PESE Win8PESE Win8.1SE Win10PESE Azin-WimBuilder Azin-LiveSystemPro-Win10PE Azin-LiveSystemPro-Win8PE
8x2 = 16 builds (x86 and x64)
and use same \Programs\ folder with all

My request with a different folder for x64 avoid the collision 

I can exaggerate more with build numbers, different sources (xp, 2k3 ..) different service back (sp1 sp2 sp3) still logic is the same   

What exactly do you mean by PCI-Z Legacy ?

At HomePage there is PCI-Z Legacy (v1.31) for windows before XP-SP3  (+ReactOS)
keep in mind it has different "pci id"

so a separate PCI-Z plugin (using different PCI-Z %ProgramFolder%) better

If you are not interested, I can take the task. 

OK,

task list:
- PCI-Z for x86 and PCI-Z_x64 for x64
- separate PCI-Z Legacy plugin

Now I will steal yours 
 

Task done 

everything is clear from the attachment,

keep in mind it has different "pci id"

Legacy 1.31 version is just updating with the same pci id base.

Launch button has no routine to copy / use latest pci id,
however on bulid it does so.

Neext 

Hi Nikky,,

keep in mind it has different "pci id"

Legacy 1.31 version is just updating with the same pci id base.

Thanks for the info, my mistake. 

Both new Plugins are on server now

Code: [Select]

Call,DownloadX,"%BaseDir%\Projects\Yomi\AppY\System Tools\HW Info\PCI-Z.Script"
Call,DownloadX,"%BaseDir%\Projects\Yomi\AppY\System Tools\HW Info\PCI-Z_Legacy.Script"

See: Downloading Plugins with a CodeBox

Neext