Nugzo Posted November 14, 2005 Posted November 14, 2005 After installing Xpize i can no longer slipstream bashrats driver packs. Uninstall Xpize and all is well.
Bâshrat the Sneaky Posted November 14, 2005 Posted November 14, 2005 After installing Xpize i can no longer slipstream bashrats driver packs. Uninstall Xpize and all is well.ONE word:impossibleP.S.: first slipstream XPize, then the DriverPacks. Everything should work alright.
Nugzo Posted November 14, 2005 Author Posted November 14, 2005 (edited) 2 wordsNot ImpossibleI made an unattended with driver pack. all works well. i am trying to now slipstream driver pack into Home OEM and Pro OEM. When i run the BTS_DPS_slipstreamer_V5115 it doesnt do anything. it doesnt create the UWXPCD_Root or do anything. the cmd window opens then closes. This is with Xpize installed. If i uninstall Xpize, then the BTS_DPS_slipstreamer_V5115 works normal. ive tried this on 3 fresh windows installs. Same results. This was with Xpize 4.0. I just tried 4.1 and it works as intended. The issue seems to be fixed now. Edited November 14, 2005 by Nugzo
Nugzo Posted November 14, 2005 Author Posted November 14, 2005 I spoke to soon. The slipstream worked, but now the Run_me doesnt work, just opens CMD Window then it closes and nothing else happens. Same as the Slipstreamer did. I uninstalled xpize and now it works like intended.
Nugzo Posted November 15, 2005 Author Posted November 15, 2005 It appears that the cmd line color tweak is causing my problem. if i install xpize without this tweak i can slipstream drivers fine.
laurens Posted November 15, 2005 Posted November 15, 2005 its look like that more people have this problem. but its not a bug of the program that Bâshrat the Sneaky create. its a bug of XPize so send a message to him.
Nugzo Posted November 15, 2005 Author Posted November 15, 2005 I didnt think the driver pack was the problem, thats why i posted in the Xpize section.
XPero Posted November 15, 2005 Posted November 15, 2005 It is not an XPize bug. It is a Windows limitation. Simply dont install the command line colors mod and problem solved.
Nugzo Posted November 15, 2005 Author Posted November 15, 2005 If windows cant run it properly or its a limitation, why include it in the program? It caused me hours and hours of aggravation. Dont take this the wrong way, I Love your program, just my opinion.
maybeme Posted November 16, 2005 Posted November 16, 2005 Had the same problem. I now just use the /nocmd switch in my uacd. Maybe it's a good thing to make a thread with known difficulties such as this, and powerdvd and ...grtz
XPero Posted November 17, 2005 Posted November 17, 2005 Had the same problem. I now just use the /nocmd switch in my uacd. Maybe it's a good thing to make a thread with known difficulties such as this, and powerdvd and ...grtzWhat if you look in the Support page in the XPize site? Also I include this because not everybody has problems with the modified console. You have the choice, and thats the important thing.
Wesmosis Posted November 23, 2005 Posted November 23, 2005 yeah kinda don't like the xpized CMD window, the old BLACK is a tradtional thing and historical:) no offense
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now