Perhaps I should clarify that... I will in the next version. wink

Please post your hwids. Check my sig for a tool to get them.

What method are you using?

1,679

(43 replies, posted in Other)

Hi everyone!

I thought it'd became time to let you guys know something... since you all seem to be wondering where I've been: some of you may think I'm dead, others might think that I've just stopped working on this endless project and again others may think I have gone gaga after switching to Mac.

Well, you're all wrong.

Truth is that I said I would be starting to work on the DriverPacks again around the 20th of June at the earliest. Unfortunately, my school seemed to have planned several things I did not know about. I didn't have the time to focus on the DriverPacks again.

Then I started my summer job, on July the 1st. Again busy. But I started coding nevertheless. One week later, I had finished a completely new 'finishing touch', now called 'DriverPacks Finisher'. In the past weekend I've modified the code for the GUI to be multilingual. And at this very moment I am further modularizing the GUI, to reduce the complexity of the code (which can truly be called complex and often far from straightforward, to accomplish certain things) and to allow for easily adding new slipstream modules.

Yes. That was/is the actual goal: new slipstream modules. But before doing so, I wanted to have the other code to be much more modularized than it is now. Once this is complete, I'll be able to add new platforms in the blink of an eye... kind of.

That last one, the modularization of the GUI, has proved to be more complex than I first anticipated... so it's taking a bit more time. But I think I can put the beta online by next wednessday, in exactly one week. I consider a beta as a necessity when there's such a significant change in the entire application.

Instead of spending alot of time on the forums, which is rather timeconsuming, it made more sense to me to just focus on coding the new features. And I'm sure you're going to like it smile

P.S.: yes, I did 'make the switch'! A MacBook Pro 17", with 2GB of RAM. That does not mean I'm swimming in the money like Scrooge McDuck: I've payed every single euro myself. I've had a nice discount, else this wouldn't have been possible. The major part is payed by the money I earned through the last summer jobs I had. But also a significant, yet minor part, was paid thanks to the people who donated to me. THANK YOU VERY MUCH!
This laptop will be extensively used for the next 4 years: for my studies. And of course for the development of the DriverPacks. Parallels runs smoothly with the 512MB of RAM I've assigned to it. The 2GB of physical RAM results in a very responsive system. This works so much more efficient! THANKS AGAIN!

Wim Leers

1,680

(3 replies, posted in Feedback and Support - DriverPacks Base)

On what hardware config is that? And especially the mass storage controller!

Well... a user of my DriverPacks found that that was the cause. That was more than a year ago I think. Because this problem only occurs very rarely, I guessed that that must be it. And you have those settings specified in your winnt.sif as well, so...

AFAIK it doesn't happen when the DRIVER is not available, but when the DEVICE is not available.

You could set up your IP settings AFTER setup completes. Would that be a problem?

larciel wrote:

Ok, so you want me to start from 'clean sp2' disc? or disc with all other Updatepack integrated, and then integrate your DP one by one?

fyi, I did not use DP_Mass for quite some time now.

With UpdatePack... since that's essential for you (and most people).

muiz wrote:

sommetimes a nforce4 chip needs older driver , i already told bashrat ( long time ago )

That 'sometimes' is VERY hard to detect. Do you still remember the mobo for which this was the case?

I knew it.

Remove these entries and it will work:

[NetAdapters]
    Adapter1=params.Adapter1

[params.Adapter1]
    INFID=*

[NetClients]
    MS_MSClient=params.MS_MSClient

[NetServices]
    MS_SERVER=params.MS_SERVER

[NetProtocols]
    MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]
    DNS=No
    UseDomainNameDevolution=No
    EnableLMHosts=Yes
    AdapterSections=params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]
    SpecificTo=Adapter1
    DHCP=No
    IPAddress=192.168.123.2
    SubnetMask=255.255.255.0
    DefaultGateway=192.168.123.254
    DNSServerSearchOrder=192.168.123.254
    WINS=No
    NetBIOSOptions=0

This only results in a restarting system if the NIC for which these options are set is NOT available. Or at least that's what has been concluded from the same problem in the past.

@midiboy, thanks for the HWID, I'll check it later.

@Amathar: ok, thank you for the confirmation. Now I only have to get it in... all languages. It's a hotfix on request so that won't be very easy I think.

NL President wrote:

Sure will see what I can do, didn't have much time for this project. But alway looking for a solution. When I'm at home (hopefully tonight) I will have a look and post the file.

Last week was pretty busy keeping some turbines up and running and had not much time to eat and sleep.

Tonight the story will continue hopefully also unattended,......

NL President

OK, no problem smile

Just don't forget to eat and sleep at all! wink

Well... you know too that I do not mess with any services, so I don't have the slightest clue by what this could be caused. I can only say that if you really want to narrow down the issue... you will have to do some extensive testing. I can understand if you don't want to.
Here's what you'd have to do: create a disc with only the Updatepack. Works? Ok, then add DP MassStorage (both text mode and normal (=Plug 'n Play)). Works? Ok, then add DP Chipset. And so on. You can also work in pairs or triplets if you want to... just use only a selection and extend the selection everytime it keeps working.

Fragbert wrote:

http://forum.driverpacks.net/viewtopic.php?id=22

Same issue. Labeled "solved" as well?

Bâshrat the Sneaky, did you look at the suggestion at the end of the thread?

I've now read that topic again and don't remember why I've set it to 'SOLVED', so I've set it to 'OPEN' again. Will try to reproduce this.

My reply however was relevant: this problem would ALWAYS exist if you were using the old DriverPack Chipset (any lower than version 6.05), since the directory structure has changed in DP Chipset 6.05.

I will now close this topic, please continue in the other one, as there's more useful information in it. Thank you.

The AMD K8 CPU driver was NOT installed?

Could you please post your HWIDs? Check my sig for a tool to get them.

Changed to 'OPEN', I don't remember why I had set it to 'SOLVED' about a month ago :s. I will try to reproduce this, which I already have tried, without success.

While going through all topics to be sure not to miss anything for the next update, I came also accross this topic and apparently I did not reply to the topic starter :s.

midiboy wrote:

Hi Bashrat,

here´s a few things that I noticed during todays installations using the latest packs available today:

Using method 2 by the way :-)

1. /USERPMTIMER switch was not applied to boot.ini on my AMD X2 PC. Is this supposed to work already or not ?

2. The ATI CCC was not installed altough I chose it during slipstream process.

3. Problem three in this thread:
http://forum.driverpacks.net/viewtopic.php?id=67

(HD Audio is left as a PCI device with ! mark in device manager) still happed with driverpack base 6.06. By the way ... the German version of the KB888111 installer was not accepted to fix the above problem, only the english version ...

4. Suddenly on my German Windows XP the "Hardware Upgrade Wizard" is in English !! This never happened before and it is a fresh new installation. No big deal but not really nice either ;-)

Other than that, great work as usual, keep it up please ! ;-)
Bye,
Alex

1.  Please post the HWID of your CPU (which is not exported by save_hwids.exe!), please use the DeviceManager to get it. It SHOULD be working, it's already included.

2. Well... is going to be solved.

3. Sereby's UpdatePack detection seems to be broken, though I do not understand why. I've already replied to that topic.
As for the incorrectly or incompletely installed KB888111: I don't have a clue. I hope it will be solved by solving the detection...

4. ERM......... LOL How in the world is this possible. You know as well as I do that I don't modify any of the Windows files that do not relate to installing files, so how this could ever be possible... don't know!

On a second thought, could I please see your winnt.sif file, NL President? (Remove your serial and use code tags please.)

@MickW: If it keeps flashing REALLY quick then it might be just ok... those windows are automatically closed, but it's possible that at given moments Windows finds unsigned drivers so quickly after eachother that the script that closes the Windows cannot keep up with it. So... don't worry about it.

Just give MakePNF.exe the time to process all the drivers and it should work just fine!


@HexiumVII: so far you're the only on whose system MakePNF.exe hangs, so perhaps it's an isolated case. If others can confirm the problem, I'll look further into it.

NL President wrote:

What is the filesize of Newdev.DL_ ?? I found it in the I386 folder and it is only 81 kb in size. Compared to Newdev_SP2.dll in the archive is much bigger 242 kb.

I'm facing some blue screens after installtion (not in safemode). So I will replace Newdev.DL_ in the I386 folder with Newdev_sp2.dll (renamed to newdev.dl_ ) wink

Let's find out what is going on this time, I'm getting a little frustrated by the blue screens.

Thanks so far,

NL President

It's compressed with CAB compression, that's why it's smaller wink

1,695

(4 replies, posted in Feature Requests)

You'll get access in the next update of the DriverPacks BASE, as I've told you through mail wink

Topic closed.

1,696

(5 replies, posted in Feature Requests)

muiz wrote:

please post in the API forum next time  (It's only visible to people who are part of the '3rd Party Developers' user group

api forum?

Only accessible for 3rd party software developers that use the DriverPacks BASE API.

1,697

(20 replies, posted in Feature Requests)

It's already available, but untested and the GUI isn't able to handle it yet. If you have a little more patience, there will be full support for it through the GUI! wink

Can you please post a transcript of the error, as the image isn't online anymore!

Xable's lite DP? What is that? You mean UpdatePack I guess? tongue

As far as I know, this can impossibly be caused by the DriverPacks. But as you're saying, it must be some kind of dark issue... veryyyy dark.

Perhaps it's also useful to tell us on which hardware configuration this is happening?

You were using 6.06.1 I presume? Could you please submit this issue at the bugtracker and attach your original svcpack.in_ with which the DriverPacks BASE had difficulties?

Please also post the HWID for that sound card.