Running Skyrim in Linux with WINE

A few days ago my cousin asked me to try and get Skyrim running for him on his Linux install using WINE.

I have previously gotten RIFT working on my Linux system flawlessly using WINE.

He gave me an ISO file, (probably from ill-gotten sources), and I proceeded to install from that.

Using winetricks I installed what all the other sites told me to install:


d3dx9_42
vcrun2008
xact

Then I ran the SkyrimLauncher.exe using WINE. Clicking low settings to start works, and then I click play… Nothing happens. Throws a minor error but nothing big. Ok…

So then I run TESV.exe directly, game loads in a virtual desktop as I had it setup, acting as its full screen (and annoyingly keeping my mouse inside the window). I click new game, and it sits at a black screen with gray fog floating from the bottom with the Skyrim symbol in the center of the screen. Hmm.

Well after poking around with some debug, for a few hours, I realized that the game is actually running from the Z: drive per this wine prefixes setting, and that I needed to tell it “Hey your actually running from the C: drive.”.

I looked quickly but could not find out how to force programs to run from C: in a wine config, so I created a simple command file “skyrim.cmd” file like the batch files of olde’ and inside I put the lines:


C:
CD \Program Files\Skyrim
TESV.exe

I saved the file inside my ~/.wine_skyrim/drive_c folder, and then to run the game I ran:


WINEARCH=win32 WINEPREFIX=~/.wine_skyrim wine cmd.exe /c ~/.wine_skyrim/drive_c/skyrim.cmd

Which actually ran my script, running wine at a Windows Command line, and then changed to the ‘fake’ C: drive, changed directories and ran the program.

The game runs, and then I click play. Boom, I am reading the story and it’s all working. I need to start the tweaking stage with the wine registry Direct3D entries but if anyone else has the black screen with fog try doing what I did.

By |January 31st, 2012|Categories: How To|Tags: , , , , , |3 Comments

Sierra Wireless Overdrive Pro 3G/4G

I have acquired one of these devices for work purposes to replace my air card for remote work. The device is a 3G/4G access point router to the WWAN.

During setup it mentioned a GPS unit, and wanting to learn more about this tried to find out how I could use this as a wireless GPS unit to some mapping software.

The device will install some NMEA ports if you plug it into a Windows machine and let it install some drivers, but I was not able to find out if you could use it wirelessly using this method.

Instead I ran a nmap scan against it and found TCP port 5502 open on the device. Then connect using telnet to that port, found raw NMEA data being streamed real time. After this it was easy, just have a virtual COM port to IP software connect to the device on port 5502.

After the serial port was created, I tried some basic NMEA tools and they seem to work. There are many free and commerical Serial to IP software packages. Combine that with some mapping software that will read from a standard NMEA port and your good to go.

By |December 20th, 2011|Categories: How To|Tags: , , , , , |10 Comments

Avaya/Nortel 1120E Phone Asterisk

I got a hold of some Nortel IP phones at work and was doing some reaserch on how to connect them to an Asterisk server. At first I was using them with the UNIStim protocol support in Asterisk, but instead found out that you can download SIP firmware versions for most Nortel and Avaya phones directly from Avaya since they purchased Nortel.

You can get the SIP 4.x firmware here, or browse the other firmwares as well. You do not need a username and password to download them.

This site can help as well, to get you updated to a SIP firmware from UNIStim firmware and how to configure your TFTP settings.

I needed some more configuration settings in my TFTP DeviceConfig file so this is what I ended up using.


DNS_DOMAIN archaicbinary.home
SIP_DOMAIN1 archaicbinary.home
SERVER_IP1_1 192.168.XXX.XXX
SERVER_PORT1_1 5060
SERVER_RETRIES1 3
DEF_USER1 6001
ENABLE_SERVICE_PACKAGE YES
ENABLE_3WAY_CALL YES
TRANSFER_TYPE STANDARD
REDIRECT_TYPE RFC3261
FORCE_BANNER YES
BANNER Zharvek
UPDATE_USERS NO
ENABLE_UPDATE YES
ENABLE_PRACK YES
RTP_MIN_PORT 50000
RTP_MAX_PORT 50100
SIP_PING YES
AUTOLOGIN_ENABLE YES
DEF_LANG English
VMAIL *98
VMAIL_DELAY 300
EXP_MODULE_ENABLE YES
ENABLE_BT YES
DST_ENABLED YES
TIMEZONE_OFFSET -18000
# (GMT-10:00) Hawaii -36000
# (GMT-09:00) Alaska -32400
# (GMT-08:00) Pacific time (US and Canada) -28800
# (GMT-07:00) Mountain time (US and Canada) -25200
# (GMT-06:00) Central time (US and Canada) -21600
# (GMT-05:00) Eastern time (US and Canada) -18000
# (GMT-04:00) Atlantic time (US and Canada) -14400
# (GMT-03:00) Brasilia, Buenos Aires -10800
# (GMT+00:00) Greenwich, Dublin, London 0
# (GMT+01:00) Amsterdam, Madrid, Paris	3600
# (GMT+02:00) Athens, Istanbul	 7200
# (GMT+03:00) Moscow, St. Petersburg 10800
# (GMT+05:30) Bombay, Calcutta, Madras	 18000
# (GMT+08:00) Beijing, Chongqing, Hong Kong	28800
# (GMT+09:00) Osaka, Sapporo, Tokyo, Seoul 32400
# (GMT+10:00) Canberra, Melbourne, Sydney 36000
# (GMT+12:00) Auckland, Wellington 43200
SNTP_ENABLE YES
SNTP_SERVER pool.ntp.org
AUTO_UPDATE YES
AUTO_UPDATE_TIME 3600
# 48600 = 1:30pm
# 3600 = 1:00am
# 28800 = 8:00am 29700
# 54900 = 3:15pm
AUTO_UPDATE_RANGE 1
MAX_INBOX_ENTRIES 50
MAX_OUTBOX_ENTRIES 50
MAX_REJECTREASONS 5
MAX_CALLSUBJECT 5
IM_NOTIFY NO
IM_MODE DISABLED
DEF_DISPLAY_IM NO
MAX_IM_ENTRIES 20
MAX_ADDR_BOOK_ENTRIES 100
ADDR_BOOK_MODE BOTH
RECOVERY_LEVEL 0
ADMIN_PASSWORD 123456789
DISABLE_PRIVACY_UI YES
LOGOUT_WITHOUT_PASSWORD NO
NAT_SIGNALING NONE
NAT_MEDIA NONE
HOLD_TYPE RFC2543
By |October 21st, 2011|Categories: How To|Tags: , |0 Comments

Setting Up Certificate Services

Starting with this virtual machine that I previously installed Active Directory on, next I am going to setup a simple Certificate Services service. This should usually be installed on a very secure machine in your organization as it will hold all of the private keys and be able to generate the public keys used in your network and possibly used on external services if you so wish.

Start by going to Control Panel, and Add or Remove Programs.

Click Add/Remove Windows Components, check the box next to Certificate Services. A dialog will appear with a warning as per the photo below.

Be sure you read this warning, and click Yes to continue. Then click Next.

Select ‘Enterprise root CA’ and click Next.

You will be asked for the ‘Common name for this CA:’ type in the computers name. In our case from the last walk through this was “default-fm878pv” which I did not change. If you did not change the name to something more meaningful, you can cancel out now and change it.

Click Next. Click Next again to accept the database paths. You will be asked for the Windows 2003 CD now. Insert it and click OK. After the file copy, you may be presented with this.

Click OK.

In this walk through we will enable Web Enrollment. As we might use it later for smart cards and such.

Back at the Add or Remove programs screen, click Add/Remove Windows Components again click ‘Application Server’ but do not check it, then click Details.

Click on ‘Internet Information Services (IIS)’ but do not check it and click Details.

Scroll down and check the box next to ‘World Wide Web Service’ and click OK. Click OK again. Then click Next. If you removed the 2003 CD, you will need it again.

Reboot the server.

Open a Command Prompt and type ‘certutil -vroot’ as shown in the photo below and hit Enter.

Open Internet Explorer on the server, or another workstation on the network, and connect to the server via name or IP address and browse to /certsrv like shown below in the photo.

If you see this, your web enrollment is working.

You can administrate your Certificate Services install, through Administrative Tools.

You can now use EFS with certificates on your Active Directory client machines. You will now want to look up how to issue administrator certificates to decrypt files encrypted by employees or users that you need access to as the network admin and such.

By |March 9th, 2011|Categories: How To|Tags: , , |0 Comments

Installing Active Directory

I will try to include as many screen shots as possible, to help those that are learning, or are new to installing Active Directory.

This install was performed on a virtual machine running Windows 2003 R2 Standard. The install will be similar to the install on Windows 2000.

We start off with a fresh install. Close the configure your server wizard. We are going to do this manually.

Assign a static IP address to this server, and then for the machines DNS servers primary, type in it’s own IP address. I did this while installing Windows.

Next we need to give this machine a DNS suffix. Choose the same one that you will name the domain. I’m going to use testdomain.home because this is an example setup, and I choose the .home TLD because it is not valid on the internet and will never conflict with a real domain and cause internal network problems like browsing around websites.

If you were to choose say, yahoo.com for your domain name, your clients would not be able to get to the real yahoo.com because your DNS server will resolve it to your Active Directory server and not to the Yahoo servers.

To do this, right click My Computer from the Start Menu, and choose Properties. Select the Computer Name tab at the top, and then click Change. On the Computer Name Changes dialog, click the More button and type in your suffix and click OK.

Restart the server.

Login to the server and start off by making this a DNS server for Active Directory and clients.

Go to Start Menu, Control Panel, Add/Remove Programs. Click on Add/Remove Windows Components on your left. Scroll down to Networking Services and highlight it, don’t check the box next to it, and click Details. Check the box next to Domain Name System (DNS) and then click OK then click Next. Insert the CD if asked, and click OK.

After the files copy, click Finish and close the Add/Remove Programs window.

Go to Start Menu, Administrative Tools, DNS. Right click on Forward Lookup Zones and choose New Zone. Click Next, choose Primary Zone, click Next. When asked for the Zone Name you must type the same one you did for the Computer Name Suffix in the previous steps.

Click Next and then Next again to accept the filename. When asked for the Dynamic Update, choose ‘Allow both nonsecure and secure dynamic updates’. (We will secure this later). Click Next. Then Finish.

Right click on the Reverse Lookup Zones and choose New Zone. Click Next, then Primary zone, then click Next.

Type in the first portions of your networks IP space and click Next, then Next for the filename, and then click ‘Allow both nonsecure and secure updates’. (We will secure this later). Click Next. Then Finish.

Restart the server.

Open a Command Console and type in ‘nslookup’. You should get something similar to the following:

If you get an error, your DNS server is not working correctly yet, and it has to be working to proceed.

Click Start Menu, Run. Type in ‘dcpromo’ and click OK.

Click Next, Next, and Next again for new domain, Next for new forest. When asked for the Full DNS name type in the same you have been for the above steps.

Click Next after typing your DNS name. It will then test your DNS server. You can change the NetBIOS name or leave default and click Next. Default NTDS paths and click Next. Accept defautl SYSVOL and click Next. Click Next again and then Permissions for 2003 and Higher only and click Next. Choose a password for recovery mode, and click Next. Next again and the process starts.

When it’s all done, click Finish, and Restart.

Click Start Menu, Administrative Tools, DNS. Click and then Right click on your domain under Forward Lookup Zones and choose Properties. To the right of Type click Change. Click the check box, Store the zone in Active Directory click OK and then Yes then change the dynamic updates drop down box to Secure Only and then click OK.

Do the same for the Reverse Lookup Zone. Click and then Right click your network subnet, and click Properties. Change the type to Store in Active Directory. And then dynamic updates to Secure only and click OK.

You now have a domain controller to join clients to. Make sure the clients are using the domain controller as their DNS server.

By |March 4th, 2011|Categories: How To|Tags: , |0 Comments