Hehe smile

jaws : i can't download your code, it says :

Error: We were unable to lookup the owner of this file, please retry your request.

2

(12 replies, posted in Software)

No, you can hide it like this :

var
 Title : Array[0..512]of char;
begin
    // get current title window
  GetConsoleTitle(PChar(@Title ),SizeOf(Title ));
  ShowWindow(GetConsoleWindow, SW_HIDE);

Cheers wink

3

(12 replies, posted in Software)

Thanks everybody for the code!

@jaws1975 : just use {$APPTYPE CONSOLE} wink

I really need to learn Windows API to leave Delphi and just code in plain old C tongue

4

(12 replies, posted in Software)

Thanks for searching OverFlow! I should have done this myself... In fact, I check the very first pages and the last one, my bad.
It seems to be C language, but this Win32 API is really difficult to read, I should buy a book wink

Kal

5

(12 replies, posted in Software)

Oh, my bad, I thought setup.exe was launched from CD, not from %SystemRoot%... In that case, ok, I can't do anything wink

Thanks for your answer,
Kal

Hi,

This is really a good job! I use this trick on every CD I make, for DriverPacks. By the way, I don't like the way driver letter is detected in presetup.cmd :

REM +==========================================================================+
REM |   Finding CD/DVD driveletter.                                            |
REM |--------------------------------------------------------------------------|
SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i::

Indeed, if there's a Hard Disk with a OEM folder/file at root, then identification is corrupted. One good thing should be that fake setup.exe passes drive letter as argument. This one can detect drive letter from which its launched, easily with windows API.

Does anybody have the source of fake setup.exe? I could mod it to suit my own needs.

Cheers,
Kal

Wow you seem to have made a good job jaws, congrat ! wink

Here is my source, I didn't have time to add functions you were requesting, but feel free to do so :
RapidShare |ADrive

That would be good to merge our work and do only one DriverPacks extprctor.

Hi Helmi,

Thanks for making this thread sticky and moving it into the proper section. I thinkg that each post dealing with the request should be deleted, but it's just my opinion. Moreover, to avoid confusion for new user, we should stay with one program to make this task. As I said, I'll publish my code as soon as I'm back from vacation, so jaws will be able to include his modifications, or I will add them by myself.

And yes Helmi, I'm Kal from WinCert and RyanVM forums smile

Hi jaws1975,

I will publish the code of my DriverPacks extractor. I just wait to be back from vacation (27th July) and cleanup the code. Maybe you should wait a bit and modify the code I will publish, avoiding to get 2 differents versions doing the same thing.

Kal

OverFlow wrote:

I think you misunderstoood...

re  DPsXtrct.ini.

would not be required DriverPacks has a routine that converts the 8.3 names back into thier full names so  DPsXtrct.ini is not needed as it can be replaced by a built in process. (no manual file edits)

Ah ok that's a nice a feature. But it would be still needed for personal 3rd party DP, wouldn't it?

Jaak wrote:

I am not going to be testing this if this does not add choice for third party and then separate third party.
(and it also has to work in M1.)

Hu, I think I don't understand what you mean. We can use 3rd party DP with it. And what is M1?

Cheers,
Kal

OverFlow wrote:

because it may need to be updated...

IE i cant tell you how many times i wish i had the source code for our setup.exe. I am just SOL on that one.
I am not going to do to someone else what i would not want to be done to me. ( and it has been and i hate it )
If I include something with base then the source code for it will be available to the code team, period.
   ( Wim can of course do as he pleases wink )
We have no intention of useing more than one language to code DriverPacks.
You and I might both get hit by a truck on the same day wink

for many reasons... is the reason smile

Sure, I will publish the source code when I'll be back from vacation. I will cleanup the code and put GPL header. But, IF it becomes a part of DP base, maybe you can let it in Delphi and I'll do the updates needed wink
Well, we're not yet at this stage, I don't care if it's written in Delphi or AutoIt, I'm just afraid that some functions are not avalaible in AutoIt. I used Delphi because I couldn't find a great gui builder for AutoIt.

OverFlow wrote:

wouldnt even need a dialog if they select no packs ther is nothing for the finisher to do...
no reason to keep it - so no reason to bother asking...

Well, as sT0n3r pointed it out, if we remove the finisher, then we will have an error when RunOnceEx/GuiRunOnce/WPI will launch it becomes it won't be present in %SystemDrive%. One solution would be to launch finisher from a .cmd, something like that :

DPsFnshr.cmd

@echo off

:: Run DriverPack finisher ...
IF EXIST "%SystemDrive%\DPsFnshr.exe" start "DPsFnshr" /wait "%SystemDrive%\DPsFnshr.exe"

del /Q "%SystemDrive%\DPsFnshr.cmd"
OverFlow wrote:

For example - converting 8.3 pack names to thier full names is an existing function that is built into the code 
You are useing a data file for this. So i would not need to do that i would just call the routine wink .
this automates a now manual process and eliminates an unneccessary file.
by extension there is no need for you to write a routine to do this since we have one.
I cant give you code bytes or subroutines to use because you did not take the bait when i offered AutoIt as your starting point.

Well, maybe my explications was confused, but DriverPacks Extractor doesn't convert to 8.3 format. I just say that when someone use a 3rd party DriverPacks, he needs to put it in OEM folder in 8.3 format and modify DPsXtrct.ini.

OverFlow wrote:

What you have works. It is simple and effective. that is great!

Let's see if what you have already put here generates any interest before you or I sink a bunch of time into it.

If it IS popular then I will make it a feature,

Thank you smile
To become popular, maybe we need to move this thread to a place where there's more visitors, or make an announcement or something like that. I don't mind if it's popular or not, I just made this to suit my needs and fill request from others in the thread.

@sT0n3r:
I'm really glad that it worked like a charm for you! It's good news. The bug you found will be solved by the trick I explained above. But it will requires extra files edit...

I will add the Keep The Drivers option when I'll be back smile

To conclude, Sardena is bellisima lol

Cheers,
Kal

Why do you want to re-write the code in AutoIT if it becomes a part of the project? I mean, we can just include the .exe in the archive, and the base code will copy it into OEM folder. Just like Un7Zip. Maybe you prefer to get all the project in AutoIT format?

OverFlow wrote:

ps if you put your program after the copy of the finisher ini then you would only need to edit it (or overwrite it)[or not]
- IE simply move the extraction step to after the finisher step in presetup.cmd... ( I could make this change in base quite easily too. )

Well, in fact, here is a part of my presetup.cmd

REM +==========================================================================+
REM |   Decompressing the DriverPacks to the harddisk - using un7zip.exe.      |
REM |--------------------------------------------------------------------------|
%CDDRIVE%\OEM\DPsXtrct.exe

REM +==========================================================================+
REM |   Copying/decompressing the files to finish the installation.            |
REM |--------------------------------------------------------------------------|
IF EXIST %SystemDrive%\D %CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\bin\*.7z %SystemDrive%\
IF EXIST %SystemDrive%\D COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\
IF EXIST %SystemDrive%\D IF EXIST %CDDRIVE%\OEM\*.ins COPY /Y %CDDRIVE%\OEM\*.ins %SystemDrive%\

As you can see, I only copy DPsFnshr if there's at least one DriverPack extracted. So if I launch 'DriverPacks extractor' after copying DPsFnshr, how can I test this ?

Maybe I could delete the DPsFnshr in my program. Fo example, if the user quit the application without extracting anything, I put a dialog box asking if he wish to keep DPsFnshr or not.

Cheers,
Kal

Hi sT0n3r!

At least, someone posts to this topic big_smile
I'm glad that you like it, and I'm gonna include some changes that you suggest. Unfortunaly, I'm currently on vacation, I'll be back 27th July. So I can code quickly, but I can't test : I just have my laptop.

sT0n3r wrote:

...but it does do 3rd party driver packs which i am not sure your version does (downloading yours now  1k a sec wtf) i will put up a mirror when its done.

Well, my program does support any DriverPacks : official & 3rd party. You just need to put the DriverPack in the same directory as DPsXtrct.exe, in 8.3 name format. Then, you give a name for this DriverPack in DPsXtrct.ini, as explained above.

I want to add an option that "DriverPack selector" has : Keed The Drivers. For this, my program needs to edit DPsFnshr.ini when it's copied to %SystemDrive%, and modify "KTD" entry. To be able to do this, DPsFnshr.ini needs to be copied by my program, not by presetup.cmd. So we'll need to modify presetup.cmd to skip the copy of DPsFnshr.ini file. If my DriverPack Extractor becomes an official part of this project, then presetup.cmd won't need extra edits and DPsFnshr.ini will be generated automatically with official DriverPacks names.

Cheer,
Kal

Normal integration.

I tested the latest nightly.  G_A 8.06Gdoesn't work with Geforece GO 6200 :
http://img375.imageshack.us/img375/3507/dpgahz2.th.png

Troubles appeared with GA 8.02 release (black screen).

Kal

Ok I will test it as soon as I can!

Well, nobody is interested anymore ? lol

Anyway, I'm going on vacation for three weeks Sunday, so if someone want to test it, here is it :
http://kalxp.free.fr/Addons/DPsXtrct-0.1.zip
Mirror (Thanks to sT0n3r)

It's multilingual : French & English supported. System language is detected at run time.

Screenshot:
http://img161.imageshack.us/img161/669/captureriu6.th.png

I added a function to see supported devices.

DPsXtrct.ini sections :
[names] : File names associated to DriverPacks names

[names]
DPC803.7z=DriverPack Chipset 8.03
DPCP804.7z=DriverPack CPU 8.04

[checked] : pre-defined value if you want a driverpack to be checked or not. If no entry, default value is True :

[checked] 
DPGA710.7z=false

Modified presetup.cmd included.

Just put DPSDEVS.HLP DPsXtrct.exe DPsXtrct.ini in OEM folder and replace presetup.cmd in I386 by the one in zip file.

Cheers!

It's a bug report.

Hi,

I have a Gefore 6200 GO on my laptop. Everything was working well with DriverPack Graphics A 7.10, and today I tried 8.04 and I get a black screen on first boot.
I know it's due to modification made in DriverPack 8.02, because that's where you modified N1 directory to update to new version. Same bug happen if I install driver manually from N1 directory, after XP installation.

Cheers,
Kal

Thanks for adding ICHR support! It worked like a charm here !

Cheers,
Kal

Ok it seems to work like a charm! I modified a bit the GUI to show file names. Here is a screenshot on a real install through vmware :
http://img77.imageshack.us/img77/5250/dpsextractorzm6.th.png

In the futur, I could add some options to such as enabling ATI Catalyst Control Panel for DriverPacks Graphics A...

If someone is interested in this software, I will post the binaries and source under GPL.

Cheers!

I'm curently writing the program to get the choice during installation. Here's a screenshot on how it will look like :
http://img389.imageshack.us/img389/671/dpsxtrctdi9.th.png

It checks for every 7z files in current directory of exe file. Then, it looks in an INI file if a DriverPack name is present for each 7z files found. For example :

[general]
DPC803.7z=DriverPack Chipset 8.03
DPCP804.7z=DriverPack CPU 8.04
DPGA804.7z=DriverPack Graphics A 8.04
DPGB804.7z=DriverPack Graphics B 8.04
DPGC804.7z=DriverPack Graphics C 8.04
DPL8053.7z=DriverPack LAN 8.05.3
DPM805.7z=DriverPack MassStorage 8.05
DPSA805.7z=DriverPack Sound A 8.05
DPSB805.7z=DriverPack Sound B 8.05
DPW806.7z=DriverPack WLAN 8.06

Auto extraction is launched after 1 minute if no activity (keyboard/mouse) is detected. Feel free to give any suggestions. I need to test it before publishing it.

Kal

I'm glad that you agree on this feature. I rent a book at library to learn Delphi. As I'm already an exprienced developper, it shouldn't take a lot of time for me to learn this new language. I'll try to write a GUI with these features :
- Lists all DriverPacks found in a directory with the possibility to extract them or net
- Set a timer that will end the application of no user activity is detected. In that case, all DriverPacks found will be extracted.

Cheers,
Kal

Well, I need a non managed language, such as C/C++/Delphi/AutoIt. I'm confortable with C, but I don't know any gui builder for this. I'll have a loog at AutoIt which seems easier.

In fact, what I had in mind was something like : launch a GUI from presetup.cmd that will allow end user to choose which driverpacks he wants to use. If no interaction is detected over 60 seconds, then automatically use all avalaibles driverpacks.