Okay, I'll fix those theme packages as well. Do those packages have the System control panel applet issue with the image in the Remote tab missing?red,blue, and purple also have no display area in the applications tab.
also, clicking on perfprmance tab locks up task manager.
thanks
RR
XPtsp GUI v3.0.0.26 - February 27, 2012
Started by
dougiefresh
, Jan 29 2009 11:54 PM
662 replies to this topic
#641
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 29 November 2011 - 12:53 AM
#642
phasma
-
- Members
-
- 2 posts
Lurker
- OS:Windows XP Pro
Posted 29 November 2011 - 02:28 PM
XPtsp v3.0.0.22
I used black with original.extra and have same problem with taskmgr...
however, no issue with System control panel applet with the image in the Remote tab.
I am also getting this AutoIt Error at boot:
Line 3031 (File "C:\Program Files\XPtsp\XPtsp.exe"):
Error: The requested action with this object has failed.
TaskBar says: "Repatching 1 file."
I believe it is because System Restore is disabled on my system.
I have never used it and don't ever plan on it...
if that is the case though, is there any away to have it check before trying to do a
System Restore point?
Also, I hope this helps to perfect the code...
I used black with original.extra and have same problem with taskmgr...
however, no issue with System control panel applet with the image in the Remote tab.
I am also getting this AutoIt Error at boot:
Line 3031 (File "C:\Program Files\XPtsp\XPtsp.exe"):
Error: The requested action with this object has failed.
TaskBar says: "Repatching 1 file."
I believe it is because System Restore is disabled on my system.
I have never used it and don't ever plan on it...
if that is the case though, is there any away to have it check before trying to do a
System Restore point?
Also, I hope this helps to perfect the code...
Spoiler
Edited by phasma, 29 November 2011 - 11:35 PM.
#643
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 14 December 2011 - 09:19 PM
What's Changed in v3.0.0.23:
- Updated Reshacker to v3.6.0.
- Fixed CAD 2009 background replacement issue that phasma found.
- Replaced System Restore creation code with code that calls SRCLIENT.DLL directly. (Issue found by phasma)
- Fixed several incorrect entries in XPtsp.ini that phasma found.
- Removed code responsible for selecting different Task Manager themes.
I've been working a lot of hours lately and haven't been able to respond in a timely manner lately....
I've replaced the System Restore code in the GUI with a system restore UDF. The UDF calls the SRCLIENT.DLL instead of making object calls, so it shouldn't crash AutoIt should it fail to create a System Restore point. As for how to detect whether System Restore is actually present, I don't really know how to do that. I've modified the GUI to check for the SRCLIENT.DLL file, and if it present, to present the option to do so. Hopefully, that'll be enough to prevent something bad from happening
I looked at the spoiler and you're quite right: The code for the CAD 2009 background replacement was wrong. I've fixed that error in the code. Also fixed the XPtsp.ini as requested, as that's not right, either. I'll fix the CAD2009 add-on shortly....
- Updated Reshacker to v3.6.0.
- Fixed CAD 2009 background replacement issue that phasma found.
- Replaced System Restore creation code with code that calls SRCLIENT.DLL directly. (Issue found by phasma)
- Fixed several incorrect entries in XPtsp.ini that phasma found.
- Removed code responsible for selecting different Task Manager themes.
I've been working a lot of hours lately and haven't been able to respond in a timely manner lately....
I've replaced the System Restore code in the GUI with a system restore UDF. The UDF calls the SRCLIENT.DLL instead of making object calls, so it shouldn't crash AutoIt should it fail to create a System Restore point. As for how to detect whether System Restore is actually present, I don't really know how to do that. I've modified the GUI to check for the SRCLIENT.DLL file, and if it present, to present the option to do so. Hopefully, that'll be enough to prevent something bad from happening
I looked at the spoiler and you're quite right: The code for the CAD 2009 background replacement was wrong. I've fixed that error in the code. Also fixed the XPtsp.ini as requested, as that's not right, either. I'll fix the CAD2009 add-on shortly....
#644
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 15 December 2011 - 06:18 PM
All XPtsp themes:
- Removed the TASKMGR.EXE.*.RES files that did not exist in the original batch versions.
I did this to remove some bad resource files that get corrupted every time I delete the dialog boxes out of the them.
- Removed the TASKMGR.EXE.*.RES files that did not exist in the original batch versions.
I did this to remove some bad resource files that get corrupted every time I delete the dialog boxes out of the them.
#645
Burned
-
- Members
-
- 54 posts
Advanced Member
- Location:Vancouver
- OS:Windows 7
Posted 19 December 2011 - 12:01 AM
Download links are dead.
#646
Burned
-
- Members
-
- 54 posts
Advanced Member
- Location:Vancouver
- OS:Windows 7
Posted 19 December 2011 - 12:12 AM
When I did a "Normal Installation" on XP Pro, the wallpapers and themes were not installed.
#647
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 21 December 2011 - 10:12 AM
I have been rewriting the website and I might have been working on that section at that moment. I apologize for the inconvience, however, the site links should work. At the moment, the mirror links don't.Download links are dead.
Hmmmm...... I'll look into it.When I did a "Normal Installation" on XP Pro, the wallpapers and themes were not installed.
#648
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 21 December 2011 - 11:22 PM
What's Changed in v3.0.0.24:
- Fixed the code flagging whether or not the theme package is a Full Pack or Icon Only.
Burned:Out of curiosity, which theme package where you using? EDIT: 
<-- This is how I feel.... I'm an idiot... 
Nevermind, the problem isn't with the theme but with the GUI. I've fixed the problem and will upload the fixed version shortly.....
- Fixed the code flagging whether or not the theme package is a Full Pack or Icon Only.
Burned:
<-- This is how I feel.... I'm an idiot... Nevermind, the problem isn't with the theme but with the GUI. I've fixed the problem and will upload the fixed version shortly.....
#649
computerfan9000
-
- Members
-
- 1 posts
Lurker
- OS:Windows 7 x64
Posted 23 December 2011 - 08:51 PM
With 3.00.24 and the Neon Blue Theme Pack, this still happens with XP MCE. I think it is because the Royale theme in MEDIACTR.CAB doesn't get replaced. I uploaded my log as an attachment.When I did a "Normal Installation" on XP Pro, the wallpapers and themes were not installed.
XPtsp.txt 15.15K
3 downloads
Edited by computerfan9000, 23 December 2011 - 08:51 PM.
#650
Mr_Smartepants
-
- Members
-
- 794 posts
DriverPacks.net Administrator
- Location:Cambridgeshire
- OS:Windows 7
Posted 02 January 2012 - 08:37 PM
I've been testing/rebuilding/retesting my XP Home source and I think the theme problem isn't fixed in 3.0.0.24. On XP Home, the themes (xptsp Home or Pro) aren't being set and the default xp theme persists.
So far this only affects Home, my Pro & MCE builds are working fine. I use the green theme and original extras.
Here's the latest log file:
*Edit
I was wrong, MCE/Pro theme is broken also in my MCE build. After the desktop loads, you're still able to select any theme you like from the desktop properties ctrl-pnl but the "Windows XP" theme is still just that, the old crusty normal XP theme.
Here's the latest log file:
Spoiler
*Edit
I was wrong, MCE/Pro theme is broken also in my MCE build. After the desktop loads, you're still able to select any theme you like from the desktop properties ctrl-pnl but the "Windows XP" theme is still just that, the old crusty normal XP theme.
Edited by Mr_Smartepants, 02 January 2012 - 10:01 PM.
#651
Mr_Smartepants
-
- Members
-
- 794 posts
DriverPacks.net Administrator
- Location:Cambridgeshire
- OS:Windows 7
Posted 04 January 2012 - 07:52 PM
Oh, and CAD2009 is still refusing to install at all.
Sorry to be the bearer of bad news.
Sorry to be the bearer of bad news.
#652
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 06 January 2012 - 09:35 PM
I thought I had uploaded a new version since December 26, 2011...... Damn 
I wasn't aware that CAD2009 wasn't installing....
EDIT: Just performed a Live Install on XP Home using v3.0.0.25.... CAD 2009 was installed. Will try a Integration into a source folder next....
EDIT2: Just integrated into XP Home and installed in a VM. CAD 2009 was NOT installed. So I'm fixed the issue and am uploading a new copy of Original.extra to address this issue.
Edited by dougiefresh, 07 January 2012 - 05:39 PM.
#653
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 07 January 2012 - 05:45 PM
What's Changed in v3.0.0.25:
- Rewrote some code dealing with the visual themes and Icon Only packages.
- Rewrote some code dealing with the visual themes and Icon Only packages.
#654
Mr_Smartepants
-
- Members
-
- 794 posts
DriverPacks.net Administrator
- Location:Cambridgeshire
- OS:Windows 7
Posted 07 January 2012 - 09:06 PM
I just tested 3.0.0.25 on XP Home and everything is working fine!
Well done!
I'll be testing Pro & MCE later. I'll report back with my results then.
*Edit
Pro and MCE work fine also. So far all bugs I reported above are fixed.
Although there is one little thing that I've found. When using a MCE source, the option to use the "Pro" theme is selected by default and greyed out so that it can't be unchecked.
This isn't a problem for me since I use the "Pro" theme for all my builds anyway, but I thought I'd mention it.
Thanks for all your hard work!
Well done!
I'll be testing Pro & MCE later. I'll report back with my results then.
*Edit
Pro and MCE work fine also. So far all bugs I reported above are fixed.
Although there is one little thing that I've found. When using a MCE source, the option to use the "Pro" theme is selected by default and greyed out so that it can't be unchecked.
This isn't a problem for me since I use the "Pro" theme for all my builds anyway, but I thought I'd mention it.
Thanks for all your hard work!
Edited by Mr_Smartepants, 08 January 2012 - 10:41 AM.
#655
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 08 January 2012 - 04:19 PM
Hallelujah!!!! Thank you for the feedback!I just tested 3.0.0.25 on XP Home and everything is working fine!
Well done!
I'll be testing Pro & MCE later. I'll report back with my results then.
*Edit
Pro and MCE work fine also. So far all bugs I reported above are fixed.
Okay, this problem will be fixed in the next version. Let me know if there is need for the fix RIGHT NOW and I'll release it. Until then, it'll get released when there are more problems to fix.Although there is one little thing that I've found. When using a MCE source, the option to use the "Pro" theme is selected by default and greyed out so that it can't be unchecked.
This isn't a problem for me since I use the "Pro" theme for all my builds anyway, but I thought I'd mention it.
#656
Mr_Smartepants
-
- Members
-
- 794 posts
DriverPacks.net Administrator
- Location:Cambridgeshire
- OS:Windows 7
Posted 08 January 2012 - 09:39 PM
For me? Don't worry about it. Like I said, I use the "Pro" theme on all of my builds so I'm not stressing it.
I did find a small bug in the theme but I'm not sure if it's part of your green theme pack or with my build. The system window title-bar font is set to Arial instead of Tahoma which looks like crap. Setting it to Tahoma looks much better. Again, I'm not sure if that's set by xptsp or not.
I did find a small bug in the theme but I'm not sure if it's part of your green theme pack or with my build. The system window title-bar font is set to Arial instead of Tahoma which looks like crap. Setting it to Tahoma looks much better. Again, I'm not sure if that's set by xptsp or not.
#657
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 09 January 2012 - 01:08 AM
As far as I can tell, that is set by the operating system, not XPtsp. I think I can set it to be the default settings, though.... Lemme investigate how to do this in AutoIt....
#658
Mr_Smartepants
-
- Members
-
- 794 posts
DriverPacks.net Administrator
- Location:Cambridgeshire
- OS:Windows 7
Posted 20 February 2012 - 10:06 PM
v3.0.0.25 has been working great for me so far. 
I just have a suggestion you might want to consider.
If the user selects a source folder where XPtsp has already been previously integrated, shouldn't the GUI display a warning like "Hey! I already fixed this folder once!"
Maybe detect the presence of %source%\XPtsp.log or other key file(s).
Or can the GUI "upgrade" previously integrated sessions?
I just have a suggestion you might want to consider.
If the user selects a source folder where XPtsp has already been previously integrated, shouldn't the GUI display a warning like "Hey! I already fixed this folder once!"
Maybe detect the presence of %source%\XPtsp.log or other key file(s).
Or can the GUI "upgrade" previously integrated sessions?
#659
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 25 February 2012 - 10:26 PM
I can add functionality to inform the user if the install has already been patched. It shouldn't be hard to do.
As for whether the GUI can "upgrade" a previously integrated session, I wouldn't see why it couldn't. Even though integrating two different XPtsp themes could result in a mish-mash of appearances, there isn't anything that would prevent a second integration.
EDIT: Regarding the active title font, I can't seem to figure out where the setting is being held.....
As for whether the GUI can "upgrade" a previously integrated session, I wouldn't see why it couldn't. Even though integrating two different XPtsp themes could result in a mish-mash of appearances, there isn't anything that would prevent a second integration.
EDIT: Regarding the active title font, I can't seem to figure out where the setting is being held.....
#660
dougiefresh
-
- Moderators
-
- 775 posts
Wincert Addict
- Location:Tennessee, USA
- OS:Windows 7
Posted 28 February 2012 - 01:25 AM
What's Changed in v3.0.0.26:
- Added code to detect whether the source folder has already been integrated previously.
- "Use Pro" box enabled when integrating to Media Center Editions.
- Added code to detect whether the source folder has already been integrated previously.
- "Use Pro" box enabled when integrating to Media Center Editions.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
