Jump to content

Phoenyx

Member
  • Posts

    19
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Brazil

Everything posted by Phoenyx

  1. KB890830 -› Microsoft® Windows® Malicious Software Removal Tool V1.2 (3/8/2005) http://www.microsoft.com/downloads/details...b3-75b8eb148356 REG ADD "HKLM\SOFTWARE\Microsoft\RemovalTools\MRT" /v "Version" /t REG_SZ /d "F8327EEF-52AA-439A-9950-CE33CF0D4FDD" /f
  2. Bâshrat, Without setuporg.exe and presetup.exe the installation under winnt32.exe is paralyzed in false setup, or either, of nothing it advances the additions of drivers mass storage in dosnet.inf in version 5.03. How much to siside.sys, it is accurately this. Therefore in all the tests executed here I got success.
  3. Well, as you say yourself, it's only required for the winnt32.exe initiated installation. Currently I had not yet added support for that (however I should ). Thanks for listing everything here Will be added as well! Bâshrat, Without setuporg and presetup the additions in dosnet.inf do not advance in much thing. How much to siside.sys, you it could only have removed its information of txsetup.sif, keeping it in the package mass storage, resembling it the employed method to drivers PATA of the nVidia, being installed later. Bye.
  4. Hi Bâshrat, I come here to ask for one more time that it removes all the information on the SISIDE.SYS in the Drivers Pack Base, leaving it only in the package Mass Storage. This because conflicts exist, and since it is about driver PATA does not have an immediate necessity for its installation. In the second stage of detection of hardwares(Ethernet, Graphics, etc), it is installed normally. Another thing, such archive also is used by others chipsets SIS, as the 745, then strings for "SIS IDE UDMA Controller" would be better to rename its. Another thing, I also noticed that you still it did not place information on the installation saw WINNT32.EXE. I want to remember to it that beyond drivers Mass Storage it is necessary to list SETUPORG.EXE and PRESETUP.CMD in DOSNET.INF, contrary case the installation is congealed in fake setup. Below I cite my insertions: (Already without the SISIDE.SYS) Finally, I want to ask a thing to it, beyond the problems with drivers nVidia(removing nvatabus.sys of txtsetup.sif and leaving driver only in the package Mass Storage to be loaded later, as in the case siside.sys, the problem could be solved?), exists plus some? 3ware total was solved? In time, I possess plate A7N8X Deluxe, obviously based in nForce II, if to need some aid is alone to say. Bye.
  5. SHRINK.INI converted for the Portuguese of Brazil: I wait that it is of some utility. With me, everything functioned perfectly. beppemito, is enough to convert SHRINK.INI for its version: [Language] lang=Italiano dir=1040 retry=&Altra prova ??? title=Microsoft Office error=Errore Bye.
  6. Unpacking the driver pack I perceived that folder AT(probably destined when driver Atheros) is empty. Why?
  7. I also perceived this, but worse i386 is the archives SYS in the directory. It is necessary to erase them, as well as in case ULTRA.SYS, therefore of the the opposite the compression of the new archives for this directory will be aborted. Not to lose time, discovering which were the archives in duplicate, I twirled this CMD before applying them: Using to advantage, Bâshrat, reason you did not suppress archive SISIDE.SYS? It brings problems in older boards, with chipset SIS 5513 and 5518. Moreover, it also is installed for others, as for example SIS 745. I recommend that it removes it "only" of txtsetup.sif/dosnet.inf, beyond, obviously, of archive SYS in the directory i386, and nominate its string in the SISIDE.INF for "SiS IDE UDMA Controller". Of this form it will be loaded later, but he will not bring conflicts to the cited boards. Hum, other small problems, found in the your TXTSETUP.SIF: and:
  8. Not enclosed Intel SATA RAID? http://www.msfn.org/board/index.php?showto...ndpost&p=233489
  9. Stranger, therefore has some months behind executed the same procedure (CC_0104 only in 3112R) and everything functioned perfectly in my A7N8X Deluxe 2.0, believes I who its A7N8X-E uses the same identification.
  10. I unmasked the mystery and I solved it temporarily. It is the following one, the SETUP.EXE modified for the Pyron does not function in this phase. For that I perceived, it does not obtain to launch the PRESETUP.CMD(I corrected my previous error). Solution: I called the original SETUP.EXE in its place, of this form: Comment: I erased the SETUP.EXE that is in 2º [Files]
  11. Well, in mine in case that the problem occurs in the installation on Windows XP, probably in the too much versions the same it must happen. But I have given interesting... I added the system archives to the DOSNET.INF and now they are loaded. Of any form the installation does not continue, after first reboot the operation enters in looping, restarting and restarting the computer. I believe that this must to the SETUP.EXE that is not more the true one. I added then the archives SETUPORG.EXE and PRESETUP.CMD in the DOSNET.INF, but I did not get success, everything continued in the same one. Ah! It was forgetting me, really a conflict in the system occurs using driver SISIDE. I made the test in a M590 plate of the PC-Chips, which takes south bridge 5513. It removes this to driver of its package, is better that the user instalale it later. Edit: Ooopss... Only now, after quote, I perceived that I placed PRESETUP.EXE instead of PRESETUP.CMD. I will make the correction and I will try one more time, desire luck to me.
  12. Debtor for the reply. But then, the system archives(sys) had been all compact for the directory i386, the only stage that did not follow were the compacting of the folder Drivers. But as it said previously, everything functions well in boot clean for the CD(proves of this is the occured installation in HD SATA), the problem is when I only want to make an update in the system, inside of the Windows.
  13. Hi to all! I am having a strange problem for here, most interesting well is that I did not find a story similar. Making a upgrade in the operational system, or either, keeping the current configurations after the installation, occurs a stop: "aec6280.sys was not found" I could verify, all the system archives mass storage are not found. Summarizing, the clean installation, for boot of the CD, occurs perfectly, error-free, recognizing my Sil3112r controller, ethernet adapters and all more. Now, bringing up to date the version of the operational system, the installation is aborted by the described errors above. PS: Method 2 for the integration, but without the compacting was used. Until soon, and I am grateful since already to who will be able to assist me.
  14. They disrespect this message, I found the steps for the insertion of the SI3112R device string described for iSmart. Debtor. I will make now slipstream it, getting success or not, I will bring notice. Again, they forgive me for my poor english. Until soon
×
×
  • Create New...