janrockt

Member
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About janrockt

  • Birthday 01/31/1986

Contact Methods

  • Website URL
    http://
  1. welcome! first slipstream the driverpacks, their run command will automatically be set in cd\i386\winnt.sif . then copy your wpi folder into the cd root and download a prepared $OEM$ folder from the official wpi website: http://wpiw.net/The_Dark_Side/files.html of course you can also youse your own cmdlines.txt by adding an entry to it and pasting the runwpi.exe in your $oem$-folder as explained under the link above.
  2. installation "worked" only with deactivated realtek changes. same problems as already mentioned, textfiles can not be opened too. next time i use a vm
  3. do not rush yourself! some people do not even believe in a new version of xpize so you have all time to get your work done i do not think that anybody will be dissapointed if it comes out some weeks later.
  4. xpize darkside changed the default desktop theme onboard, you can install your favorite. the old one was luna royale and i prefered it, too. luna element black is another alternative.
  5. wrong. this basic software is fresh and it is on the road to xpize 5. the last soonest date für a testing version was mentioned as the middle of february, so just be patiently.
  6. is there something new concerning status and first testing release? will we perhaps have another gift under the christmas tree?
  7. i would be pleased! i have three older pcs and 3 almost up-to-date notebooks (not all mine but i manage my brother´s it-stuff). windows xp sp3 prof and vista business, perhaps even x64 if my school gives me a license. experience with virtualbox, nlite (so i often reinstall my os ). codeplex account has been created (janrockt). i hope my english will be good enough to form my thoughts into words!
  8. how is the progress? or are you waiting for the new xpize before you continue?
  9. i did not use the 'product as subfolder'-option, only the 'category as subfolder', works fine now.
  10. thanks! sounds thoroughly understandably. but when i think about the popularity of this option to remove replaced updates i wonder why it seems to work for other users..
  11. erm..no. first it was an external harddrive, but reading the log i thought about security settings with removable drives and i copied the wud-folder to my normal harddrive. it was no solution. everything works fine without this box checked.
  12. very nice program, but this errorlog happens when i check the "remove unlisted files"-box: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.UnauthorizedAccessException: Access to the path 'G:\XPCD\Extra\Tools\WUD\ICSharpCode.SharpZipLib.dll' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.Delete(String path) at WUD.formMain.removeUnlistedFiles(String folder) at WUD.formMain.buttonDownload_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.226 (QFE.050727-2200) CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- WUD Assembly Version: 2.25.895.0 Win32 Version: 2.25.895.0 CodeBase: file:///G:/XPCD/Extra/Tools/WUD/WUD.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.233 (QFE.050727-2300) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.221 (QFE.050727-2200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- ICSharpCode.SharpZipLib Assembly Version: 0.85.1.271 Win32 Version: 0.85.1.271 CodeBase: file:///G:/XPCD/Extra/Tools/WUD/ICSharpCode.SharpZipLib.DLL ---------------------------------------- System.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.231 (QFE.050727-2300) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.226 (QFE.050727-2200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Web Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.210 (QFE.050727-2100) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. is it a bug or just a problem with my configuration?