a. I have a Sony Vaio Notebook with a nearly full 256GB SSD drive, 8GB Ram - its seems like its quick to overheat and shuts itself down frequently, especially if there's a lot of network traffic
b. I have a MacBook Pro, 15", 500GB SSD
c. I cant afford to purchase a new system (Windows or Mac) AND I'd like to migrate the 'content' off the Sony Vaio
My plan/thoughts goes something like this
Upgrade the SSD in the Macbook Pro to 2TB
Install Mac Parallels on the MacBook Pro
Import the Sony Vaio as a VM onto the MacBook Pro (yeah, its going to be a mutha of a VM)
If the 'Vaio VM' is usable, good, if not, continue
Create a new Windows 7 VM on the MacBook under Parallels (maybe on an external drive), Install VS 2015 Onto it (the Sony Vaio only has VS2010 on it)
If I can get past step (3), my big worry is if Parallels can actually handle a VM that size
Any thoughts ? or do I download the 14 day trial of Parallels and 'jfgowi' (just freaken get on with it)
I hope you feel better soon! One of my friends has a Hyper-V VM with a 64 TB drive and it works fine (he is using a RAID system to store it). I don't know what he has on it, but I do know it is about half full.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
I have installed SQL server 2008 R2 and I have created databse engine instance. I am configuring mail setup. What should be in the field of server name? I am new to this and don't know what to put there. Please help me out.
On New Database Mail Account screen, for Server Name specify your SMTP Server name like
Hotmail: SMTP server name: smtp.live.com, Port number: 587
Gmail : SMTP server name: smtp.gmail.com, Port number: 587
Yahoo : SMTP server name: smtp.mail.yahoo.com,Port number : 25
AOL : SMTP server name: smtp.aol.com, Port number : 587
The server requires a secure connection (SSL) - check this box
At home I got Windows 10 Pro.
I also have Hyper V with a few virtual machines, including another (virtual) Windows 10 (pro) machine.
I am trying to share file between the two! Doesn't work!
My VM use an External (Virtual) Network switch
On my local (real) PC I have a file share available to everybody (read/write access).
On my VM, in the file explorer > network, I can see my (real) PC, but I can't open the file share!!
OK.. so I have an application built on the .NET 2.0 framework with a MySQL database which needs to run on a 64-bit Windows 2008 Server (with service Pack 1)
After installing it, in order to get it to run, I have to go to the application pools in IIS, find the relevant one, click on Advanced Settings, and set "Enable 32-bit applications" to True.
That works - otherwise I get a "Server Error in '/' Application. ... is not a valid Win32 application" page.
Trouble is though, as soon as I do set this, while simple pages display al;right, as soon as I get to one that requires database access I get this error:
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
If I set "Enable 32-bit applications" to False, I can run a simple test page that access tha database (uncompiled, with inline server code) and this works fine - so the connector is working adn the connectionstring correct.
All of which kind of leaves me between a rock and hard place. Any ideas gratefully received!
You've created an ODBC data source using the 64-bit version of the ODBC Administrator tool. You need to create it in the 32-bit version of the tool, which is located at: %SystemRoot%\SysWOW64\odbcad32.exe
You have to check with the hosting services in what way MySQL configured...You have two main options...
1. MySQL accessible only from applications running on the hosted server...
2. MySQL made public and you can use it from the outside world...
In my experience it is always the first option you get...
But! also in this case you can access your data from outside, by adding a layer - of some API - of software to it...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.