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

    • He has planned to file a lawsuit in small claims court so it'll only be a $1000 lesson assuming he wins. That's likely a fraction of what Samsung spends on toilet paper on a daily basis.
    • Windows Server gets DNS over HTTPS (DoH) support by Usama Jawad For the past few months, Microsoft has been previewing DNS over HTTPS (DoH) for Windows DNS Server, touting it as a foundational upgrade for zero-trust enterprise networks. It essentially introduces encrypted, authenticated DNS for the networks rather than transmitting DNS traffic in clear. Now, the company has introduced the general availability (GA) of this feature. The GA of DoH encourages organizations to deploy the solution in production environments without implementing a new client-to-resolver architecture. DoH helps improve the overall security of the network and reduces the risk of spoofing due to its zero-trust design. This is a significant change because pretty much every interaction with the network requires interfacing with DNS. DoH offers several advantages over standard DNS traffic, such as encryption using HTTPS, preventing unauthorized inspection, man-in-the-middle attacks, and traffic analysis. Since it leverages TLS certificates so that clients can verify the identity of the DNS server, it prevents spoofing through this authentication mechanism. Additionally, it's built on the DoH standard defined by the Internet Engineering Task Force (IETF), which means that it should work with modern RFC 8484-compliant clients. Finally, it integrates into the existing network architecture seamlessly and can even run in parallel with standard DNS, so that customers can migrate to the new technology at their own pace. Microsoft says that in the past few months of preview, DoH has become more stable, and customers can confidently deploy it in production environments with proper guidance. Microsoft has emphasized that migrating to DoH is necessary for organizations that are moving toward zero-trust DNS solutions. Windows clients already support DoH, but the latest availability on Windows Server provides encrypted DNS to all endpoints. The company has also mentioned that "while this release focuses on encrypting client-to-resolver communication, support for encrypted communication between Windows DNS Server and upstream DNS resolvers is planned for a future update." You can follow Microsoft's guidance to deploy DoH here, but keep in mind that you need a Windows Server 2025 installation with the latest Patch Tuesday updates installed.
    • Lol I had one of these turn faulty in Jan, guess it wasn't just bad luck lol
    • I'm team Rossmann all the way. I have the exact same NVME, altough not in an array like him.
    • It had gone weeks ago. Although thinking about it I'm on the beta.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      184
    3. 3
      +Edouard
      159
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!