2,226 Reply by Jaak

(19 replies, posted in News)

Hi
when sil 3132 is active, I no longer get BSOD.
I could not update the onboard chip to a more recent ROM, but it no longer causes a BSOD, and I can use it as storage.

At the moment, I am trying to set up to it, in a RAID array on the SIL 3132.
(using Ruud's latest custom pack, on request)
With a single drive, that did not work, Muiz and Ruud know this, as I was testing Ruud's customised packs.

Pleasant note, with the released version, I did not get BSOD either.

I may have more news in an hour or so..
Glad to see so many issues gone..

Go to forum: News

2,227 Reply by Jaak

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

Hi ShadowBlade

I agree.
I would add my own suggestion, and that is simple too.
When a new mass storage pack comes out, DPs_Base has to be a new version..
In between new mass storage packs, it could be a good idea to allow people to get the older base that works with the published driverpacks.
New visitors would then be able to get a version which was known to work for many..
(For instance, some newer members were told to get base 8.06.8, but they cannot get to it..)

it's a thought, might work too, like oldversion dot com.. smile

Go to forum: Feedback and Support - DriverPacks Base

2,228 Reply by Jaak

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

Hi BigBrit
textmode drivers are not processed.
there ought to be a fix soon.

I believe Helmi reported that if you did that with QSC filled with the files from your previous (610 or 612), that the process did what it had to do. ( Well, he had not noticed the error because the folder with content was in placeas he had replaced an earlier base...)

Hmmm, I have not tried that myself...

Go to forum: Feedback and Support - DriverPacks Base

2,229 Reply by Jaak

(102 replies, posted in DriverPack Mass Storage)

thanks, just got home from work, and this saves me some editing and time doing tests..

Go to forum: DriverPack Mass Storage

2,230 Reply by Jaak

(102 replies, posted in DriverPack Mass Storage)

so, if i remove these 3ware, Repack, and test on the Gigabyte royal wich has that sil 3132, I could be of help?
(this did a BSOD too... see)

note, the royal also has a Jmicron chip.. did that no have issues of its own? I sorta forgot.

Go to forum: DriverPack Mass Storage

2,231 Reply by Jaak

(18 replies, posted in Translations Team)

didn't even have the chance to RUN 7.01... smile
hehe, it"s a Good thing I checked before I started making builds.

Go to forum: Translations Team

2,232 Reply by Jaak

(4 replies, posted in Hardware)

updated fdisk, that is fdisk found in millenium floppy.

edit;
if you want to use drive manufactor's diskmanager, and do not know the make of the drive, I can recommend another little tool
DUGIDE
http://www.cybertechhelp.com/download/s … management

this will tell you the maker and a lot more
you can then go to their website, and get a disk manager, which will work a lot faster than fdisk and format..

Go to forum: Hardware

2,233 Reply by Jaak

(4 replies, posted in Hardware)

http://www.cybertechhelp.com/download/file/wipeout

put this on a windows 98 bootdisk, and use it
the description on the site should be changed, this tool does no more than wipe partition table in one move
the readme in it was re-written by your truly...

WARNING
The use of WIPEOUT can and will result in the loss of ALL data on your hard drive.

This tool sets a harddisk with a blank table, with all partitions gone off it.
You will not see remainders of bootstrap calls left by antivirus or other utilities.
Traces of overlay are gone too.
It does it really fast, and in one step.

DIRECTIONS for use with a single drive

1- Unzip file
2- Copy WIPEOUT to a Win9x boot disk
3- Boot with Win9x disk
4- At the A:\> type "wipeout c: /nq /np" (no quotes)

/nq = no queries - you will not be asked if you are sure.
/np = no partitions - this will overwrite the MBR



=================================================

Maybe you want to use this in a machine with more than one hard disk...

Wipeout has a little peculiarity.
the hard disk fdisk /status reports as drive 1 is called C: by wipeout.
(no matter what letters drive 1 actually contains)

the hard disk fdisk /status reports as drive 2 is called D: by wipeout.
(no matter what letters drive 2 actually contains)


1- Unzip file
2- Copy WIPEOUT to a Win9x boot disk
3- Boot with Win9x disk
4- FDISK /STATUS
make a note of the numbers the harddisks have been given, and the drive letters the partitions on the harddisks have been assigned.
5- exit fdisk

As noted, the NUMBERS FDISK gave correspond with LETTERS in WIPEOUT
C: is drive 1
D: is drive 2
E: is drive 3
F: is drive 4

LET us suppose you want to zap the partitions off harddisk 2

6- At the A:\> type "wipeout d: /nq /np" (no quotes)

/nq = no queries - you will not be asked if you are sure.
/np = no partitions - this will overwrite the MBR

Just a reminder, for drives larger than 64 Gigabyte, use the updated fdisk.

Go to forum: Hardware

2,234 Reply by Jaak

(19 replies, posted in DriverPack Mass Storage)

sad
yes, old faithful triggered a BSOD on me on a live test today.
base6.12, with mass 6.08 was tried on a machine that has sil 3132 and a jmicron inside.
And it failed.

funny thing is, when I used the slipstreamed disc I made in september (base 6.086 with mass 6.08 and chipset 6.091), that this installed just fine. The silicon raid tool showed in CP..

I had better pull the drive, and get the setup error log off it.. and maybe see what triggered it.

I'll test the mass 6.11 beta in there after that.

Go to forum: DriverPack Mass Storage

2,235 Reply by Jaak

(9 replies, posted in DriverPack LAN)

hi
looked in older packs, and these did not have RTL1868 driverfile for win2000 either

I found the drivers here (xp/2000/x64 etc are in version 658, the 151Kilobyte zip is what I looked at )

ndis5x-pcie(658).zip

http://www.realtek.com.tw/downloads/dow … wn=false#1

Go to forum: DriverPack LAN

2,236 Reply by Jaak

(9 replies, posted in DriverPack LAN)

it is in the 2000 section..
in the XP section, it goes for RtenicXP.sys

are you installing XP or 2000?

Go to forum: DriverPack LAN

2,237 Reply by Jaak

(5 replies, posted in Other)

famous words by "dingers"
uuk e geleukig niefjoar ey?

>> "woa zin min tanden?" <<

Go to forum: Other

2,238 Reply by Jaak

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

another thanks,

I wondered how come the answerfile I made for somebody did not fill in the user.
I had used Nlite to make it
(because it was for a friend living abroad, different timezone etc, etc, I used Nlite rather than editing a "stock" copy I use for Dutch versions.)

so that was the reason...

Go to forum: Feedback and Support - DriverPacks Base

2,239 Reply by Jaak

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

Hi
thanks

did you download the updated RVM hotfix pack 215a?

Go to forum: Feedback and Support - DriverPacks Base

2,240 Reply by Jaak

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

hi
RVM has a very recent fix in updated release 215a

I've seen Nlite break base slipped sources one too many times.
I won't go try use it as last of the preparing right now. When new releases come out, maybe.
Don't use NLite for packing Bâshrat the Sneaky driverpacks, it cannot handle these packs.

what graphics card is in there?

Go to forum: Feedback and Support - DriverPacks Base

2,241 Reply by Jaak

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

the other question
donators, testers, translators and coders have been able to look at source files since this went open source.
I think devpath is by M$, so you would not find the source for that.

are you an AUTOIT user?

Go to forum: Feedback and Support - DriverPacks Base

2,242 Reply by Jaak

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

hi

did you run DPs_base while there was a winnt.sif of your own in 386 folder?

Go to forum: Feedback and Support - DriverPacks Base

2,243 Reply by Jaak

(9 replies, posted in 3rd Party DriverPacks)

hi

No offence meant, but this is funny..
x86-32 already tells me it is for 32 bits.

64 bit drivers would have AMD-X64 or x86-64 in the name?
those I saw at 3rdparty here used x86-64

Go to forum: 3rd Party DriverPacks

2,244 Reply by Jaak

(22 replies, posted in DriverPack Graphics)

remind me to email u couple days from now.
I had a LOT on my plate too.

Go to forum: DriverPack Graphics

2,245 Reply by Jaak

(22 replies, posted in DriverPack Graphics)

hi
I will ask Dave Wills a few questions in our modroom, and hope to get him or other web designers interested enough to share tips, tools, and tricks.
siginet and Rougespear may know a lot too, but Mr Wills is a genius at this.
he is the founder of cybertechhelp

Go to forum: DriverPack Graphics

2,246 Reply by Jaak

(23 replies, posted in DriverPack Mass Storage)

you convinced me.
looked at the buy now pages, has lifelong updates too. smile

I thought DPs_Base won't have problems with read-only files. FAIK, it resets them.

I wonder wether Stoph solved his problem by putting the OEM folder in the ISO...

Go to forum: DriverPack Mass Storage

2,247 Reply by Jaak

(23 replies, posted in DriverPack Mass Storage)

we can learn a lot by sharing methods...I am all ears!


I have not used ultraIso yet..  sad
I have used winimage (which can edit ISO to do what you do), isomaker (whis is quite limited), nlite, and RVM integrator because the better tools could not do over 300 Mb in trial mode..

So, why did I use Isobuster?
One major thing I tried was this MSDN DVD which has Five different OSes on it, and that would not work with the bootloader one finds on the net, or got off an XP pro, or is present in RVM and Nlite.

fwiw, the first specialised bootloader I ever made was for windows 98se.
The next was just a rip from xp pro and this year i did that msdn DVD.

I'll look up where I can get UltraIso... because the ISO making/editing tools I used cannot do that msdn properly.
(which is why i had to first make the DVD, and then make an ISO of it.)

I started using VPC about a month ago. Before that, I had no need for tools that MAKE ISO files.

Go to forum: DriverPack Mass Storage

2,248 Reply by Jaak

(23 replies, posted in DriverPack Mass Storage)

OOPS

hehe, I jumped straight to last post....
I usually do not make an ISO before burning.
I use NERO burning Rom, and what I do is simple.
copy the sourse
slipstream the copy
get boot image off the source using ISOBUSTER
use nero, tell it where the boot image is
set sectors to 4, NO floppy emulation
drag the slipstreamed source into the compilation
(you can omit valueadd, and the Migration folders in 386 can go too)
burn

live test, if OK, this burn is then used to make an iso of.

when I first make an ISO from a folder, I also use the original boot image which I get off the source.
(because I did some experimental stuff I had to stick to original boot images. you can use RVM or NLite to build a bootable ISO from the slipstreamed source.)

Go to forum: DriverPack Mass Storage

2,249 Reply by Jaak

(23 replies, posted in DriverPack Mass Storage)

hi
I have not looked up what zac-az wrote.

but, based on what you write....
I think you missed the OEM folder.

Go to forum: DriverPack Mass Storage

2,250 Reply by Jaak

(33 replies, posted in Other)

hi

EDIT april 2008
this tool works.
http://forum.driverpacks.net/viewtopic.php?id=2403


WELL;  what you read here..  is educational, but it didn't work.
----------------------------------------------------------------------
this has been asked before, and this is a rewrite about doing drivers on CD (or DVD).

Suppose you have a testrig in which you regularly change devices for you have to see wether they still work.
It runs XP which you do not want to reload.
It would be nice to have a large collection of devicedrivers ready on the drive.
Well, one can do something quite interesting.

what does one need...
1; one or two little cmd files one creates for oneself
2; a source you slipped with base, using method 2 (the source will then contain the files.)

SCRATCH THIS.
NOT NEEDED. 3; 7zip. (for unzipping a file needed for the doPNF.cmd method.)

and then, how it works
copy the OEM folder from the slipstreamed source to a CDRW
create a little batchfile (or create both) and copy that to that CDRW
(one can, of course, put the batch files and those you extracted on a slipstreamed source..)
--------

Dopath.cmd works very simple
It extracts the files from the slipstreamed DVDRW into a folder in windows.
devpath then tells windows the files are there, ready to be searched when hardware is added.
You have to hit "use anyway" when you run hardware wizard and it turns out the driver is not WHQL signed.

doPATH.CMD

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:
%CDDRIVE%\OEM\BIN\7z.exe x -y -aoa %CDDRIVE%\OEM\DP*.7z -o"%SystemRoot%\DriverPacks"
%CDDRIVE%\OEM\BIN\DevPath.exe %SystemRoot%\DriverPacks
exit

The other method takes longer to apply because makePNF installs the drivers into the windows INF section.
The result is that windows does not bug you with driver is not signed.

UPDATED.

Go to forum: Other