1

(19 replies, posted in News)

Sorry to hear that. Rest up and get well.

Yes, new Intel-based Macs can run Windows for sure (as virtual or stand-alone). I just want to know how convenient it is, are there any issues, etc.

Thank you smile

We all know that Bâshrat the Sneaky uses a mac! I think to get one for myself and would like to hear from the pro about how easy it is to use a mac to develop and test Windowz apps?! (is there autoit for mac big_smile)

Thank you.

4

(8 replies, posted in DriverPack Sound)

Could you please explain:

removed
- Realtek HD Audio (onboard on Intel Chipsets) driver, since it is now completely supported by the official Realtek HD Audio driver

Is Realtek HD Audio supported in this dp or what?!

5

(13 replies, posted in Other)

Thank you Helmi.

closeDSP.exe works, but, the whole process consumes quite long time.

When I said the method described in this thread is better, I meant it consumes less time. Both methods run DevPath.exe, so "Windows adds the path as a default driver source". I only want to know if the time taking by makePNF.exe is necessary.

6

(13 replies, posted in Other)

Helmi wrote:

Well, IIIRC, your goal in this thread (http://forum.driverpacks.net/viewtopic.php?id=535) thread was to have Windows automatically detect the directory as a driver source.
That will only work with Bâshrat the Sneaky's method I guess.

With the CD of this thread you could only point it to search the CD for drivers.
Not sure what you prefer.

The method in that thread includes makePNF.exe which throws tens of DSP popus. So, if running makePNF.exe is not necessary, then the method described here is better.

7

(13 replies, posted in Other)

@BST, will this method work in case Windows has already been installed using standard CDs, i.e. no DriverPacks were slipstreamed?

8

(19 replies, posted in Other)

I meant no DSP windows where shown at all and closeDSP.exe did not close anything!! I even run makePNF.exe  without closeDSP.exe in background and no DSP windows where given. Maybe there is a cache or something where Windows keeps info about drivers and doesn't ask for their signatures if it asked for them before.

9

(19 replies, posted in Other)

Maybe I did something wrong the first time! I repeated the process today but did NOT get any DSP window!!! How can I make the DSP windows to show up again?!

10

(19 replies, posted in Other)

There was a problem with closeDSP.exe! When the first DSP popup came, the program gave an error message (something like text not found) and exited!

Does your closeDSP.exe work with all Windows languages, i.e. multilingual GUI ?

Thank you.

11

(19 replies, posted in Other)

@Bâshrat the Sneaky:
Will your updated guide install only signed drivers? Or it was only to get rid of Driver Signing Policy popup?

Thank you.

12

(19 replies, posted in Other)

Thank you Bâshrat the Sneaky smile

Now, suppose that I have a fresh Windows XP with yellow exclamation marks on some hardware devices. What suppose I do after extracting DriverPacks and executing the two programs given above, so that Windows starts H/W drivers installation? Should I restart the computer or what?

13

(19 replies, posted in Other)

Any hint how this can be done?!

14

(19 replies, posted in Other)

Helmi wrote:

Unless you want to create this directory on an already installed Windows...

Exactly!

15

(19 replies, posted in Other)

I know the driver disk is in Bâshrat the Sneaky' to-do list, but, is it possible to manually build driver disk out of DriverPacks? Uncompressed DriverPacks are huge and wouldn't fit in a CD. One can of course have all 7z files on a CD and uncompress them into a folder after Windows setup. The question is how to tell Windows to search that folder to find drivers for uninstalled H/W? I'm thinking load and want answers smile

Is it safe to extract and recompress each DP using: 7z, Ultra, LZMA, 128MB, 273Word, and Solid Archive?

17

(11 replies, posted in Feature Requests)

All the respect Bâshrat the Sneaky, but one check box would not be big deal!

Here is an example:

if checkbox then
mkisofs.exe -iso-level 4 -force-uppercase -volid ""%CD_label%"" -A PEBUILDER/MKISOFS -sysid ""Win32"" -b BOOTSECT.BIN -no-emul-boot -boot-load-size 4 -hide BOOTSECT.BIN -hide boot.catalog -o ""%ISOfile%"" ""%OutDir%""
endif

18

(11 replies, posted in Feature Requests)

Will we see this feature in 6.08.x? No big effort is needed as only one command line is added to the end of process!

Thanks.

smile

Ok, will deleteing "aticcc.exe" and "aticcp.exe" result in not working ATI drivers? In other words, what these .exe files do? Are they just accessories?

Good suggestion Siginet smile I'll try it.

What about the additional files in Graphics DriverPacks that can be safely removed. I read about it once but could not find it.

I'm not talking about making customs DriverPacks!! I'm trying to slim down the official DriverPacks!! For example, in Graphics A DP, I heard that some ATI controls can be deleted to gain some space.

Hi,

Thank you Bâshrat the Sneaky and others for your hard and amazing work in this project.

I prefer to have all official DriverPacks integrated in one CD. So, are there any auxiliaries that I can remove from DriverPacks.7z files? Such as trayicons, helpfiles, panels, etc.?

Regards.

23

(40 replies, posted in Other)

One html page with anchors on the top! KISS big_smile

24

(3 replies, posted in Other)

Thank you Helmi smile

How can we be 100% sure about this? Is Bâshrat the Sneaky around ?! roll

I'd like to know if a device ID (HWID) is the same on any computer the device is connected to. In other words, are these IDs built in hardware OR are randomly assigned by M$ Windows?

Thank you.