Topic: [SOLVED] ATIIDE.SYS issue
if i use the text mode then during install the error comes up: ATIIDE.SYS cound´t find.
i use the actual base with all driverpacks included.
any help would great.
thanx mikel
- Wim Leers
- aka Bâshrat the Sneaky
- Offline
Re: [SOLVED] ATIIDE.SYS issue
Please post your DPs_BASE.ini and DPs_BASE.log. (And don't forget to use CODE tags please!)
Founder of DriverPacks.net — wimleers.com
Re: [SOLVED] ATIIDE.SYS issue
sorry i didn´t know how to use code tags :-(
Re: [SOLVED] ATIIDE.SYS issue
Click on link "BB Code", it will show you help about code tags.
Re: [SOLVED] ATIIDE.SYS issue
ok i will try it
[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"
[Settings]
; disc/bartpe/multibootDisc
instPlatform = "disc"
; trailing backslash is allowed, but not necessary
location = "J:\Image_F\xp_pro\test"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "GUIRunOnce"
; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "all"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "yes"
; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset = "yes"
DP_CPU = "yes"
DP_Graphics_A = "yes"
DP_Graphics_B = "yes"
DP_Graphics_C = "yes"
DP_LAN = "yes"
DP_MassStorage = "yes"
DP_Sound_A = "yes"
DP_Sound_B = "yes"
DP_WLAN = "yes"
DP_MassStorage_textmode = "yes"
; this section is optional!
[OptionalSettingsOther]
; CCC/CCP, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming DriverPack Graphics A)
ATI_cpl = "CCC"2006-09-02 15:07:17 : <INIT> DriverPacks BASE 6.08.6 initialized.
2006-09-02 15:07:17 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2006-09-02 15:07:17 : <INIT> Detected settings file "J:\Image_F\Bâshrat the Sneaky\DPs_BASE.ini".
2006-09-02 15:07:17 : <INIT> Windows XP Professional - OEM SP2 detected.
2006-09-02 15:07:17 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-09-02 15:07:17 : <INIT> Imported settings from settings file.
2006-09-02 15:07:17 : <INIT> Detected DriverPack Chipset 6.09!
2006-09-02 15:07:17 : <INIT> Detected DriverPack CPU 6.09!
2006-09-02 15:07:17 : <INIT> Detected DriverPack Graphics A 6.09!
2006-09-02 15:07:17 : <INIT> Detected DriverPack Graphics B 6.08!
2006-09-02 15:07:17 : <INIT> Detected DriverPack Graphics C 6.03!
2006-09-02 15:07:17 : <INIT> Detected DriverPack LAN 6.08.1!
2006-09-02 15:07:17 : <INIT> Detected DriverPack MassStorage 6.08!
2006-09-02 15:07:17 : <INIT> Detected DriverPack Sound A 6.08.1!
2006-09-02 15:07:17 : <INIT> Detected DriverPack Sound B 6.08!
2006-09-02 15:07:17 : <INIT> Detected DriverPack WLAN 6.08!
2006-09-02 15:07:17 : <INIT> Could not detect any 3rd party DriverPacks.
2006-09-02 15:07:17 : <INIT> DriverPacks scanned sucessfully.
2006-09-02 15:07:17 : <GUI> Initialized GUI.
2006-09-02 15:07:17 : <GUI> Created a list of all available language files.
2006-09-02 15:07:18 : <GUI> Set the last used language, English, as the GUI language.
2006-09-02 15:07:36 : <GUI> Refreshed UpdateChecker with success.
2006-09-02 15:07:38 : <GUI> Saved settings!
2006-09-02 15:07:38 : <GUI> Closed GUI.
2006-09-02 15:07:38 : <SEL> Selected module: mod_slip_wxp_x86-32_disc_m2.
2006-09-02 15:07:39 : <PREP> Removed all attributes from \I386.
2006-09-02 15:07:39 : <PREP> Created a backup of \I386\winnt.sif.
2006-09-02 15:07:39 : <PREP> Created a backup of \I386\txtsetup.sif.
2006-09-02 15:07:39 : <PREP> Created a backup of \I386\dosnet.inf.
2006-09-02 15:07:40 : <PREP> Cleaned up \$OEM$\cmdlines.txt.
2006-09-02 15:07:40 : <PREP> Created temporary working directory.
2006-09-02 15:07:40 : <SLIP> Extracted necessary files for method 2.
2006-09-02 15:07:40 : <SLIP> Created necessary directory structure for method 2.
2006-09-02 15:07:40 : <SLIP> Copied files necessary for method 2.
2006-09-02 15:08:11 : <SLIP> Copied DriverPacks to \OEM.
2006-09-02 15:08:11 : <SLIP> German (Sereby's) UpdatePack detected: no HDA hotfix will be slipstreamed.
2006-09-02 15:08:11 : <SLIP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2006-09-02 15:08:12 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2006-09-02 15:08:20 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2006-09-02 15:08:21 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2006-09-02 15:09:07 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2006-09-02 15:09:16 : <SLIP> Compressed setup.exe to SETUP.EX_.
2006-09-02 15:09:16 : <SLIP> Created \I386\presetup.cmd file.
2006-09-02 15:09:16 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2006-09-02 15:09:16 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2006-09-02 15:09:17 : <SLIP> Updated \I386\winnt.sif to support method 2.
2006-09-02 15:09:17 : <SLIP> Updated DPsFnshr.ini to enable KTD for all DriverPacks.
2006-09-02 15:09:17 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2006-09-02 15:09:17 : <SLIP> Slipstream finished in 1 minutes and 38 seconds.
2006-09-02 15:09:19 : <CLNP> Temporary working directory successfully deleted.
2006-09-02 15:09:19 : Program terminated.Re: [SOLVED] ATIIDE.SYS issue
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.
- Wim Leers
- aka Bâshrat the Sneaky
- Offline
Re: [SOLVED] ATIIDE.SYS issue
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?
Founder of DriverPacks.net — wimleers.com
Re: [SOLVED] ATIIDE.SYS issue
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 .
- Jaak
- Old Timer Rookie
- Offline
Re: [SOLVED] ATIIDE.SYS issue
hi
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?
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- Jaak
- Old Timer Rookie
- Offline
Re: [SOLVED] ATIIDE.SYS issue
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..
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- Wim Leers
- aka Bâshrat the Sneaky
- Offline
Re: [SOLVED] ATIIDE.SYS issue
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?
Founder of DriverPacks.net — wimleers.com
Re: [SOLVED] ATIIDE.SYS issue
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 ..
Last edited by mikelm (2006-09-03 09:27:11)
Re: [SOLVED] ATIIDE.SYS issue
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
Last edited by mikelm (2006-09-03 09:53:57)
- Wim Leers
- aka Bâshrat the Sneaky
- Offline
Re: [SOLVED] ATIIDE.SYS issue
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.
Founder of DriverPacks.net — wimleers.com
- Jaak
- Old Timer Rookie
- Offline
Re: [SOLVED] ATIIDE.SYS issue
ah
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.
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- Jaak
- Old Timer Rookie
- Offline
Re: [SOLVED] ATIIDE.SYS issue
aha, I see the edit.
sereby on a clean one, and DriverPacks after that worked...
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
Re: [SOLVED] ATIIDE.SYS issue
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
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 ...
- Jaak
- Old Timer Rookie
- Offline
Re: [SOLVED] ATIIDE.SYS issue
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.
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- Wim Leers
- aka Bâshrat the Sneaky
- Offline
Re: [SOLVED] ATIIDE.SYS issue
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.
Founder of DriverPacks.net — wimleers.com