Downtime Notice: Thursday, July 17th 9:00 AM - 2:00 PM Eastern (-4 GMT)

Eoin-1

Eoin-1

But now I'm supposed to baby sit this stupid heart
Kessaran said:
I would assume not, since there had to be changes done to the code to address the tr cache transfer removal. Unless that was done internally only and doesn't affect client data. I'm still confused why the game's texture files updated on Tuesday though.
Click to expand...
Lots of Lamordia stuff hitting the client. So new weapon and armor textures, plus quest maps, mobs, stuff like that. Also why the audio file was updated. And the huge localization file update.
 
Warcandy

Warcandy

Active member
don't know why Cordovan didn't edit his post or reply to his post on page 1 where the original announcement was posted.
 
T

Tiff

Well-known member
I hope we dont get another issue where the will have to wait another day or two.

For example, because of load we have found that everyone will need to empty all their shared storage?!?
 
C

Clumsyoof

Well-known member
In all fairness, these guys have been up all night studying the user manual for the new servers.
Looking up terms, references pages.... it's not easy getting the hang of new toys.

User Manual: Transferring Your Gloriously Retro 32-Bit Game to a Fancy 64-Bit ServerBecause Your Pixelated Dreams Deserve a Modern Home
IntroductionWelcome, brave digital archaeologist, to the noble quest of dragging your beloved 32-bit game—forged in the ancient fires of dial-up modems and CRT monitors—into the gleaming, overpowered realm of a 64-bit server. Fear not the perils of bit incompatibility, for this manual shall guide you with wisdom, wit, and a touch of absurdity. By the end, your game will either run triumphantly or crash spectacularly. Either way, it’ll be a wild ride.Disclaimer: This manual assumes you have a 32-bit game (think pixelated heroes and MIDI soundtracks), a 64-bit server (shiny, soulless, and probably overpriced), and a sense of humor. If you lack any of these, please consult your local wizard or abandon hope.
Step 1: Confirm Your Game’s Nostalgic CredentialsBefore we begin, ensure your game is truly 32-bit. Signs include:
  • It runs on Windows XP like a dream but crashes on anything newer.
  • The installer features a wizard with a pointy hat.
  • The soundtrack sounds like it was composed on a Casio keyboard.
If your game meets these criteria, congratulations! You’re dealing with a certified retro relic. If not, you might have a 16-bit game, in which case, please consult a time machine.
Step 2: Inspect Your 64-Bit ServerYour server is likely a hulking beast of modern computing, with more RAM than your childhood PC had hard drive space. To confirm it’s 64-bit:
  1. Check the specs. If it mentions “x64” or “64-bit,” you’re golden.
  2. If it’s running Windows Server 2022 or Linux with a kernel newer than 3.10, it’s probably 64-bit.
  3. If it hums ominously and demands a blood sacrifice, you may have purchased a quantum server by mistake. Return it immediately.
Pro Tip: Name your server something epic, like “ThunderHub” or “ByteSmasher.” It won’t help the transfer, but it’ll make you feel like a cyber-lord.
Step 3: Prepare for the Great Bit MigrationTransferring a 32-bit game to a 64-bit server is like teaching a dinosaur to use TikTok. It’s not impossible, but it requires finesse and possibly some dark magic. Follow these steps:3.1: Gather Your Tools
  • A 32-bit emulator or compatibility layer: Think DOSBox, Wine, or a virtual machine running Windows XP (because nostalgia is your co-pilot).
  • File transfer method: FTP, SCP, or a USB drive you found in a drawer labeled “2003.”
  • Patience: Approximately 12 gallons.
  • Coffee or energy drinks: For when the server laughs at your puny 32-bit executable.
  • A rubber duck: For debugging. Trust us, it works.
3.2: Check CompatibilityMost 64-bit servers don’t natively run 32-bit applications because, frankly, they’re snobs. To bridge this gap:
  • Windows Servers: Enable the 32-bit Application Support feature in IIS or use a virtual machine with a 32-bit OS.
  • Linux Servers: Install ia32-libs or equivalent (e.g., lib32z1 on Ubuntu) to trick your server into tolerating 32-bit binaries.
  • Cloud Servers: Pray to the cloud gods (AWS, Azure, etc.) and spin up a 32-bit VM instance if your provider still supports them.
Warning: If your game requires DirectX 5 or a Voodoo graphics card, you may need to sacrifice a floppy disk to the Retro Gaming Gods.
Step 4: Transfer the Game Files
  1. Locate the Game Files: Dig through your ancient hard drive or that dusty CD-ROM with a cracked jewel case. Copy the game folder (e.g., C:\Program Files\EpicQuest2000) to a safe location.
  2. Compress the Files: Zip them up to avoid corruption during transfer. Name the zip file something cool, like PixelPaladin.zip.
  3. Upload to the Server:
    • Use FTP (FileZilla, because it’s free and you’re cheap).
    • Or SCP if you’re a Linux nerd who whispers “chmod 777” in their sleep.
    • If all else fails, sneakernet it with a USB drive and some ninja moves.
  4. Unzip on the Server: Extract the files to a directory like /home/server/games/EpicQuest2000. If the server complains about permissions, apologize profusely and run chmod -R 755 or equivalent.
Fun Fact: If your game folder contains a file named README.TXT in all caps, it’s legally required to be ignored.
Step 5: Make It Run (or Beg It to Run)Now comes the fun part: convincing a 64-bit server to run your 32-bit masterpiece. Option 1: Virtual Machine
  1. Install a 32-bit OS (e.g., Windows XP or Ubuntu 12.04) in a VM using VirtualBox or VMware.
  2. Copy the game files into the VM.
  3. Install any ancient dependencies (e.g., QuickTime 4, DirectX 7).
  4. Launch the game and pray it doesn’t summon a blue screen of death.
Option 2: Compatibility Layer (Linux)
  1. Install Wine (sudo apt install wine32 on Debian-based systems).
  2. Run wine EpicQuest2000.exe.
  3. If it crashes, mutter “I knew it,” and try winetricks to install missing DLLs.
  4. If it still crashes, consult your rubber duck.
Option 3: Rewrite the Game in 64-BitJust kidding! Unless you have 12 years and a PhD in masochism, skip this option.Pro Tip: If the game launches but looks like a Picasso painting, tweak the resolution settings or sacrifice another floppy disk.
Step 6: Test and Celebrate (or Cry)
  1. Test the Game: Connect to the server via Remote Desktop, SSH, or carrier pigeon and launch the game.
  2. Check Performance: If it runs slower than a dial-up modem, optimize the VM or compatibility layer. If it runs too fast (looking at you, old FPS games), cap the frame rate.
  3. Celebrate: If it works, crack open a soda and bask in your victory. If it doesn’t, blame sunspots and try again tomorrow.
Troubleshooting
  • “It won’t run!”: Did you install the 32-bit libraries? Did you bribe the server with cookies?
  • “The graphics are glitchy!”: Update your compatibility layer or lower the resolution to 640x480 for that authentic retro vibe.
  • “The server caught fire!”: Unplug it, run, and deny everything.
Epilogue: The Legacy of Your 32-Bit TriumphCongratulations! You’ve either successfully transferred your 32-bit game to a 64-bit server or learned a valuable lesson about the futility of fighting technological progress. Either way, you’re now a certified Bit Wrangler. Go forth and conquer other obsolete formats, like 8-bit NES ROMs or Betamax tapes.Final Note: If all else fails, frame your game CD as a relic of a bygone era and tell everyone you “meant to do that.” This manual was brought to you by xAI, because even AI appreciates a good pixelated adventure.
 
E

Eelpout

Well-known member
Tiff said:
I hope we dont get another issue where the will have to wait another day or two.

For example, because of load we have found that everyone will need to empty all their shared storage?!?
Click to expand...
Only be an issue for us mentally ill horders...Ask around...
 
Dandonk

Dandonk

Beater of Dead Horses
Mornyngstar said:
"The demolition permit was clearly posted in the basement janitors closet in city hall for a full month. It is the publics responsibility to read and respond before the date of action."
Click to expand...
“It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard'. "
 
Warcandy

Warcandy

Active member
why should i track the staff when its their job to inform us of changes they should do so in the SAME PLACE of the thread. in other words they should reply to their own posts or EDIT them. rather than expecting us to jump through hoops for them. it's called customer service not follow the leader
 
Kessaran

Kessaran

Well-known member
Eoin said:
Lots of Lamordia stuff hitting the client. So new weapon and armor textures, plus quest maps, mobs, stuff like that. Also why the audio file was updated. And the huge localization file update.
Click to expand...
Ah, I didn't notice those being updated too. That explains it. I only saw it updating client.mesh data and was confused before I walked away to let it update :ROFLMAO:
 
Strahd

Strahd

Well-known member
Tharminator said:
Those of us in the it world ensure that database moves go smoothly...if you are losing data in the process that's a huge red flag you are not ready for live...
Click to expand...
Agreed and of course they were not ready for the transfer to go live. Comments made insinuated that they were still testing things moments before it was to go live. I was not in the least bit surprised and several of us comment that things were likely to go close to what actually occurred.
 
You must log in or register to reply here.
Top