Jump to content
Sign in to follow this  
Angry_Games

hard drives & raid - benchmark and compare!

Recommended Posts

Can Stress Prime mess with my results?If youc an see I was running stress prime.If it's the case I will rerun after Prime is finished running for 12Hrs.

Later EDIT!I redid the test with only antivirus/firewall/winamp/yahoomsgr. running.The results are better as I can erad)if thhat numbers there are the transfer rates in KB/s.

attorunkb3.th.jpg

LE:Is it good or I can throw it out the window?

Share this post


Link to post
Share on other sites

If Prime95 (or dual Prime95) is running at the default CPU priority (1, or very low I think) and your are setting to use less than the available free ram in your system... then the impact of runing Prime95 and Atto at the same time would be minimal.............. yet I am sure it would give you a better result when not runing Prime95.

Share this post


Link to post
Share on other sites

awesome info! I just did a test on my raptor dual 74gb array.

 

I tried disabling read cache. My burst went up, but my access went down. I'll edit this w pics soon.

 

I'm trying disabling command queue first.

 

WITH READ CACHE AND NCQ ENABLED:

 

beforereadcachedisable.jpg

 

WITH READ CACHE DISABLED, BUT NCQ STILL ENABLED:

 

afterreadcachedisable.jpg

 

WITH READ CACHE AND NCQ BOTH DISABLED: (0% cpu??)

 

afterncqdisable.jpg

Share this post


Link to post
Share on other sites

Very nice results placenta

L.E I disabled write caching and the results are worst.The acces time is bigger and I get a 2% incerase in CPU Usage.One more question what drivers are you using?I always used the ones on the CD.Is there a driver that is known to work better?Is that the reason I can't select the dead caching?Dose my HDD have NCQ?In some price lists it appears like it has.

Later than LATER EDIT:Can I put more than 2 Drives in RAID 0 configuration?I would like to buy 2 more 320GB ones to have 1 TB.

Share this post


Link to post
Share on other sites

i dont understand my non raid sata is just as good as the benchmark i see here. also would it help to cconfiqure a raidi drive with a 16mb cache. small file write 6 51.

Share this post


Link to post
Share on other sites

Post your bench pelase.The 16MB cache helps a bit.Of course RAID will help but you need 2 HDD.s.LE:I saw a bench of 4xWD in 4xRAID 0.And The average in HDTach was 2003MB/s.And I was wondering...I would buy 2 moe HDD's but I wouldn't buy 160GB/s since they are not best buy anymore.I was thinking on 250GB 16MB cache.Can I do 2x RAID 0 Matrice?

Share this post


Link to post
Share on other sites

Try this:

 

Replace something like this:

 

AddReg = Crush11_DisableFltCache_AddReg

 

[Crush11_DisableFltCache_AddReg]

HKR,,DisableFilterCache,0x00010001,1

 

 

With something like this(for now, burp...) this:

 

AddReg = nVATA_Tweaks

 

[nVATA_Tweaks]

 

;HKR,,DisableFilterCache, %REG_DWORD%,0x00000000 ;Enables MS Filter Caching, (Disables nVATA's Ability For Read Caching) (Default, But Not Driver INF Default)

HKR,,DisableFilterCache, %REG_DWORD%,0x00000001 ;Disables MS Filter Caching, (Enables nVATA's Ability For Read Caching) (INF Default, But Not Driver Default)

 

;HKR,"Adma",EnableAdma, %REG_DWORD%,0x00000000 ;? Disabled (Default)

HKR,"Adma",EnableAdma, %REG_DWORD%,0x00000001 ;? Enabled, Increases Write Speeds

 

;HKR,"Adma",EnableBypass, %REG_DWORD%,0x00000000 ;? Disabled (Default)

HKR,"Adma",EnableBypass, %REG_DWORD%,0x00000001 ;? Enabled, Increases Read Speeds

 

Try it out...

I'm using driver 667 btw, long ago I used to use 622.

These are decent driver, 622 defently has allright burning.

I'm not totally sure about 667 though, I don't know(not bad, I just have'nt tested that much).

667 is faster then 622 however by a decent amount.

 

 

 

Edit:

Sorry dude...

Cluster size is not in any bios and never will be.

It's stripe size you're thinking of.

Which is important as well.

 

Cluster size you have to setup on the software end of things.

I'd only reccomend 64k clusters, ever...

Or larger if you can...

 

 

Now that I think about it, if read caching is giving you a problem, then it would be my guess that it's a latency issue.

Thee latency issue with these drivers anyways.

 

Which can be fixed.

But whatever.

 

The above read caching tweak is not to turn it on, but to allow you to check or uncheck the read caching box thingy in the cpl...

Like stock..., hence why it says inf default.

I have no clue what adma is, but it 1st increases write speeds a good amount, also decreases read speeds a bit though.

However after enabling the bypass mode of it,whatever that is, again, this brings the read speeds back up, past the previous.

In the end, you end up with a bit more speed overall.

 

I used atto for benching them.

Results were consistant, not using direct i/o, using overlapped i/o of 10 I think, the max it allowed me.

Tested using a 64k chunks, of a max file size of 256m, etc.

Results were I think around 100-200 megs a sec more on both read and writes.

I get around 900-1100 megs a sec right now using the os for drive access.

Edit:

That was 111,232K writes, 933,284K reads the last bench I did, sorry lol.

So the change was probably around 20-100megs, I forgot, my previous was around 800 and 80-90.

Share this post


Link to post
Share on other sites

Thnx very much.I don't get what could be the problem anyways my OS is crumpy.But I get a weirdsound from around the CPU when it writes to the HDD and I'm sure it's not the HDD beacuse I bent over and put my ear next to both of the HDD's.And one more thing how do I add that registry?I don't think it's the latency cuz I did the test and I posted it here and it was fne.The problem could be that I disabled write caching and I can't enable it now.

Share this post


Link to post
Share on other sites

Aeka you give out good tips, but for the sake of sanity, you should say which file to edit, is this a INF file you should edit? If so, which one?

 

Is it a .REG file you should edit? If so which one? Or create a new one?

 

Im sure clever people can figure this one out, but seeing you already completed these steps it would be easier for others to follow if you give a example

 

create nvfix.inf

 

put this in it:

 

AddReg = nVATA_Tweaks

[nVATA_Tweaks]

;HKR.. etc

 

etc..

 

:thumbsup:

Share this post


Link to post
Share on other sites

Np ;), just been having some issues in real life that I've been trying to take care of, 4x abcess infections.... yum yum sort of thing lol

 

 

Lemme break it down ;)

Extract the nVidia driver pack(chipset).

You'll have a sub folder called "IDE".

 

IDE

IDEWin2K

IDEWinXP

 

Lemme explain these 2 1st.

In oder to install into win2k, you need a win2k folder for some reason, even though the driver recognizes the inf and files in the winxp folder, and acts like it's going to install it, it ends up not installing it.

 

So you need both win2k and winxp folders to install in any os.

Both folders will be completely identical.

 

So mod say the winxp folder, then copy the xp one over the 2k one, something like that.

 

Just for clearification...

 

 

Ok, we have these inf's:

nvatabus.inf

nvata.inf

nvraid.inf

 

All of these do the same thing.

In a full ver of the driver, you'll have 2 of them.

 

nvatabus.inf

nvata.inf

These are identical, just diff names in diff rev's of the drivers.

Same exact inf though.

 

The raid one is for raid stuff.

 

It should of been intergrated into 1 inf, but it is'nt, yet anyways I'm not sure.

Same layout though.

 

Anyways you'll have to mod both.

 

 

Essentually they are the same.

But not...

 

In any of these inf's, you'll find a line saying something like this:

 

[Crush11_Service_Instx86]

ServiceType = %SERVICE_KERNEL_DRIVER%

StartType = %SERVICE_BOOT_START%

ErrorControl = %SERVICE_ERROR_CRITICAL%

ServiceBinary = %12%nvatabus.sys

LoadOrderGroup = "SCSI Miniport"

AddReg = Crush11_DisableFltCache_AddReg

 

Ignore the above except the line where it says add reg disable filter cache...

 

Pointing it out:

 

[Crush11_Service_Instx86]

AddReg = Crush11_DisableFltCache_AddReg

 

Here's that reg:

 

[Crush11_DisableFltCache_AddReg]

HKR,,DisableFilterCache,0x00010001,1

 

Understand how this goes?

AggReg = [bracket title thing you can make or mod or whatever]

 

 

Anyways a portion of the my previos post is allready in there ;).

 

HKR,,DisableFilterCache,0x00010001,1

 

Or:

 

;HKR,,DisableFilterCache, %REG_DWORD%,0x00000000 ;Enables MS Filter Caching, (Disables nVATA's Ability For Read Caching) (Default, But Not Driver INF Default)

HKR,,DisableFilterCache, %REG_DWORD%,0x00000001 ;Disables MS Filter Caching, (Enables nVATA's Ability For Read Caching)

 

Note it has those wierd #'s on the top ver...

 

Check this:

 

; *******Non Localizable Strings*******

 

SERVICE_BOOT_START = 0x0

SERVICE_SYSTEM_START = 0x1

SERVICE_AUTO_START = 0x2

SERVICE_DEMAND_START = 0x3

SERVICE_DISABLED = 0x4

 

SERVICE_KERNEL_DRIVER = 0x1

SERVICE_ERROR_IGNORE = 0x0

SERVICE_ERROR_NORMAL = 0x1

SERVICE_ERROR_SEVERE = 0x2

SERVICE_ERROR_CRITICAL = 0x3

 

REG_EXPAND_SZ = 0x00020000

REG_DWORD = 0x00010001

 

See ;), it's doing the same, just the run about way.

Well, not really I guess.

 

It's actually the correct way they doit.

But, you can make an inf much easier to read and work with if you use these little macro thingys.

Which nvidia allready di, a little bit, but they did'nt use them for some reason...

Whatever.

 

 

 

This is what I did:

 

[Crush11_Service_Instx86]

 

Replaced:

AddReg = Crush11_DisableFltCache_AddReg

 

With:

AddReg = nVATA_Tweaks

 

(The reason being is to reserve a function witha decent name, somewhat decent(may rename the end of it but hey), for future use, for me...)

 

You don't have to do that.

 

Then I replaced:

[Crush11_DisableFltCache_AddReg]

HKR,,DisableFilterCache,0x00010001,1

 

With:

[nVATA_Tweaks]

 

;HKR,,DisableFilterCache, %REG_DWORD%,0x00000000 ;Enables MS Filter Caching, (Disables nVATA's Ability For Read Caching) (Default, But Not Driver INF Default)

HKR,,DisableFilterCache, %REG_DWORD%,0x00000001 ;Disables MS Filter Caching, (Enables nVATA's Ability For Read Caching)

 

;HKR,"Adma",EnableAdma, %REG_DWORD%,0x00000000 ;? Disabled, Increases Write Speeds (Default)

HKR,"Adma",EnableAdma, %REG_DWORD%,0x00000001 ;? Enabled, Increases Write Speeds

 

;HKR,"Adma",EnableBypass, %REG_DWORD%,0x00000000 ;? Disabled, Increases Read Speeds (Default)

HKR,"Adma",EnableBypass, %REG_DWORD%,0x00000001 ;? Enabled, Increases Read Speeds

 

 

Do this with any inf you have in the /ide/ sub folders.

Then duplicate that sub folder as, either winxp or win2k(likely missing win2k so make one by copying your modded winxp folder).

Just for completion, if you want to use win2k with this driver ver.

 

Now you may or may not have the raid inf, some drivers do, some don't.

 

 

 

To get more detailed about the driver it's self.

The mods allready shown above so...

 

Under each sub dir, ie /ide/winxp

There's: raidtool

/IDE/winxp/raidtool

 

It can be extracted(there's compressed raidtool dir's in certain ver's).

 

There's 2 inf's, which I explained above, raid and non raid ones.

 

Then there's these files, which are the most important to exlain when putting together a completely custom driver(sorta).

 

nvatabus.sys

nvata.sys

 

nvraid.sys

 

You cannot use the raid sys driver for non raid controller's.

It does'nt work out.

For now anyways.

 

The other 2, nvata and nvatabus are the same exact thing.

Diff names for diff driver ver's.

Use what ver you like the best, rename it if nessary, or change the inf to use that file name.

 

 

[sourceDisksFiles.x86]

nvatabus.sys=0

idecoi.dll=0

 

[Crush11_Service_Instx86]

ServiceType = %SERVICE_KERNEL_DRIVER%

StartType = %SERVICE_BOOT_START%

ErrorControl = %SERVICE_ERROR_CRITICAL%

ServiceBinary = %12%nvatabus.sys

LoadOrderGroup = "SCSI Miniport"

AddReg = nVATA_Tweaks

 

[Crush11_EventLog_AddReg]

HKR,,EventMessageFile,0x00020000,"%%SystemRoot%%System32IoLogMsg.dll;%%SystemRoot%%System32driversnvatabus.sys"

HKR,,TypesSupported,0x00010001,7

 

[Crush11.Files.x86_12]

nvatabus.sys

 

Just chnage the above instances of nvatabus.sys to nvata.sys if you wanted, that's how you would do that.

 

If you wanted to rename the service...

 

[Crush11_Inst.ntx86.Services]

AddService = nvatabus,0x00000002,Crush11_Service_Instx86,Crush11_EventLog_Instx86

 

Where it says nvatabus, renme to whatever you want.

I'd rename to nVATA...

Whatever.

 

 

Anyways lets get to some better thigns to do.

 

[Version]

Signature = "$Windows NT$"

Class=HDC

ClassGUID={4d36e96a-e325-11ce-bfc1-08002be10318}

Provider=%NVIDIA%

CatalogFile=nvata.cat

DriverVer=01/18/2005,5.10.2600.0622

 

Do this:

 

[Version]

Signature = "$Windows NT$"

Class=HDC

ClassGUID={4d36e96a-e325-11ce-bfc1-08002be10318}

Provider=%NVIDIA%

;CatalogFile=nvata.cat

DriverVer=01/18/2005,5.10.2600.0622

 

Also, when chnaging the main files(the 3 I stated above, the sys ones), chnage the ver in the above text, in the inf of course, to what ver you are using.

It makes it easier for upgrading(windows by default won't install a driver unless it's newer).

Also win2k freaks out unless it's newer.

(more on this in the end of my post).

 

Change the date to the date you modded it probably.

You can keep the inf across diffrent driver versions.

 

Note this: (old of my crap, not modded, just addins from this and that driver).

 

 

[Manufacturer]

%NVIDIA%=NVIDIA

 

[NVIDIA]

; 32 bit only platforms

%MCP2Desc%=Crush11_Inst,PCIVEN_10DE&DEV_0065

%MCP2SS%=Crush11_Inst,PCIVEN_10DE&DEV_008E&REV_A2

%MCP2SS%=Crush11_Inst,PCIVEN_10DE&DEV_008E&REV_A3

%MCP2SP%=Crush11_Inst,PCIVEN_10DE&DEV_0085

; 32/64 bit platforms

%CK8Desc%=Crush11_Inst,PCIVEN_10DE&DEV_00D5&REV_A2

%CK8DescSB%=Crush11_Inst,PCIVEN_10DE&DEV_00D5&REV_F2

%CK8Desc%=Crush11_Inst,PCIVEN_10DE&DEV_00D5&REV_A4

%CK8DescSB%=Crush11_Inst,PCIVEN_10DE&DEV_00D5&REV_F4

%CK8Desc%=Crush11_Inst,PCIVEN_10DE&DEV_00D5&REV_A5

%CK8DescSB%=Crush11_Inst,PCIVEN_10DE&DEV_00D5&REV_F5

%CK8Desc%=Crush11_Inst,PCIVEN_10DE&DEV_00D5&REV_A6

%CK8DescSB%=Crush11_Inst,PCIVEN_10DE&DEV_00D5&REV_F6

%CK8SSP%=Crush11_Inst,PCIVEN_10DE&DEV_00E5

%CK8SSS%=Crush11_Inst,PCIVEN_10DE&DEV_00EE

%CK8SSS%=Crush11_Inst,PCIVEN_10DE&DEV_00E3

%MCP04SSS%=Crush11_Inst,PCIVEN_10DE&DEV_003E

%MCP04SSS%=Crush11_Inst,PCIVEN_10DE&DEV_0036

%MCP04SSP%=Crush11_Inst,PCIVEN_10DE&DEV_0035

%MCP51S%=Crush11_Inst,PCIVEN_10DE&DEV_0267&CC_0101

%MCP51S%=Crush11_Inst,PCIVEN_10DE&DEV_0266&CC_0101

%CK804SSS%=Crush11_Inst,PCIVEN_10DE&DEV_0055

%CK804SSS%=Crush11_Inst,PCIVEN_10DE&DEV_0054

%CK804SSP%=Crush11_Inst,PCIVEN_10DE&DEV_0053

 

This is how you add a controlelr, a device to the inf.

Simple as heck.

 

Note:

 

 

[strings]

 

; *******Localizable Strings*******

NVIDIA= "NVIDIA Corporation"

Desc_x860= "SRCDATA"

MCP2Desc="NVIDIA nForce2 ATA Controller"

MCP2SS="NVIDIA nForce2 Serial ATA Compatible Controller"

MCP2SP="NVIDIA nForce2 Parallel ATA Controller"

CK8Desc="NVIDIA nForce3 Parallel ATA Controller"

CK8DescSB="NVIDIA nForce3 Parallel-Serial ATA Bridged Controller"

CK8SSS="NVIDIA nForce3 250 Serial ATA Controller"

CK8SSP="NVIDIA nForce3 250 Parallel ATA Controller"

MCP04SSS="NVIDIA nForce4 Intel® Edition Serial ATA Controller"

MCP04SSP="NVIDIA nForce4 Intel® Edition Parallel ATA Controller"

MCP51S="NVIDIA MCP51 Serial ATA Controller"

MCP51P="NVIDIA MCP51 Parallel ATA Controller"

CK804SSS="NVIDIA nForce4 Serial ATA Controller"

CK804SSP="NVIDIA nForce4 Parallel ATA Controller"

 

Stuff like: CK804SSP, in the device id portion are just links to the names in the string/macro portion.

It's the default, messy way that everyone makes a driver.

 

You can get more advanced on it's @ss and make it in one if you want...

 

For example:

 

%MCP2Desc%=Crush11_Inst,PCIVEN_10DE&DEV_0065

 

"Device Name"=Device_Install_Linkage,PCIVEN_10DE&DEV_0123

 

10DE is the vendor id for nv.

the the dev id.

Then sub device id's if needed, for example:

 

%MCP2Desc%=Crush11_Inst,PCIVEN_10DE&DEV_0065&SUBSYS_012310DE

 

 

Anyways that's the basic's of it.

 

Her'e the reg file ver of the mod I told you guys about in the previous post.

 

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnvatabus]

 

"DisableFilterCache"=dword:00000001

 

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnvatabusAdma]

 

"EnableAdma"=dword:00000001

"EnableBypass"=dword:00000001

 

;;; Or : (diff driver rev sometimes uses this, official ones of course)

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnvata]

 

"DisableFilterCache"=dword:00000001

 

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnvataAdma]

 

"EnableAdma"=dword:00000001

"EnableBypass"=dword:00000001

 

 

;;;;

 

Oh and note, sata drivers are infact pata drivers, they work for both.

So you can use the files from ethier if you wish.

 

Keep with one inf, add you device id, or move from each driver inf to the next.

 

Replace all files, use newest possible except for the main 3 files(nvata/nvatabus, and nvraid).

Use whatever ver you want for those 3...

Extrat the raidtool dir into ide/winxp and win2k.

Use the newest files there.

 

When looking for newest files, check by data and driver ver's, ver's come 1st, when there is no ver, check the size, and date.

 

 

Oh yeah, the one thingy...

 

Use the windows find thingy, for files, search for:

oem*.inf, in the same partition where you got windows.

Del all of them, when things are getting hard to install.

 

Remove the devices, then reset, then install, it should install corretly then(win2k aand maybe stock winxp+).

That's if you allready installed the same driver rev allready before hand, stuff liek that.

The knowledge comes in handy when yuou mod alot, and install it over and over for testing.

 

 

Anyways lol, overkill ^^ I think.

The reg file ver's are above ;).

The forum may add a gap or 2 here and there(vb does it alot to reg stuff for some reason), should be understandable though and correctable easy enough.

 

See if it helps a tiny bit, I only checked using atto using pretty much the layer in windows, I don't use direct i/o in progs anyways except for hex editing.

It's actually slower then using windows to doit on my end.

 

 

Edit:

Oh and if you make a reg file, instead of using regedit, make sure you press enter/return twice after the last return.

 

For example.

 

Last line here.

 

 

(end of file, the previous line is the actual last line, blank, no char's, that sort of thing)

 

 

I think I about covereed it though.

I could go on and on about service start types, start failed types.., logging types, device types(you can make it into a scsi controller if you want...), that sorta thing.

But that's general/advanced inf crap, stuff that isnt truly relative to this topic.

 

 

On last edit:

The tweaks I found I someething I had stashed away from driver string dumps.

A very small portion of it, but those 3 are all of the ones that belong to the service.

The other ones go into a diff spot in the registry, where dma modes and all that goes(cpl stuff).

 

I have been strauggling recent with diff aspects of my system, so I started working on a few diff things here and there to ensure they were in top form.

And one of them ended up being the disk driver thingy.

Benched and was happy with the results on my end so...

 

Been super pi'ing everthing too recenty...

 

 

Anyways here is the rest of my dump, to give you an idea of what may be possible so far with the drivers these days, nv ide wise:

 

 

HKR,,EnableNCQ, %REG_DWORD%,0x00000001 ;?

;HKR,,IncrementTimeout, %REG_DWORD%,0x00000000 ;?

;HKR,,isableRemovable, %REG_DWORD%,0x00000000 ;?

;HKR,,SataPowerDownCount, %REG_DWORD%,0x00000000 ;?

;HKR,,SingleController, %REG_DWORD%,0x00000000 ;?

(These may be servece based, oops, should of re-looked I guess)

 

These are defently service based, yeah I forgot again, but anyways these I dn what to do with:

;HKR,"Adma",EnableNotifiers, %REG_DWORD%,0x00000000 ;?

;HKR,"Adma",Timeout, %REG_DWORD%,0x00000000 ;?

 

These go into the same part of the reg that the cpl mods:

 

;Override

;EnableDma

;UltraDmaActive

;MultiWordDmaActive

;SataSpeedActive

;FlushPolicy

;FlushTimer

;WriteCacheEnabled

;QueuedCmdEnabled

;TCQEnabled

;UseBiosDefault

;Downgraded

;MaxRetries

;MaxErrors

;ErrorWindow

;DiskSortAlgorithm

;DiskSortStarvation

;ReadAheadEnabled

;ReadAheadSize

;MaxCpb

;AdaptiveQueuing

;QueuedThreshold

;NonQueuedThreshold

;QueueChange

;NonQueueChange

;SequentialMaxCount

;SequentialThreshold

;SequentialDecrement

;EarlyInterrupt

 

;Secondary

;Slave

;EnableDma

;UltraDmaActive

;UltraDMASupport

;MultiWordDMAActive

;MultiWordDMASupport

;SataSpeedActive

;SataSpeedSupport

;FlushPolicy

;FlushTimer

;WriteCacheSupported

;WriteCacheEnabled

;QueuedCmdSupported

;QueuedCmdEnabled

;UseBiosDefault

;Downgraded

;MaxRetries

;MaxErrors

;ErrorWindow

;DiskSortAlgorithm

;DiskSortStarvation

;ReadAheadEnabled

;ReadAheadSupported

;ReadAheadSize

;MaxCpb

;AdaptiveQueuing

;QueuedThreshold

;NonQueuedThreshold

;QueueChange

;NonQueueChange

;SequentialMaxCount

;SequentialThreshold

;SequentialDecrement

;EarlyInterrupt

 

;Timing

;Timing

;Pio

;Udma

;Timing

;Pio

;Udma

;Channel

;Channel

 

Yes there is dup's in there, that's the way the driver had them, maybe not the same oder though, I think I sorted them.

 

Anyways I'm gonan quit while I'm ahead lol, I don't mean to piss people off with rambling.

I don't add any of those to my inf's or anything, just the ones I said before.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...