[daddydave]

DrivercabHelper Version 1.2
Now handles Unicode files!

The new version can be found here:

http://www.freewebs....ercabhelper.htm

This contains both the compiled DrivercabHelper.exe and the equivalent DrivercabHelper.au3 for those who currently have Autoit3 installed.

Target audience: HFSLIP users.

What it does
Copies files from the source folder to the destination folder, including subdirectories, deleting the destination folder at the beginning. For each file that is an INF file, it does the third step of the DRIVERCAB integration method described here by Oleg_II and clarified here by Tomcat76, preserving comments in the INF files. Note that Oleg_II says "it's not for every user because some INF editing is involved." DrivercabHelper aims to solve the problem of having to do all that INF editing. The files that are not INF files are just copied. The third step appears to be the only required step; I am getting my drivers using a driver backup utility and I am not using subfolders.

How to use
Set a source and destination folder, verify ISOTITLE (see IMPORTANT UPDATE below), hit the big button. Source and destination folder may be specified on the command line. To be cautious, it is recommended that you use a temporary folder for the destination folder, then copy the result to your DRIVERCAB folder.

How to find bugs
The interface contains a detailed log window to assist in finding possible bugs. In addition, the excellent program CSDiff is highly recommended if you care to do any bug testing, you can do a folder compare first, note any missing or added files (there shouldn't be any of either), then double-click on any modified file for a quick file comparison.

IMPORTANT UPDATE: DrivercabHelper 1.2 now supports Unicode files. Please let me know if this works for you.

DrivercabHelper 1.1 has been corrected to use the default ISOTITLE of HFSLIPCD and is now user configurable. If you are not using HFANSWER.INI, use the DrivercabHelper 1.1 default, and if you are using HFANSWER.INI, change the ISOTITLE field to whatever your ISOTITLE is in that file.

Screenshot


Gratitude To
Jon Bennett for adding Unicode support to AutoIt
Oleg_II for coming up with this method
TommyP and Tomcat76, obviously, for all the hard work they put into coding and supporting HFSLIP
Tim Fehlman at Daily Cup of Tech for the article "Folder Recursion in Autoit" including source code, from which DrivercabHelper borrows heavily to process subfolders.



Any bug reports, feature requests, or interface suggestions are welcome.

Bug Report
DrivercabHelper does not currently support Unicode files. This might not be an easy fix, since AutoIt3 doesn't support Unicode either.

This post has been edited by daddydave: 12 September 2007 - 01:55 PM

[Tomcat76]

Thanks

[Kiki Burgh]

would this be included in HFSLIP cmd eventually? thanks!

[daddydave]

Kiki:

Quote

would this be included in HFSLIP cmd eventually? thanks!

As far as tommyp and tomcat76 and tommyp including it in HFSLIP, I see at least a couple of obstacles. The main one is that unfortunately, I wrote this as an .au3 file and not a .cmd file...writing in .cmd more difficult for string manipulation. And the utility is probably too interactive in its current form for that purpose.

EDIT on 1/22/07 Not to mention the fact this only has to be run once, vs. multiple runs of HFSLIP.

This post has been edited by daddydave: 01 February 2007 - 12:45 AM

[daddydave]

First bug found (more to follow?)...WINCD should be HFSLIPCD, at least if you are using the HFANSWER.INI from the hfslip.org site.

See original post, which has been edited, for details

[daddydave]

Updated to version 1.1. Now uses the default ISOTITLE of HFSLIPCD and is user configurable. See first post for details.

[daddydave]

Added screenshot to first post.

[daddydave]

I know it's early, but is anyone using this besides me?

[Kiki Burgh]

i've downloaded it but have yet to try when i hopefully could already create new ISOs ... hopefully soon (as since my sys crashed, i have been able to even participate neither in the test releases nor in the recent finals)

[Lindiro]

The wording in my INF file for my marvell LAN driver was replaced with unreadable symbols. I've attached a copy of the file so you can see what I mean. I manually edited the file and will test it tonight along with my other drivers.

Attached File(s)

•  yk51x86.inf (17.34K)
  Number of downloads: 10

[daddydave]

@Lindiro: Thanks for the bug report. Could you attach the original inf file as well?

[Tomcat76]

Is it possible that the original was in Unicode?

[Super-Magician]

Yes, this problem occurs for me too. The file was in Unicode as Tomcat76 suggested, so I had to replace the copy and modify it myself later. That should be the only issue with your program.

[daddydave]

This might not be an easy fix, since AutoIt3 doesn't support Unicode either.


EDIT: Or not
http://www.autoitscript.com/forum/index.ph...&hl=unicode

This post has been edited by daddydave: 31 January 2007 - 11:46 PM

[Oleg_II]

daddydave
Wow! Just come by this topic! You rock!

By the way. It is easy to convert INF files from Unicode and they only loose the characters from some languages. The work around is still manual editing of INF file - change the strings in that language to English and then convert from Unicode.

Don't have an idea how to do it with your utility but maybe it's possible it checks if INF is in Unicode and worns a user about this?

[Lindiro]

daddydave here is the orginal INF file.

Attached File(s)

•  yk51x86.7z (13.75K)
  Number of downloads: 8

[daddydave]

I can confirm that Lindiro's inf does show up as "UCS-2 little endian" in Notepad++.

Not sure what to do yet. (rewrite in from scratch in Python?)

I could warn the user, that could be a good interim band-aid, but I'd really like to able to just handle it.

[Oleg_II]

I read about Unicode2ANSI conventer somewhere on the sites about BartPE...

[daddydave]

Oleg_II, on Feb 1 2007, 11:25 PM, said:

I read about Unicode2ANSI conventer somewhere on the sites about BartPE...

Is converting it to ANSI the right thing to do? What about characters that can't be represented in ANSI?

[Oleg_II]

daddydave, on Feb 1 2007, 11:17 PM, said:

Is converting it to ANSI the right thing to do? What about characters that can't be represented in ANSI?

Well, it's just a thought You can't use Unicode, then try something else - why not ANSI?

As for charecters - I don't think there will be problems with installing drivers. But there will be unreadable lines in drevices > drivers. Unfortunatelly there is no other way to deal with it except creating driver packs or just INF pack for replacement. Or editing it manually

PS Or maybe you find the way to edit Unicode files...

This post has been edited by Oleg_II: 02 February 2007 - 12:03 AM