Recommended Posts

Originally posted by arhra

the orange is waiting until i've finalised the design. since quite a few things are still in a state of flux atm, i don't want to be reworking everything twice (once for blue, once for orange), when i change something.

Thanks for the info, I was worried you were going to keep it mixed like this. The orange is intense, can't wait for this to be done.

damnit. board ate a reply. i hate it when that happens :dead:

hankster: there's not a lot i can do about the clock, it's completely font/fontsize dependant, so other than fiddling with the font and size, it's out of my hands... i'm going to try switching it to dungeon, and fiddling with the size to see if i can get it to work ok...

has anyone dont a trillian skin yet ?

if i knew how to i would but i dont but if i could i would :)

well if anyone can do that i'm sure we would all appreciate it

not just me but everyone on here....

thanx ahead of time.. if someone does do it..

and if you need trillian sounds... just contact me.

*BUMP*

i finally finished the LS theme. download here.

I should have the blue/white msstyle finished up sometime in the next few days, although i've not ever started on the shellstyle yet, so it might take a bit longer...

the orange/black versions of both are waiting on a fsckload of photoshop work.

i'm having problems with the litestep theme.

i'm using the LS-OTS distro.

i downloaded the rhodium edge LS theme and put it in the litestepthemes folder.

i've installed everything with default settings and personalized my applications (part of the installer) and rebooted.

it started up in the simplicity theme. so i used the LSTS theme changer thing and switched to rhodium edge.

all of a sudden, about 20-30 popups would come on one after another, giving me error msgs about loading variables.

when it finally loads, it looks all screwed up.

can anyone help me?

thanks in advanced.;)

[edit]

i was looking through the step.rc file included in rhodium edge...and one line is:

include "$ConfigDir$themevars.rc"

but i checked in litestepthemesrhodiumedgeconfig and i couldn't find a themevars.rc file.

so then i check the simplicityconfig folder and saw one there.

so is this what is causing my problem, and is there something i should change?

[/edit]

*sigh*

is it too much to ask that people read the readme?

Requires an OTS-compliant directory structure, and a recent indie build (June 2002 or later) to function correctly.

now, admittledly i forgot to put the url in the readme, but it was clearly linked in the description on deskmod...

so, head over to lsdev@shellfront, download the latest build, follow the instructions found here to upgrade your build, and try it again.

Originally posted by arhra

*sigh*

is it too much to ask that people read the readme?

now, admittledly i forgot to put the url in the readme, but it was clearly linked in the description on deskmod...

so, head over to lsdev@shellfront, download the latest build, follow the instructions found here to upgrade your build, and try it again.

I've done all as you've said and the theme still wont work. Whats goin on? Can anyone help? If not I'm giving up on litestep once again.

- ZX

Originally posted by ZeroXero

I've done all as you've said and the theme still wont work. Whats goin on? Can anyone help? If not I'm giving up on litestep once again.

- ZX

did you switch themes using lsts?

if so, you might have been bitten by the typo-bug (there's a version of lsts where occasionally it sets it to include "stdtep.rc" instead of "step.rc" thanks to a typo in the code...).

open up your $litestepdir$step.rc in your text editor of choice, and it /should/ look like this:

<pre>rcStep "step.rc";

dirTheme "$LitestepDir$themesRhodiumedge";

include "$dirTheme$$rcStep$";</pre>

if not, edit it so that it does, and recycle litestep.

if you're still having problems, check to make sure you're running hte latest build available (look in the !about box, if the theme isn't working and you've got no other way to get to it, you can get to it via the recovery menu [ctrl-alt-F1]).

you should have something like this:

!about.png

the part circled in red is the important part. i'm pretty sure the theme works on any build from about the beginning of june onwards, although i'm not certain. as you can see, i'm running the 16th june build, so i'm pretty certain it works fine on that one...

if you /are/ running a recent build, and you're still having problems, then you almost certainly have a deeper problem with your installation. redownload the latest build, and copy the files back over whatever ones you've got in your litestep dir (after quitting litestep, of course, since you can't overwrite the files while they're in use). verify that the files have been overwritten (check the datestamps on them), and start litestep up again (litestep.exe -nostartup).

if you still have problems, then i haven't the foggiest what's wrong :ermm:

hey arhra,

sorry, i didn't read the part that said to use the latest build of LS.

but i did everything you said, and it works really well.

except when i startup rhodium edge, a popup says that it can't start up "gfxviewer".

what is that? the theme still works well, but i'm wondering if this "gfxviewer" makes the theme better.

thanks,

joseph

gfxviewer is one of the standard OTS evars, you should have set it up during the install... to change it, edit $litestepdir$personalevars.rc (you should just be able to get to it from the popup, litestep/edit config/evars.rc), and edit the gfxviewer line to point at your preferred program (or add it if it isn't there).

arhra, thanks for your help but it still wont work. do you have a link to the installer you got at all? I updated my litestep to the version you have and it still wont work. Even updated LSTS and it dont work. Says it cant load modules or something. Thanks again for all your help.

- ZX

Muchos good theme, even made me try LS again.

I got it all working, which is good except for two things:

1. The Systray doesnt show anywhere on the LS thingy. s it meant to? if not, methinks it would be good :)

2. When ever I click the My Computer button, or anything that runs explorer,exe, the damn start menu appears, and all my boot up proggies run again!

any way to fix?

Cheers.

ZeroXero: i frankly haven't a clue what's wrong with your setup. If you've got an up-to-date build, an OTS-compliant directory structure, and you unzipped the theme to the right place, it should literally be a drag-and-drop install. Everyone else i know who's tried the theme has only had problems if they didn't have a new enough build, and the problems went away as soon as that was rectified.... :ermm:

actually, i've just been informed of a slight ######-up in that the directory structure wasn't properly preserved when i zipped it up, so it might be that it's not in the right directory, which would explain the unable to load module errors...

the directory structure should be similar to this:

<pre>$litestepdir$themesrhodiumedge

+---config

+---images

|   ---bluewhite

+---misc

---modules

    ---docs

</pre>

if it /is/ like that, and you're still having problems, i'd be tempted to say just back up any themes you want to keep, nuke your litestep dir, and start from scratch with omar's installer, then immediately upgrade to the latest indiestep build following the instructions on omar's site.

ZeroXero: heh. glad you got it working eventually :)

condorstats: sounds like litestep isn't set as the shell properly. try running litestep.exe -install, and answering yes when it asks you if you want to set it as shell. (oh, and the systray is on the left, just below hte clock, if you meant you couldn't find it, or if you meant it wasn't working properly, that'll be due to your b0rked shell settings).

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • But the reality is it will work for people's needs, and they don't care about the technology that makes it. Clearly not everyone's needs, but that low end space where personal laptops were only used to type emails, watch content and browse websites, but they didn't want to do that on a small screen device. Heck, writing that out I can now see the connection and reason it'll do so well. Apple is about experience. If the experience is bad, they don't release it. Low end Windows laptop manufacturers up until this point have not taken that into consideration ever before, so slow laggy usage with brittle slimey plastic shells were common. I hope that the low end space at least creates better physical products that last a bit longer, and if Microsoft get their act together, they could also have a solid OS on such low end hardware that would actually make the experience work for what the hardware was intended for. The fact that the CPU is a "cellphone", sorry mobile phone processor is irrelevant. It's about the experience, and so far, that sounds quite solid.
    • Hello, Bonjour is Apple's implementation of a multicast-DNS service, which allows devices running Apple's software and/or hardware to find each other on your local network.  I believe the Windows version was last updated around 2010. If you do not need it, you can stop and disable the Bonjour service in the Services Control Manager (filename: SERVICES.MSC).  Once you have done that, the operating system will no longer attempt to load the service. Regards, Aryeh Goretsky  
    • This AMD RX 9070 16GB GPU that performs close to Nvidia 5070 is under $600 by Sayan Sen With the memory shortage that's prevalent nowadays, discounts are super-hard to get. As such we post good deals whenever they pop up. Recently, we covered a few great discounts on SSDs wherein you can get a 4TB TeamGroup NVMe PCIe Gen4 drive for just $400 thanks to a special coupon. If you want a faster product but don't need all that capacity, you can also opt for Samsung's 990 PRO 2TB that is on sale for its lowest price in over three months. Let's say though that you are on the hunt for a 1440p gaming card. In that case AMD's RX 9070 non-XT can help, and with its 16GB VRAM, you can also run AI models locally without worrying about bottlenecking (check out our recent 9070 GRE reviews for gaming and productivity to get an idea). The PowerColor Reaper variant of the RX 9070 is currently on sale for just $580 which is a very good price in the current state of affairs (purchase link under the specs table down below). The Reaper cooler on this 9070 uses a triple‑fan design with ring‑blade fans, paired with premium dual ball bearings to extend lifespan and reduce friction. "Intelligent" fan control allows the fans to remain idle at lower temperatures, only spinning up when the GPU is under load. A nickel‑plated copper base makes direct contact with both the GPU and memory modules, helping to spread heat evenly. PowerColor also applies Honeywell PTM7950 phase‑change thermal interface material (TIM), which fills microscopic gaps between the die and heatsink for more efficient thermal transfer. The fan shroud is shorter in height as the firm has made it such that it can be used in certain SFF (small form factor) cases. The technical specifications of the Reaper RX 9070 are given in the table below: Specification Value Stream Processors 3584 Units Video Memory 16GB GDDR6 Memory Speed 20.0 Gbps Memory Interface 256-bit Engine Clock Game Clock: up to 2070 MHz Boost Clock: up to 2520 MHz Bus Standard PCI Express 5.0 x16 Display Connectors 1 x HDMI 2.1b, 3 x DisplayPort 2.1a Maximum Resolution DisplayPort: 7680 × 4320 HDMI: 7680 × 4320 Board Dimensions 289mm × 111mm × 41mm 304mm × 127mm × 42mm (with bracket) Slot 2 Minimum System Power Requirement 600W Power Connectors Two 8-pin PCI Express Get the PowerColor Reaper RX 9070 at the links below (you get only a 90-day warranty on Woot): PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $579.99 (Sold and Shipped by Amazon US) (Was: $700) PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $559.99 (Sold and Shipped by Woot US) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • Are they marketed as an entry into astronomy or astrophotography? I do astrophotography. With big rigs, lots of computers, cables and headaches. I love it. And by learning this ridiculously complex hobby, I’ve learned about the objects I’m shooting. Astronomy followed from photography.
    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      578
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      72
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!