DriverPacks.net Forum - [SOLVED] ATIIDE.SYS issue

Re: [SOLVED] ATIIDE.SYS issue

2006-09-03T09:18:10Z

jtdoom, all of that is most definitely NOT necessary. During the initial beta testing it was a good thing to do, but now it's definitely useless.

@mikelm: What you describe (not remembering the settings for DriverPack MassStorage text mode and QuickStream Cache), is impossible - UNLESS you've opened the DPs_BASE.ini with a text editor that's using a write lock. You can ask any one on the forum, but you're definitely the only one with that problem. You must be doing something wrong, probably without realizing it - and that's something that happens to every one once every while.
You could try Unlocker to find processes that have locked the DPs_BASE.ini.

Re: [SOLVED] ATIIDE.SYS issue

2006-09-03T00:28:53Z

Hi
I think one can avoid trouble by working with fresh folders.

When I ran the betas and release candidates and encountered a problem with one method, I would save the logs to a folder.
Then I deleted the entire content of DriverPacks folder, and unpacked the Base download to it all over again.
This created fresh base files.
Then I'd copy the driverpacks into the driverpacks subfolder, and also copy the source files to a cleaned out folder.

When things improved, I did some trials with sources I had done another method DriverPacks slipstream on.
But when I bailed out DURING a slip (lets say because I saw the path limit was exceeded), I would usually start anew, using fresh content in the folders.
I thought I'd better spend four minutes loading a fresh copy, than waste 50 minutes while running a trial setup that got botched because I made it difficult for the slipstream process.

all in all, DPsBase detects quite a few things that happened previously.
I often wondered wether I had more luck than others.
I also made sure I had plenty room on the hard disk.
((after twenty trials or so I had less than 28 Gb free on a 160 partition, so I moved 90 giga to another drive.. ))

I think you must have at least ten percent free room (a windows annoyance), plus 2 giga for the temps, so twenty percent free room is better..

I don't think folder permissions would be an issue here.

if it can not create the DPs_Base.ini, you might try unpack 6.08.6 in a fresh folder, and try again.

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T22:51:06Z

now it seems to work , bu i didnÂ´t change anything ..

i only delete QSC folder, all iniÂ´s and logs and make an new BTSinit ...

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T22:42:01Z

no all the time the last config was not remembered fully.. every time i must disable or enable textmode drivers.

and also i every time cleared the QSC folder but this not works ...

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T22:27:41Z

aha, I see the edit.
sereby on a clean one, and DriverPacks after that worked...

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T22:25:34Z

Sereby's is like a copy of RVM's integrator in German...
I would not know wether there are bugs left in either one.

in RVM's integrator, you must click advanced, to enable the unicode to ANSI tool.
I would imagine this is the same in Sereby's.

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T22:11:54Z

The last configuration is automatically remembered... I don't see how that could not work.

And then please DELETE the directory I mentioned. Then slipstream again. The QuickStream Cache will now have been rebuilt and it should be a valid one this time.

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T22:06:12Z

ok some testing results:

1. with a pur xp pro sp2 now it works...

2. with a pur xp pro sp2 + serebyÂ´s it works too

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T21:52:58Z

there are only a file like 3k.. something in it , and i didÂ´t interrupte anything during slipstreaming ..

the error can be reproduced any time ..

i used a blank xp, then i put serebyÂ´s updatepack , then i make changes with nlite and at least i use Bâshrat the Sneaky with M2

did u have icq ore msn ? this would be easier to communicate and find the problem ..

the other question i have is why the base programe forget every time i started it all the konfiguration? every time i must set all information new. which driverpacks an anything else ..

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T21:48:42Z

Hmmm.... I think you have once cancelled the slipstreaming process while it was creating a QuickStream Cache for DriverPack MassStorage text mode. That would explain the missing files. Could you please exist if there are ANY files in the directory

QSC\wnt5_x86-32_uni_DP_MassStorage_608_textmode

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T21:47:12Z

I wonder wether this could be caused by running it on a previously used source

it looks like it had a method 1 done on it before, and/or sereby's
(which I have not used before)

the M2 I just did was done on a source where the hotfixes were slipped in with RyanVM integrator, and the last six versions I did like that gave no error whatsoever..

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T21:37:37Z

I just ran a method 2 slip, (all packs..)

ALIIDE.org and ALIIDE.SY_ are both present here.

this makes me think you don't see the file, even when it is there...
in windows, how are folder options set?

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T15:56:13Z

so i found out that the textmode driver komplette missing in the i386 folder.

i only found an ALIIDE.ORG in the i386 no aliide.sy_

i also couldnÂ´t believe that there is a difference between uppercase and lowercase during instal

have you msn oder icq so is it easier to communicate .

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T15:30:22Z

ironside wrote:

When i had this issue the atiide.sy_ was in lower case in the i386 folder.
Converting the files in the i386 to UPPERCASE will fix it but having said that the latest DP base should do that for you automatically i dunno why it did;nt for you.

That could indeed be the cause. But it should be UPPER case automatically now... Could you please verify that, mikelm?

Re: [SOLVED] ATIIDE.SYS issue

2006-09-02T14:37:42Z

When i had this issue the atiide.sy_ was in lower case in the i386 folder.

Converting the files in the i386 to UPPERCASE will fix it but having said that the latest DP base should do that for you automatically i dunno why it did;nt for you.