Recommended Posts

URL to post, and download link :)

Alternate download link

gonedark.jpg

[PASTED FROM POST ON MY SITE]

I ported the GoneDark and GoneDark Polarized message style for Adium. It's been awhile since my last release, so here it is folks. Enjoy! Please read the readme. I'd post a longer post, but I have an exam tomorrow. Almost completed high school laughing

I will mirror this at the Miranda addons page tomorrow. I require resting for my examination tomorrow. Have fun. Should be no bugs. If there are, please comment this post. Finally, I hope you guys like it (I do appreciate comments of encouragement and compliment too of course!).

[/PASTED FROM POST ON MY SITE]

(i am tired from studying, not much effort to post a giant post. bugs, etc reply here or comment on my page. thanks! and enjoy)

EDIT: LINK BUG FIXED (fix finally uploaded, more accurately speaking :p ). Please download from alternative download link. Would also be nice if anyone has any suggestions for free RELIABLE hosting so I can simply host all my IEView templates on one central location...

- Russellc

Edited by russellc

You need to select your outgoing font here: Message Sessions > Fonts and colors > Message Input Area

Tell me if that fixed your problem :)

I'm sure it worked :p

I'm actually trying to change the font that the recipient of my messages will see. The ">> Outgoing Messages" font. I have it set to be Georgia size 8, but that is not showing up. Here's my version info if that helps any.

CPU: AMD Athlon 64 Processor 3800+ [x86 Family 15 Model 15 Stepping 0] [DEP enabled]

Operating System: Microsoft Windows XP [version: 5.1.2600 Service Pack 2]

Installed RAM: 1024 MBytes

Free disk space on Miranda partition: 54822 MBytes

Miranda path: C:\Program Files\Chat\Miranda IM

Miranda IM version: 0.4.3 alpha build #52 Unicode

Build time: 20:20:49 on 25 April 2006

Profile size: 502.60 KBytes

Profile creation date: 06 Jun 2006 at 23:26:25

Nightly: Yes

Unicode core: Yes

Active Plugins (18):

AimOSCAR.dll v.0.0.0.5 [26 Apr 2006] - AIM OSCAR Plugin - Beta 5

chat.dll v.0.3.2.1 [26 Apr 2006] - Chat (Unicode)

clist_modern.dll v.0.4.2.28 [26 Apr 2006] - Modern Contact List (UNICODE)

dbx_3x.dll v.0.5.1.0 [26 Apr 2006] - Miranda database driver

fingerprint.dll v.0.0.0.8 [20 Jan 2006] - Fingerprint (client version) icons module

help.dll v.0.1.2.2 [26 Apr 2006] - Help

IcoLib.dll v.0.0.0.2 [15 Apr 2005] - Icons library manager

ieview.dll v.1.0.9.3 [13 May 2006] - IEView

import.dll v.0.9.2.2 [26 Apr 2006] - Import contacts and messages

loadavatars.dll v.0.0.1.21 [07 Apr 2006] - Avatar service (Unicode)

msn.dll v.0.4.3.0 [26 Apr 2006] - MSN Protocol (Unicode)

png2dib.dll v.0.1.3.0 [26 Apr 2006] - PNG images processor

PopUp.dll v.2.0.3.8 [22 Sep 2004] - PopUp Interoperability

smileyaddw.dll v.0.1.12.6 [07 Jun 2006] - SmileyAdd Unicode

tabsrmm.dll v.0.9.9.200 [26 Apr 2006] - tabSRMsgW (unicode)

VersionInfo.dll v.1.2.0.3 [01 Jun 2006] - Version Information

WhoIsReadingMyStatusMsg.dll v.0.0.1.1 [13 Apr 2006] - WhoIsReadingMyStatusMsgNotify

Yahoo.dll v.0.3.0.9 [26 Apr 2006] - Yahoo Protocol Beta/Nightly

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

    • No registered users viewing this page.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!