1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Soft7 2.0b1 released

Discussion in 'Windows & Other Software' started by Se7ven, 22 Apr 2010.

  1. Se7ven

    Wise Guy

    Joined: 7 Nov 2009

    Posts: 1,475

  2. marc2003

    Capodecina

    Joined: 6 Feb 2004

    Posts: 20,237

    Location: England

    ooh i like this. a lot more effort has been put into this than your usual windows 7 themes. i see it's had many more windows controls styled rather than just the window border. :)
     
  3. chronic86

    PermaBanned

    Joined: 4 Sep 2007

    Posts: 1,169

    Location: Newcastle upon tyne

    i dont know how to install this! no info on the page either

    "No instruction given because it's a beta, use it if you know how to !
    I will not answer for installation problems !"
     
  4. asim18

    Capodecina

    Joined: 5 Dec 2006

    Posts: 15,410

  5. bledd

    Don

    Joined: 21 Oct 2002

    Posts: 46,801

    Location: Parts Unknown

    I used to play around with XPize in XP, but I wouldn't touch these with a barge pole in Vista/7, since files that Windows update replaces are archived within Windows.

    You could be opening up a plethora of problems for the future.

    Performance 'tweaks' and bitmap patches like these should not be used in Vista / 7
     
  6. Se7ven

    Wise Guy

    Joined: 7 Nov 2009

    Posts: 1,475

    I have been using custom themes since January with no problems at all.

    chronic86 check his previous versions for instructions.
     
  7. asim18

    Capodecina

    Joined: 5 Dec 2006

    Posts: 15,410

    I've been using custom themes, patches, dlls since vista. Never had a problem. Maybe you've been unlucky.
     
  8. bledd

    Don

    Joined: 21 Oct 2002

    Posts: 46,801

    Location: Parts Unknown

    I haven't used any myself, but they eventually will cause problems. XPize had problems of it's own when it came to MS updates, and that was just files referencing dll's which made the newer files run into memory problems because too much space was being taken up by the custom bitmaps in the dlls.

    Now they're stored in the winsxs folder forever, so you may be fine for ages then an old program references it and you're presented with a problem. one that MS wouldn't get or even attempt to fix

    Using custom visual styles is much safer since that is only changing the display aspect of windows and not the files it depends on the most to make the visual modifications