- 0
restoring database, and I get this error...
-
Recently Browsing 0 members
- No registered users viewing this page.
-
Posts
-
By Usama Jawad96 · Posted
Debian switches to 64-bit time completely to avoid Y2K38 disaster by Usama Jawad Some of you may remember the Y2K problem, where the world expected airplanes to fall from the sky as soon as we reached the year 2000, primarily because many software applications at that time typically just used the final two digits of each year to store calendar year data, which meant that the year 2000 was indistinguishable from the year 1900. Fortunately, we were able to avoid the 2K problem, thanks to the tireless efforts of many software vendors and engineers. Now, we are a few years away from a similar issue, and it looks like the Linux distro Debian wants to solve that problem right now in its own operating system. Basically, older 32-bit architectures will face the Y2K38 problem in the year 2038. This is because the signed representation of Unix datetime values will overflow the 32-bit space, which would cause bugs in associated software. Debian is a pretty old distro with its first release dating back to 1993, so the maintainers say that a lot of sensitive computing is still happening on 32-bit architecture. Although there are still roughly 13 years to go before we reach 2038, developers want to proactively tackle the problem rather than having to scramble at the last minute like with Y2K, according to The Register. Another name for Y2K38 is the Unix Epochalypse, since it impacts systems that store datetime values in the Unix format within a signed 32-bit space. On January 19, 2038, 03:14:07 UTC, this space will overflow. As such, Debian maintainers will use 64-bit time_t formats even on 32-bit architectures starting with the release of Debian 13 "Trixie". This is not a small change, as maintainers found the use of the time_t variable in random places across 6,429 packages. The maintainers went on to say that: This may be a breaking change for some applications, so it is important to test your program's response to the time_t variable switch by leveraging the Debian wiki. Interestingly, Y2K38 may also impact certain older Windows programs and out-of-support Windows operating systems. -
By +sphbecker · Posted
I hope they programed its eyes to turn red when it becomes evil, that is an important feature for any AI representation. -
By TarasBuria · Posted
Microsoft gives Copilot visual appearance with real-time expressions and emotions by Taras Buria Several months ago, during its 50th anniversary event, Microsoft teased a visual upgrade for Copilot (then called "Copilot Avatar") that would give the chatbot a visual character with expressions, reactions, and emotions. Now, users in the US, UK, and Canada can try Copilot Appearance, "a new, visual way to chat." Conversational mode has been available in Copilot for a while, but it lacked any visual cues or non-verbal communications. All users see on their screens is some abstract animation. With Copilot Appearance, Microsoft is improving voice conversations with real-time visual expressions. Sadly, Copilot Appearance is not a Clippy 2.0. In its current form, it is an abstract blob with a face that can morph into different shapes, express emotions, nod in agreement, etc. The concept is similar to what xAI offers with Grok AI companions that cost $300 per month, but Microsoft's approach is much more toned down (and you cannot undress it). On the official Copilot Labs website, Microsoft describes Copilot Appearance as "an experiment to incorporate a more visual, engaging experience into Copilot." Copilot Appearance is rolling out to a limited set of users in just three countries as Microsoft takes a cautious approach to a more personified AI. If you have a lucky ticket, you can try Copilot Appearance by launching Voice Mode (click the microphone button in the composer) and toggling the feature in Voice Mode settings. Microsoft says that the initial release is experimental, and it is working on refining the experience. -
By TRS-80 · Posted
A number of years ago I purchased a "Renewed" HP laptop. It worked great until it didn't work at all. Both of my W11 devices are HP AIO desktops. Have had them since before W11. They upgraded fine and have worked great ever since. My printer is also an HP inkjet. I have had it several years and have never paid for ink. -
By TRS-80 · Posted
If you use AdGuard on your PC, you can find the new "Disable Windows Recall" feature in Settings > Tracking Protection. The "Disable Windows Recall" feature in Adguard 7.21 in turned on by default. No need to do anything if you want to use the feature.
-
-
Recent Achievements
-
CyberCeps666 earned a badge
Week One Done
-
d4l3d earned a badge
Very Popular
-
Stephen Leibowitz earned a badge
Dedicated
-
Snake Doc earned a badge
Dedicated
-
Philsl earned a badge
One Month Later
-
-
Popular Contributors
-
Tell a friend
Question
thollian
Help Please....
Error importing backup file
DEBUG MODE
SQL Error : 1064 You have an error in your SQL syntax near '71', '', '', 'reserved'); INSERT INTO phpbb_posts_text (post_id, bbcode_uid, pos' at line 1
INSERT INTO phpbb_posts_text (post_id, bbcode_uid, post_subject, post_text) VALUES('70', '62c510fdf9', 'Molten Core Strats', '<center> <font color=\"red\" size=\"18\">-=MOLTEN CORE STRATS=-</font> </center> **THIS IS A DRAFT - IT WILL BE EDITED FOR APPEARENCE, CONTENT, PICTURES** <font size=\"16\">-- Table of Contents --</font> <font size=\"14\"><a href=\"#section1\">Introduction</a><br> <a href=\"#section2\">Interface Addons</a><br> <a href=\"#section3\">Raid Makeup</a><br> <a href=\"#section4\">Mob Encounters</a><br> <ul> <li><a href=\"#section4.1\">Molten Giants</a></li><br> <li><a href=\"#section4.2\">Firelords</a></li><br> <li><a href=\"#section4.3\">3 Pull - Giants + Firelord</a></li><br> <li><a href=\"#section4.4\">Lava Surger</a></li><br> <li><a href=\"#section4.5\">Lava Annihilator</a></li><br> <li><a href=\"#section4.6\">Ancient Core Hound</a></li><br> <li><a href=\"#section4.7\">Imps</a></li><br> <li><a href=\"#section4.8\">Core Hound Packs</a></li><br> <li><a href=\"#section4.9\">Lava Packs</a></li><br> </ui> <a href=\"#section5\">Molten Core Bosses</a></li><br> <ui> <li><a href=\"#section5.1\">Lucifron</a></li><br> <li><a href=\"#section5.2\">Magmadar</a></li><br> <li><a href=\"#section5.3\">Gehennas</a></li><br> <li><a href=\"#section5.4\">Baron Geddon</a></li><br> <li><a href=\"#section5.5\">Garr</a></li><br> <li><a href=\"#section5.6\">Shazzrah</a></li><br> <li><a href=\"#section5.7\">Golemagg</a></li><br> <li><a href=\"#section5.8\">Sulfuron</a></li><br> <li><a href=\"#section5.9\">Majordomo</a></li><br> <li><a href=\"#section5.10\">Ragnaros</a></li><br> </ui> <a name=\"#section1\">Introduction</a> This will be a running sticky discussing how each pull in molten core should be handled by our guild. It is required you know these and are prepared to execute them each time. I will be adding simple drawings to help me get my points across and will be added when i have the time. If you have any questions or suggestions please feel free to send me a tell in game, as i would love to discuss it with you. The purpose of this is so that we all feel confident with the strategy we\'re using. Required addons (see figs (osamu) sticky on this) -RaidBar *looking into cqraidbar might be better* (EVERYONE) -CQMC (Healers) -CQCure (Dispelers) Ideal Raid Group Make Up --Group 1-- warrior (Main Tank group - Most always nerion) mage shaman druid (druids to spread out the priests for dispel - we dont get paladins) priest --Group 2-- warrior (Main Off tank group- Osh? Bone?) mage shaman druid priest --Group 3-- warrior mage shaman rogue priest --Group 4-- warrior mage shaman warlock priest --Group 5-- warrior mage shaman rogue priest --Group 6-- warrior mage shaman hunter priest --Group 7-- rogue mage shaman warlock priest --Group 8-- hunter mage shaman rogue priest This is the ideal raid makeup, each has at least 2 healers (priests for dispel and shamans for fire resistance) and a mage to dispel curses -= THE PULLS =- Every pull that we make should be taken seriously, even if it may seem easy. This is the very first pull that we make, yes we have always been succesful with this pull; however we are still doing the most basic things wrong. It might not hurt us in this pull, but we need to get in the habit for future pulls when it becomese 2 destroyers instead of giants. How i explain this will be confusing without visuals and will most likely be edited or a lot deleted once a picture/flash file is made Our number 1 problem with this pull that we are still making is keeping the mobs together. The giants use an AOE attack that hits close ranged melee attackers. By seperating the mobs, this will solve our problem. How do we do this effectively? Proper positioning and use of the skills available in our raid. The offtank (not nerion) will be along the right hand side of the wall pushed up ready to pull with his group close behind him. Everyone else will be along the far back wall with Nerion out front a bit more. Beside him will be a hunter. Osh will pull the right giant, as soon as this is done the hunter beside nerion will use distracting shot pulling him down towards the raid. **Now what if the distracting shot doesnt work? This may seem paranoid, but as we\'ve seen before...if the pull is mishandled we will wipe. I have thought of assigning a warrior and his group as the designated \"emergency\" group. Let me explain how it would work in this scenario - and im sure you will understand how it is meant to work if i reference it later on. The emergency group in this situation would be on the left hand side of the wall - halfway between osh and nerion - if the distracting shot failed the \'emergency\' group could take over...the warrior could charge it and pull back to where nerion is. We have to let him pull it back, our typical reaction is OH NOES IT DIDNT WORK RUSH IT! and we\'re back to square 1. You might say that this is overdoing it for such an easy pull, but again i stress we will need to be using thought out strategies like this later in the instance and its better to work on them here then there.** Osh will get on the right giant and keep him up high on top of the hill...with the healers healing him (3) The distracting shot is successful and the left giant will come down right to nerion...let him get agro!!!! wait about 5seconds after the giant is on him and NUKE AWAY! Kill then simply move on to the next one. If not handled properly this potentially is the most deadly mob in the instance. It respawns in 2.5hours and does not patrol. Hits tank for around 500 fire dmg and can be moved around by the main tank. It casts a debuff on people increasing fire dmg by XXX amount (it hurts!!) this is why we need priests in each group. It also casts a debuff that does 250dmg every 2seconds and silences the person. This is a prime reason we need raid bar..if a group is all effected by this it can be devastating since no one can heal while silenced. With priests dispeling each other...it will allow those priests to dispel their own groups and continue healing. It will also summon a lava spawn which if not killed in time will split into 2 and those 2 will split into 4 and so on. The key for this pull is to keep the firelord close to the lava spawns and all the mages use blizzard. Blizzard does double dmg to these and also will hit both targets. All other DPS will target the lava spawns as they come out...USE YOUR MAIN ASSIST PLEASE! We know that not everyone does, so start doing it....if you don\'t know how to set up an assist macro PLEASE do not be embarrassed and /whisper an officer about it. I dont believe that the spawns can the shocked or silenced to make sure they\'re in close with the firelord so it is critical that the main tank moves the firelord in close to where the lava spawns spawn. Here\'s the kicker...its doable, we just need to merge our giant and firelord strategies to beat this tough pull. The first that must be dropped is obviously the firelord...this has always been our strategy we\'re just not handling the giants properly, this is mainly a \"pull\" problem that hopefuly this will resolve. The ultimate goal is to get the firelord all the way down to the backwall where we enter the instance, and to keep both of the giants up the hill near the bridge. We need to make sure that the distance apart is great enough that the AOE spells cast by the firelord do not effect anyone involved with the 2 giants We will setup group1 and group2 where we want both the giants to end up, just before the bridge one on the left one on the right. There will be a hunter inbetween the two groups to pull the firelord (giants will come too) and the rest of the raid will be all at the backwall. The second hunter will then be out front of the raid a bit with the tank going on the firelord. The first hunter pulls and runs straight back to the raid group. When the giants reach the tanks (the firelord will be slightly ahead) group1 and group2 will engage their giant bringing them towards the their sides. As soon as this happens the hunter standing with the tank that will be on the firelord will use distracting shot to make sure that the firelord doesnt peel back to group1 and 2. If this fails we will have the emergency group up halfway ready to charge in, gain agro and pull him down. If the distracting shot works, the main warrior set up for tanking the firelord will get on him and pull him down to the back. Moving back to group1/2 when the firelord gets pulled far down there will be a \"safe pocket\" in the middle of the triangle of mobs to which the healers should move towards. This is an ideal position because you can keep tabs on your mage if he needs heals while attacking the firelord, but also be in range to heal the group1/2 tanks all the while staying out of the AOE debuff/dmg from the mobs. Back to the rest of the raid group, the tank that has agro on the firelord has to be aware of any lava spawns that are summoned while pulling him down, because if he spawns one but is pulled down away from it this may wipe us since there will be no blizzard effecting it. So it\'s critical the agro\'d tank moves the firelord in towards any spawns - this is more important then pulling it back to the ideal spot (however we hope it doesnt happen until he stops). On that note its very important that the mages use their blizzard!! it does double damgage and keeps dps on both the firelord and any spawns, all other melee focus on the spawns as they come. Once he\'s down the raid will move onto one of the giants the healers using raidbar will hopefully help out with healing the 2 tanks will on the giants as their mana will be starting to run low. This may have to be tweaked as we practice this strategy but i believe its a very good start to get us by this part without wiping. This is an easy mob to kill when alone, and if it adds it can be banished. This guy is tough to hold agro on and he likes to randomly select targets and knock them back a bit It\'s important to either keep your back to a wall or be a safe distance from the edge of the lava. He doesnt really knock you back very far so if you\'re in from the sides you should be fine. Just nuke away at him...no strategy is really needed Very similar to the surger, but it does a lot less charging at random people. He is still hard to hold solid agro on him, but is a little better to control Easy to kill...no strategy is really needed This guy likes to roam around all over and will keep respawning every 20minutes or so until magamadar is slain, in which they will not repop after they are killed. It has serveral different AoE spells that are randomly given to the mob once spawned. They consist of: Short duration stun 200 fire resist debuff 50% spell and melee slow Short duration confuse 30% less health 50% less int/spirit Some are worse then others, but they\'re all relatively easy to handle. The main key to this fight is too get ALL the tanks on the other side of the hound and turning it away from the rest of the raid so that we can pound it up the ass. Rogues will also be on the back, and if he turns on you use feint. Nuke away until dead, they\'re pretty easy. After our first horrible attempt at killing these, they became trivial and are now very easy to handle. Have a tank pull while sheilded and he will use AoE taunt, in come the mages with Frost Nova and then just pound away at them with AoE\'s until dead. INSERT INTO phpbb_posts_text (post_id, bbcode_uid, post_subject, post_text) VALUES('71', '', '', 'reserved'); INSERT INTO phpbb_posts_text (post_id, bbcode_uid, post_subject, post_text) VALUES('72', '', '', 'reserved'); INSERT INTO phpbb_posts_text (post_id, bbcode_uid, post_subject, post_text) VALUES('73', '', '', 'reserved'); INSERT INTO phpbb_posts_text (post_id, bbcode_uid, post_subject, post_text) VALUES('74', '4186719149', '', 'You should be able to login, your account is active. Try again?'); INSERT INTO phpbb_posts_text (post_id, bbcode_uid, post_subject, post_text) VALUES('76', '', '', '
Blue and grey >Line : 980
File : /letalis/admin/admin_db_utilities.php
Link to comment
https://www.neowin.net/forum/topic/291075-restoring-database-and-i-get-this-error/Share on other sites
3 answers to this question
Recommended Posts