Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Got windows 10 installed.


  • Please log in to reply
69 replies to this topic

#1 Allen

Allen

  • Members
  • 337 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Canada
  • Local time:03:16 PM

Posted 01 October 2014 - 04:17 PM

No issues so far, install went smoothly

 

VmIWIW4.png


Hey everyone I'm Allen I am a young web developer/designer/programmer I also help people with computer issues including hardware problems, malware/viruses infections and software conflicts. I am a kind and easy to get along with person so if you need help feel free to ask.

BC AdBot (Login to Remove)

 


#2 connor12568

connor12568

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Local time:02:16 PM

Posted 01 October 2014 - 04:29 PM

Windows 10...?

I thought it was windows 9 

:smash:


Edited by connor12568, 01 October 2014 - 04:37 PM.


#3 Union_Thug

Union_Thug

    Bleeps with the fishes...


  • Members
  • 2,355 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:is everything
  • Local time:02:16 PM

Posted 02 October 2014 - 12:10 AM

Installed mine in VMWare Player, no problem...pretty fast install AAMOF. It's very "7 like"...

 

1murray.jpg

...Which is nice!

 

A5_Win_10.png


Edited by Union_Thug, 02 October 2014 - 12:15 AM.


#4 old rocker

old rocker

  • Members
  • 451 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:East Tennessee
  • Local time:02:16 PM

Posted 02 October 2014 - 07:27 AM

Already found first stumbling block...

 

It will not accept EMET 5.0 (Cannot start service) and install rolls back.

 

Going to try EMET 4.1 to see if there is any difference.

 

----- Edit -----

 

EMET 4.1 installation went without a hitch.
Using default recommended settings for now.

Now for the task of finding out why 5.0 final hangs on starting the service, causing installation to fail.

From the Application log...

 1. Application: EMET_Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.ShimUtil.WriteSdb(System.String, Boolean, delCanHandleExeEntry)
   at MitigationInterface.ShimUtil.CommitExeEntries(delCanHandleExeEntry)
   at MitigationInterface.ApplicationMitigations.UpdateShimDb(MitigationInterface.AppConfigEntryList)
   at MitigationInterface.ApplicationMitigations.RebuildApplicationsShim()
   at MitigationInterface.ConfigHelper.InitEmet(MitigationInterface.ConfigOptions)
   at ServiceProcess.MainService.HandleCommandLineArgs(System.String[])
   at ServiceProcess.MainService.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

 2. Faulting application name: EMET_Service.exe, version: 5.0.5324.31805, time stamp: 0x53d99e7a
Faulting module name: apphelp.dll, version: 6.4.9841.0, time stamp: 0x5413c365
Exception code: 0xc0000005
Fault offset: 0x0000000000041c7b
Faulting process id: 0xc9c
Faulting application start time: 0x01cfde3e68477df9
Faulting application path: C:\Program Files (x86)\EMET 5.0\EMET_Service.exe
Faulting module path: C:\Windows\system32\apphelp.dll
Report Id: a62f89ff-4a31-11e4-95d7-b8ac6f6ae9e5
Faulting package full name:
Faulting package-relative application ID:

 3. Application: EMET_Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.ShimUtil.WriteSdb(System.String, Boolean, delCanHandleExeEntry)
   at MitigationInterface.ShimUtil.CommitExeEntries(delCanHandleExeEntry)
   at MitigationInterface.ApplicationMitigations.UpdateShimDb(MitigationInterface.AppConfigEntryList)
   at MitigationInterface.ApplicationMitigations.RebuildApplicationsShim()
   at MitigationInterface.ConfigHelper.InitEmet(MitigationInterface.ConfigOptions)
   at ServiceProcess.MainService.HandleCommandLineArgs(System.String[])
   at ServiceProcess.MainService.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

 4. Faulting application name: EMET_Service.exe, version: 5.0.5324.31805, time stamp: 0x53d99e7a
Faulting module name: apphelp.dll, version: 6.4.9841.0, time stamp: 0x5413c365
Exception code: 0xc0000005
Fault offset: 0x0000000000041c7b
Faulting process id: 0xc5c
Faulting application start time: 0x01cfde3e6be99d44
Faulting application path: C:\Program Files (x86)\EMET 5.0\EMET_Service.exe
Faulting module path: C:\Windows\SYSTEM32\apphelp.dll
Report Id: a9c0b7f9-4a31-11e4-95d7-b8ac6f6ae9e5
Faulting package full name:
Faulting package-relative application ID:

 5. Application: EMET_Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.ShimUtil.WriteSdb(System.String, Boolean, delCanHandleExeEntry)
   at MitigationInterface.ShimUtil.CommitExeEntries(delCanHandleExeEntry)
   at MitigationInterface.ApplicationMitigations.UpdateShimDb(MitigationInterface.AppConfigEntryList)
   at MitigationInterface.ApplicationMitigations.RebuildApplicationsShim()
   at MitigationInterface.ConfigHelper.InitEmet(MitigationInterface.ConfigOptions)
   at ServiceProcess.MainService.HandleCommandLineArgs(System.String[])
   at ServiceProcess.MainService.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

 6. Faulting application name: EMET_Service.exe, version: 5.0.5324.31805, time stamp: 0x53d99e7a
Faulting module name: apphelp.dll, version: 6.4.9841.0, time stamp: 0x5413c365
Exception code: 0xc0000005
Fault offset: 0x0000000000041c7b
Faulting process id: 0xc50
Faulting application start time: 0x01cfde3e6f3ccb5e
Faulting application path: C:\Program Files (x86)\EMET 5.0\EMET_Service.exe
Faulting module path: C:\Windows\SYSTEM32\apphelp.dll
Report Id: ad1649d7-4a31-11e4-95d7-b8ac6f6ae9e5
Faulting package full name:
Faulting package-relative application ID:

 7. Application: EMET_Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.ShimUtil.WriteSdb(System.String, Boolean, delCanHandleExeEntry)
   at MitigationInterface.ShimUtil.CommitExeEntries(delCanHandleExeEntry)
   at MitigationInterface.ApplicationMitigations.UpdateShimDb(MitigationInterface.AppConfigEntryList)
   at MitigationInterface.ApplicationMitigations.RebuildApplicationsShim()
   at MitigationInterface.ConfigHelper.InitEmet(MitigationInterface.ConfigOptions)
   at ServiceProcess.MainService.HandleCommandLineArgs(System.String[])
   at ServiceProcess.MainService.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

 8. Faulting application name: EMET_Service.exe, version: 5.0.5324.31805, time stamp: 0x53d99e7a
Faulting module name: apphelp.dll, version: 6.4.9841.0, time stamp: 0x5413c365
Exception code: 0xc0000005
Fault offset: 0x0000000000041c7b
Faulting process id: 0x820
Faulting application start time: 0x01cfde3e728d9c53
Faulting application path: C:\Program Files (x86)\EMET 5.0\EMET_Service.exe
Faulting module path: C:\Windows\SYSTEM32\apphelp.dll
Report Id: b064b535-4a31-11e4-95d7-b8ac6f6ae9e5
Faulting package full name:
Faulting package-relative application ID:

 9. Application: EMET_Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.ShimUtil.WriteSdb(System.String, Boolean, delCanHandleExeEntry)
   at MitigationInterface.ShimUtil.CommitExeEntries(delCanHandleExeEntry)
   at MitigationInterface.ApplicationMitigations.UpdateShimDb(MitigationInterface.AppConfigEntryList)
   at MitigationInterface.ApplicationMitigations.RebuildApplicationsShim()
   at MitigationInterface.ConfigHelper.InitEmet(MitigationInterface.ConfigOptions)
   at ServiceProcess.MainService.HandleCommandLineArgs(System.String[])
   at ServiceProcess.MainService.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

10. Faulting application name: EMET_Service.exe, version: 5.0.5324.31805, time stamp: 0x53d99e7a
Faulting module name: apphelp.dll, version: 6.4.9841.0, time stamp: 0x5413c365
Exception code: 0xc0000005
Fault offset: 0x0000000000041c7b
Faulting process id: 0x1ec
Faulting application start time: 0x01cfde3e75de6751
Faulting application path: C:\Program Files (x86)\EMET 5.0\EMET_Service.exe
Faulting module path: C:\Windows\SYSTEM32\apphelp.dll
Report Id: b3b582d2-4a31-11e4-95d7-b8ac6f6ae9e5
Faulting package full name:
Faulting package-relative application ID:

11. Application: EMET_Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.ShimUtil.WriteSdb(System.String, Boolean, delCanHandleExeEntry)
   at MitigationInterface.ShimUtil.CommitExeEntries(delCanHandleExeEntry)
   at MitigationInterface.ApplicationMitigations.UpdateShimDb(MitigationInterface.AppConfigEntryList)
   at MitigationInterface.ApplicationMitigations.RebuildApplicationsShim()
   at MitigationInterface.ConfigHelper.InitEmet(MitigationInterface.ConfigOptions)
   at ServiceProcess.MainService.HandleCommandLineArgs(System.String[])
   at ServiceProcess.MainService.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

12. Faulting application name: EMET_Service.exe, version: 5.0.5324.31805, time stamp: 0x53d99e7a
Faulting module name: apphelp.dll, version: 6.4.9841.0, time stamp: 0x5413c365
Exception code: 0xc0000005
Fault offset: 0x0000000000041c7b
Faulting process id: 0x9f4
Faulting application start time: 0x01cfde3e792cd4a6
Faulting application path: C:\Program Files (x86)\EMET 5.0\EMET_Service.exe
Faulting module path: C:\Windows\SYSTEM32\apphelp.dll
Report Id: b703ee27-4a31-11e4-95d7-b8ac6f6ae9e5
Faulting package full name:
Faulting package-relative application ID:

13. Application: EMET_Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.Apphelp.SdbWriteStringTag(IntPtr, UInt16, System.String)
   at MitigationInterface.ShimUtil.WriteSdb(System.String, Boolean, delCanHandleExeEntry)
   at MitigationInterface.ShimUtil.CommitExeEntries(delCanHandleExeEntry)
   at MitigationInterface.ApplicationMitigations.UpdateShimDb(MitigationInterface.AppConfigEntryList)
   at MitigationInterface.ApplicationMitigations.RebuildApplicationsShim()
   at MitigationInterface.ConfigHelper.InitEmet(MitigationInterface.ConfigOptions)
   at ServiceProcess.MainService.HandleCommandLineArgs(System.String[])
   at ServiceProcess.MainService.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

14. Faulting application name: EMET_Service.exe, version: 5.0.5324.31805, time stamp: 0x53d99e7a
Faulting module name: apphelp.dll, version: 6.4.9841.0, time stamp: 0x5413c365
Exception code: 0xc0000005
Fault offset: 0x0000000000041c7b
Faulting process id: 0xf14
Faulting application start time: 0x01cfde3e7c7da8cf
Faulting application path: C:\Program Files (x86)\EMET 5.0\EMET_Service.exe
Faulting module path: C:\Windows\SYSTEM32\apphelp.dll
Report Id: ba54bbdf-4a31-11e4-95d7-b8ac6f6ae9e5
Faulting package full name:
Faulting package-relative application ID:

15. Product: EMET 5.0 -- Error 1920. Service 'Microsoft EMET Service' (EMET_Service) failed to start.  Verify that you have sufficient privileges to start system services.

 

:guitar:


Edited by old rocker, 02 October 2014 - 11:01 AM.


#5 Kirbyofdeath

Kirbyofdeath

  • Members
  • 459 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Somewhere on Earth
  • Local time:01:16 PM

Posted 02 October 2014 - 10:03 AM

Installed mine in VMWare Player, no problem...pretty fast install AAMOF. It's very "7 like"..

Lucky dog... Attempted to install, got blue screen... On my host computer.



#6 Union_Thug

Union_Thug

    Bleeps with the fishes...


  • Members
  • 2,355 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:is everything
  • Local time:02:16 PM

Posted 02 October 2014 - 10:54 AM


Lucky dog... Attempted to install, got blue screen... On my host computer.

 

VMWare or VBox? Did you create the VM as a Win 8 machine? How much Ram on the host & VM? My host has 8gb, gave the VM 2.5gb, VMWare tools installed no problem.

The devil is in the details...

 

http://answers.microsoft.com/en-us/windows/forum/windows_tp-windows_install/windows-10-preview-on-a-virtual-machine/76d1b436-040c-436d-951c-696f684cbfc0


Edited by Union_Thug, 02 October 2014 - 11:03 AM.


#7 khafan11

khafan11

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:09:46 PM

Posted 02 October 2014 - 11:43 AM

@Allen

 

can you make vpn connection and take pic from > Properties > Options ?



#8 Kirbyofdeath

Kirbyofdeath

  • Members
  • 459 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Somewhere on Earth
  • Local time:01:16 PM

Posted 02 October 2014 - 04:16 PM

 

Lucky dog... Attempted to install, got blue screen... On my host computer.

VMWare or VBox? Did you create the VM as a Win 8 machine? How much Ram on the host & VM? My host has 8gb, gave the VM 2.5gb, VMWare tools installed no problem.

The devil is in the details...
 
http://answers.microsoft.com/en-us/windows/forum/windows_tp-windows_install/windows-10-preview-on-a-virtual-machine/76d1b436-040c-436d-951c-696f684cbfc0

 

VBox... Nice oracle...
 Attempt A: Host BSOD

 

Attempt B to D (no EFI):
(Host) "Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000005D
Parameters:
0x00000000078BFBFF
0x0000000028100800
0x0000000000000001
0x0000000000000000"

 

Attempt E (EFI): Forever hang.

 

Attempt F (No EFI): Works!



#9 rockysosua

rockysosua

  • Members
  • 772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Caribbean
  • Local time:02:16 PM

Posted 02 October 2014 - 04:51 PM

Wouldn't it be a lot easier to just shrink your hard drives, enough to install 10?

Not only would you avoid the VM issues, but you'd get a true feel for the system.

Running a virtual system can't give you the full resources from the computer, so it would be hard to tell if the system is faster than previous systems, and speed is a very important factor.


All is well in Paradise.

#10 Kirbyofdeath

Kirbyofdeath

  • Members
  • 459 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Somewhere on Earth
  • Local time:01:16 PM

Posted 02 October 2014 - 05:25 PM

I had just realized that, given my machine had only 5% memory left.

 

I'd prefer keeping my os on my main computer (and not to partition), so i will install it on my laptop! 


Edited by Kirbyofdeath, 02 October 2014 - 05:25 PM.


#11 Allen

Allen
  • Topic Starter

  • Members
  • 337 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Canada
  • Local time:03:16 PM

Posted 02 October 2014 - 05:35 PM

Day 2 of testing

_________________

 

No crashes

No Issues

It takes less time to get to sleep mode.

wake up time seems the same which takes usually between 1 and 5 seconds

RAM usage is good.

 

Overall its good so far.


Hey everyone I'm Allen I am a young web developer/designer/programmer I also help people with computer issues including hardware problems, malware/viruses infections and software conflicts. I am a kind and easy to get along with person so if you need help feel free to ask.

#12 rockysosua

rockysosua

  • Members
  • 772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Caribbean
  • Local time:02:16 PM

Posted 02 October 2014 - 07:10 PM


Overall its good so far.

What do you think of the changes?

Have you found many,other than the Start Menu and multiple Desktops?


All is well in Paradise.

#13 Felipe2237

Felipe2237

  • Members
  • 353 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:California,USA
  • Local time:11:16 AM

Posted 02 October 2014 - 11:58 PM

I think I'll be upgrading my 8.1 to 10 main OS this weekend. Feeling excited!

 

 

...to back up or not to back up? I'll see how luck I feel tomorrow...


Unofficial iOS Genius


#14 Union_Thug

Union_Thug

    Bleeps with the fishes...


  • Members
  • 2,355 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:is everything
  • Local time:02:16 PM

Posted 03 October 2014 - 12:56 AM

Wouldn't it be a lot easier to just shrink your hard drives, enough to install 10?

Not only would you avoid the VM issues, but you'd get a true feel for the system.

Running a virtual system can't give you the full resources from the computer, so it would be hard to tell if the system is faster than previous systems, and speed is a very important factor.

 

Good point, but OTOH bad things can happen with dual-boots gone awry. Worst that can happen in VM bad install is Rt Click>> Delete VM from disk.

That being said, I'm preparing to dual boot on my laptop's SSD, (imaging & backups) ...should be interesting :thumbup2:



#15 ocean77

ocean77

  • Members
  • 226 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Carolina
  • Local time:02:16 PM

Posted 03 October 2014 - 02:00 AM

I see where Windows 10  Beta is available for trial. Is this only the "Start Menu" or other new things to also try? Do you think it is worth trying now or wait till they get all the kinks out? Thank you!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users