Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


FranceBB last won the day on May 28 2019

FranceBB had the most liked content!

Community Reputation

290 Excellent


About FranceBB

  • Rank
    Broadcast Encoder
  • Birthday 07/29/1993

Contact Methods

  • MSN
  • Skype

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

3,908 profile views
  1. Ok so they dropped them both altogether. Classic... -.-
  2. In case anyone was wondering, I tried with my modified kernel and it doesn't run on my machine either. All the missing kernel calls are patched except for "CancelIoEx": https://docs.microsoft.com/en-us/windows/win32/fileio/cancelioex-func The good news though was that there's CancelIo in Windows XP, so I replaced CancelIoEx with its non-ex counterpart and I tried to make a few tests without any positive result. The reason is that the normal CancelIo (the non-ex one available in XP) can't be used to cancel io operations in other threads, so most of time it just hangs on nn_close... On top of that, the new code has several missing calls for the UI as well and I can't fix any of them in Shell32 as I'm not a UI guy... I guess I'm gonna stick with 1.8.15 'till it's gonna work, then I don't know... A few screenshot for those interested: On a normal XP SP4 Installation: On my XP running a custom kernel: Then there are missing calls in Shell32 and User32: I guess that's pretty much it for Telegram, unless someone wants to try to fork it and re-introduce XP compatibility. I'll leave a link to the source code anyway: https://github.com/telegramdesktop/tdesktop Out of curiosity, is there anyone who can try the official installer on Windows Vista?
  3. That's true, but we like your the way you are.
  4. Windows 7 has been one of the best Microsoft OS; now the support is over, but that didn't stop businesses from keep using it. As a matter of fact, Windows 7 has been the de facto replacement for many Embedded systems who were deployed across the world in a period when Windows XP Embedded was slowly starting to get to the EoS path. This topic is dedicated to the Spotters, namely people who see Windows 7 or its derivatives (Win 7 Embedded) running in the wild and take a picture. We started one for XP as well when support was over: Alright, let's crack on, shall we? The first picture is from a Win 7 system running advertising. The second picture was taken today by me in Milan, Italy and shows Windows 7 in idle on the login screen:
  5. If you are going to install all of them, please do it sequentially. Anyway, as ED_Sln said, I haven't encounter any programs running on .NET 1.1 for years now as pretty much everything targets .NET 4.0 or newer (newer version can't run on XP). I personally kept all of them on my computer just in case, anyway .NET Framework 4.0 is supposed to have superseded all the previous ones so it's probably the only one you need.
  6. Nope, the only reason why I choose "FranceBB" long time ago (in 1998) was because my first name is "Francesco" and the first letter of my surname is "B", however the website I was trying to register to (I don't even remember which one it was) already had that name, so opted for "BB". It was also fine 'cause at the time I used to go to the beach to do surf but not with a regular board and that thing was called bodyboarding, so in that case the two "B" had a sort of double meaning. Little I know that I would have left Italy within few years because of my studies and my job and that my nickname would have created a lot of confusion xD
  7. As I said in PM, please use the Russian patch. Just install it and you'll see that your boot.ini changes pointing to a custom kernel and HAL, however they're NOT called like the Windows default, they're different. It takes advantage of the fact that XP can load a different version of HAL and kernel if you specify which files it has to load. Besides, I would also append another string to boot.ini, call it "Normal kernel backup" in which you specify the Original Kernel and HAL so that you can decide whether you're gonna boot with the Russian patch (up to 64 GB of RAM supported) or with the original one. The Russian patch works like a charm and it will also install you some USB configuration files that fix the bloody problem the original Chinese patch had because of the mismatch between Windows Server 2003 and XP. I don't know why you're using this so called TU kernel, but I don't really wanna test it (nor Jaclaz I think). Anyway if it is replacing system files that shouldn't be replaced it's no wonder that SFC will bring them back and you'll see the 3GB of RAM only back. That's a very poor approach considering that instead of replacing system files you can just specify a different name to use in the boot.ini and that's exactly what the Russian patch does. I've been using it for years now and I have no problem with my 32 GB of RAM, I can send you as many screenshots as you want. I will also send you the link in PM (I can't post it here otherwise @dencorso will yell at me for very obvious reasons), but then please stop reinventing the wheel. There's already an implementation, it works, everybody use it, don't use something else.
  8. That's the saddest slope I've ever looked at... That's right. I'm one of those people faking my user agent, however I only bump the number of the version of Chrome to match the very latest release and many websites are happy with that. Most of the times there's no need to also change the OS. The last thing I want is to increase the share number of the bloody Windows 10! Besides I like the idea of people spitting out coffee when they check their website stats and they see "Windows XP x86 - Chrome 80".
  9. You know what's worse? That it was probably paid to do it as he sold the "slowdown" as an upgrade.
  10. Thank you, as always. You've become my Flash update reminder for quite some time now xD By the way, as we're in 2020 life is gonna be over soon for Flash, although there are still many websites using it and most of them are not going to be rewritten anytime soon, so I kinda fear about what will happen once the EoS is meet. Hopefully nothing, but I wouldn't be so sure for a software who has been suffering from security problems ever since its initial release through all these years... Well time will tell, I guess...
  11. Oh God... 1 GB with Win10 means no RAM whatsoever is left for the user to open up programs and so on: everything is put on the paging files and moved back and forth from the HDD to the RAM and vice versa. Not only it's gonna reduce the life of the Hard Drive, but it's also going to be extremely slow...
  12. Ok so with the new drivers it works absolutely fine! :) Just a question though: every time I get a new network adapter, I always have to memorize all my networks from scratch. Is there a way to share the memorized networks between the network adapters? You know, it's not a big deal, I've been doing this for years, but I'm getting lazier as years pass... :P
  13. Yep that's a touchscreen indeed, but believe me it's very annoying when you press the buttons 'cause it's poorly calibrated. EDIT: I did some research (I literally asked people xD) and people seem to recall those machines being installed in Northern Italy between 2009 and 2010. So... it's not as old as I thought.
  14. Dunno, really, but I think it's pretty old. I'm not from that area, so I can't tell... They "recently" (2017 I think) changed the device on the right with a modern one to support contactless cards, though.
  15. Hi there, I've recently purchased a new USB Wi-Fi adapter: Alfa AWUS1900. It's brand new and bought it specifically 'cause since it was first released to the public in 2013, it has drivers from Windows XP up to Windows 10. As a matter of fact, I quickly downloaded the drivers from here (official Alfa website): https://files.alfa.com.tw/?dir=[1] WiFi USB adapter/AWUS1900/Windows On Windows 10, when I ran the Setup Wizard, everything was fine and the USB adapter was working, but when I tried to install the drivers on Windows XP using the same Setup Wizard, it prompted me to a big fat bluescreen. I tried to reboot and do it again: bluescreen. I tried to install the driver in safe mode: bluescreen. I rebooted, I logged back in my account and I installed the driver by prompting the installer to the location of the .ini file on my desktop \windows_xp_32_64bit_1024.6\windows_xp_32_64bit_1024.6\RTWLANU_Driver\WinXP and the installation completed successfully, however the Device Manager says "This device cannot start. (Code 10)". What really p***es me off is that they even advertise "Compatible with Windows XP" on the package but it clearly doesn't work! (I can post a picture if you want). I would really like to know whether it's them not testing drivers on XP or me who has something wrong in my configuration. This is what Microsoft website says about error code 10: Useless of course, as I can't update the driver, I already have the very latest and greatest version! -.-
  • Create New...