FlyaKite 3 it's comming! =D =D =D


Recommended Posts

Awesome, looking forward to shots of it. I take it it will install like any other VS? (As in it can be removed/changed via the Display dialogs)

586862688[/snapback]

Ehh... not so much. What you have to realize is, FlyakiteOSX at it's basics is an installer. It is not a program in the typical sense. What it will do is moddify your system files, install software, install skins, cursors, sounds, etc. without the user having to mess with that stuff.

Display Properties only shows a few things. Mainly wallpaper in the Desktop tab and visual styles in the Appearance tab. So the wallpaper and visual style skins that FlyakiteOSX installs will appear in the tab, but everything else will not. Cursors will apear in the Cursors tab of Mouse Properties. Sound schemes in the Sounds tab of Sounds and Audio Devices, etc.

But yes, sure you can change the visual style still through Display Properties and all that, but it's not just a whole set you can turn off with a switch. Especially the icons. Since the icons stored within an actual system file is modded, the system is now using that icon. To use different icons you need to use Icon Packager (or IconPhile does it as well I believe?), or you need to uninstall the "System Files" portion of the package.

Ok then...Thank you for that. Will there be an uninstaller? So that if i want to change, i can uninstall the style and any files it placed with the files that were there previous to installation (reverting back to the state of the VS before hand).

Ok then...Thank you for that. Will there be an uninstaller? So that if i want to change, i can uninstall the style and any files it placed with the files that were there previous to installation (reverting back to the state of the VS before hand).

586862948[/snapback]

Yes, yes.

I saw this v3 preview about a week ago. I wanted to download v2 and got that image. Can't wait either.

Holy **** man it's COMING and NOT COMMING!

I went to the official site of Fly a Kite and I found with the announce of the third version!!!

The second version is greate, but How would it be the third???

Well, for anyone who likes this shellpack I think this gonna be interesting ^^...

http://osx.portraitofakite.com/

586853213[/snapback]

  • 3 weeks later...

:alien: Question,wish somebody can help me:

I'm using FlyakiteOSX 2.0, Who can tell me, how dose it change the bootscreen as so? Can I do it without FlyakiteOSX?

If so, which steps should i follow?

which files dose it changed or added?

I have checked the Ntoskrnl.exe file, it isn't changed, so how can it be like that?

Plz answer me.... I really want to do it myself. Coz I when i reinstall my system, i can keep the things (Or who can tell me which files should i keep after installing FlyakiteOSX?).

Thnx...... :D

:alien: Question,wish somebody can help me:

I'm using FlyakiteOSX 2.0, Who can tell me, how dose it change the bootscreen as so? Can I do it without FlyakiteOSX?

If so, which steps should i follow?

which files dose it changed or added?

I have checked the Ntoskrnl.exe file, it isn't changed, so how can it be like that?

Plz answer me.... I really want to do it myself. Coz I when i reinstall my system, i can keep the things (Or who can tell me which files should i keep after installing FlyakiteOSX?).

Thnx...... :D

There are a number of programs that allows you to change your bootscreen including StyleXP, LogonUI Boot Randmoizer.

I havn't tried Flyakite 2 but am waiting to try the version 3 so i can't tell whether it hacks the ntoskrnl.exe file aur creates its copy. However you can try other programs which can change your bootscreen.

:alien: Question,wish somebody can help me:

I'm using FlyakiteOSX 2.0, Who can tell me, how dose it change the bootscreen as so? Can I do it without FlyakiteOSX?

If so, which steps should i follow?

which files dose it changed or added?

I have checked the Ntoskrnl.exe file, it isn't changed, so how can it be like that?

Plz answer me.... I really want to do it myself. Coz I when i reinstall my system, i can keep the things (Or who can tell me which files should i keep after installing FlyakiteOSX?).

Thnx...... :D

v2.0 uses a special method to edit the boot screen. It edits the boot.ini file and appends the switches /bootlogo and /noguiboot to the end of the first boot entry. What this does is tells the system to not use the normal GUI bootup with the XP boot screen and progress bar. It also tells it to use a static bmp as the boot logo. If you look in your WINDOWS directory you will find Boot.bmp, that is the image it is using.

As for v3.0, this has entirely changed. The installer creates a copy of ntoskrnl.exe. Then what it does is dynamically patch the color palette that is hardcoded into the file, as well as replaces the standard image resources in the file. What this does is allows the system to use a normal bootup screen that allows a progress bar and does not interfere with startup procedures like ChkDsk or Partition Magic. It also removes the switches set by v2.0 and sets a new switch /kernel=osxboot.exe, which tells the system to use the copy of the ntoskrnl.exe file it made. This way your original ntoskrnl.exe file is NEVER messed with.

As for a time frame, it was originally supposed to be released before Christmas, but has been pushed back a couple of weeks or so. Since releases are so rare now, I think we can all agree its best to do it right than release it early and regret it later. Don't worry though, it will be worth the wait as soooo much is being changed/added/fixed.

Thanks everyone!

v2.0 uses a special method to edit the boot screen. It edits the boot.ini file and appends the switches /bootlogo and /noguiboot to the end of the first boot entry. What this does is tells the system to not use the normal GUI bootup with the XP boot screen and progress bar. It also tells it to use a static bmp as the boot logo. If you look in your WINDOWS directory you will find Boot.bmp, that is the image it is using.

As for v3.0, this has entirely changed. The installer creates a copy of ntoskrnl.exe. Then what it does is dynamically patch the color palette that is hardcoded into the file, as well as replaces the standard image resources in the file. What this does is allows the system to use a normal bootup screen that allows a progress bar and does not interfere with startup procedures like ChkDsk or Partition Magic. It also removes the switches set by v2.0 and sets a new switch /kernel=osxboot.exe, which tells the system to use the copy of the ntoskrnl.exe file it made. This way your original ntoskrnl.exe file is NEVER messed with.

As for a time frame, it was originally supposed to be released before Christmas, but has been pushed back a couple of weeks or so. Since releases are so rare now, I think we can all agree its best to do it right than release it early and regret it later. Don't worry though, it will be worth the wait as soooo much is being changed/added/fixed.

Thanks everyone!

Thanks Flyakite! :blush: But, could u tell me which files should I keep for Bootscreen, Plz? Cheers! :D

Strongly support you, your team and FlyakiteOSX !!! Merry X'mas! :laugh:

Thanks Flyakite! :blush: But, could u tell me which files should I keep for Bootscreen, Plz? Cheers! :D

Strongly support you, your team and FlyakiteOSX !!! Merry X'mas! :laugh:

Go to the WINDOWS directory and find the file Boot.bmp, and keep that.

Then after you reformat, edit your boot.ini (in the root of your WINDOWS drive, generally C:\boot.ini. Its hidden, but trust me it is there). Or, System Properties -> Advanced tab -> Startup and Recovery settings -> "Edit" button under System Startup.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

That is the default boot.ini normally. On the first line after [operating systems] add the switches /noguiboot and /bootlogo, so you end up with something like this:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /noguiboot /bootlogo

After you have edited boot.ini and saved it, copy Boot.bmp into your WINDOWS folder and you're all set.

Go to the WINDOWS directory and find the file Boot.bmp, and keep that.

Then after you reformat, edit your boot.ini (in the root of your WINDOWS drive, generally C:\boot.ini. Its hidden, but trust me it is there). Or, System Properties -> Advanced tab -> Startup and Recovery settings -> "Edit" button under System Startup.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

That is the default boot.ini normally. On the first line after [operating systems] add the switches /noguiboot and /bootlogo, so you end up with something like this:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /noguiboot /bootlogo

After you have edited boot.ini and saved it, copy Boot.bmp into your WINDOWS folder and you're all set.

Brilliant, Thank you very much Flyakite. You're so kind. Looking forward to the V.30... Supporting you forever... :cry:

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

    • No registered users viewing this page.
  • Posts

    • Louis Rossmann suing Samsung over "990 Pro SSD warranty scam" by Sayan Sen Back in 2023, if you recall, Neowin reviewer Robbie Khan had a dispute with Samsung over his 990 Pro SSD, which was rapidly losing its health. After significant back and forth, the tech giant had finally released firmware to "stop" the issue. Interestingly, its previous flagship at the time, the 980 Pro was also facing problems leading to two consecutive sets of firmware fixes. Three years later, it looks like a similar conflict has now broken out between tech repair entrepreneur YouTuber Louis Rossmann and Samsung, as it has escalated into a threatened lawsuit after the company allegedly refused to appropriately replace a failing 990 Pro SSD that remained under warranty. According to Rossmann, a 4TB Samsung 990 Pro NVMe SSD purchased for approximately $330 less than two years ago, began experiencing major hiccups and issues, even though he claims it had been operated under ideal cooling conditions. It was installed in a RAID 1 array and cooled by a heatsink and dual high-speed fans. However the drive reportedly started dropping out of the array, exhibiting controller-level failures that eventually became not useable in any meaningful way. Rossmann said Samsung’s support process was marked by delays and confusion from the very start. After initially contacting the wrong regional support channel, he was redirected to Samsung’s memory support division where he submitted detailed diagnostics, logs, and proof of purchase. Rossmann runs a repair company and owns an ACE Lab PC-3000 machine, which is a professional-grade data recovery equipment. As such, he had been confident in his diagnostics. Samsung even seemingly acknowledged that later. Regardless, Rossmann claims that his initial support ticket was automatically closed before a full 24-hour response window had elapsed, forcing him to reopen the case and resubmit documentation. The controversy however intensified further from here after Samsung accepted the drive for warranty evaluation but later returned it with a repair report stating that the drive had passed its testing and that the SSD had been verified as functional. Rossmann strongly disputed those claims citing that his own independent testing on PC-3000 showed write speeds reducing to as low as 40–60 MB/s before the drive failed entirely. Samsung subsequently informed him that the SSD had been reset and reflashed, passing internal stress tests. However, the company also stated that replacement units were unavailable due to an industry-wide memory shortage and suggested that a refund process could be initiated if further testing confirmed the fault. Thus, to settle, the company offered a refund of $330, the amount that was initially paid by him to make the purchase. Here, Rossmann pointed out the seeming hypocrisy of the tech giant as in how no Samsung drive was apparently allocated for warranty replacements, but they were abundantly available for retail sales especially when using business accounts. As you can see, Rossmann is indeed right, there are Samsung 990 Pro 4TB SSDs on Amazon currently for $950 (shipped and sold by first-party Amazon US itself), and they are also available on Samsung's own store too, albeit for an even higher price of $1100. Thus Rossmann argues that Samsung’s inability or unwillingness to provide a replacement while the same model remains available for purchase at significantly higher market prices reflects a failure to honor its warranty obligations. He has issued a formal 60-day notice and says he intends to file suit in Texas small claims court, asserting that companies should face greater costs for denying legitimate warranty claims than for fulfilling them. You can check out the full video titled "Samsung's 990 Pro SSD warranty policy is a scam; I'm taking them to court," at the link below. Source and image: Louis Rossmann (YouTube) As an Amazon Associate we earn from qualifying purchases
    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
  • 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
      509
    2. 2
      PsYcHoKiLLa
      185
    3. 3
      +Edouard
      158
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!